NATION

PASSWORD

'403 client not registered for api' when sending telegrams

Bug reports, general help, ideas for improvements, and questions about how things are meant to work.
User avatar
Agadar
Powerbroker
 
Posts: 7784
Founded: Dec 06, 2009
Psychotic Dictatorship

'403 client not registered for api' when sending telegrams

Postby Agadar » Mon Apr 08, 2024 1:38 pm

I'm the developer of Agadar's Telegrammer (viewtopic.php?f=15&t=388960). Recently a user contacted me telling me he's receiving HTTP status code 403 when attempting to send telegrams. I checked with my own API keys and sure enough I get the same HTTP status code 403. Using my IDE's debugger I discovered the exact message I am receiving is 'client not registered for api' when sending telegrams'. This is quite strange seeing as neither my code nor my keys have changed in literal years.

Has anything changed that can cause these 403's to appear?
Proud resident of The Western Isles, the #1 role-playing region!
Developer of Telegrammer, NS API Java Wrapper, and more!

Return to Technical

Who is online

Users browsing this forum: Bormiar, Card Cleaver, Google [Bot], Grensfind, Kractero

Advertisement

Remove ads

cron