Page 1 of 1

Telegrams API problem

PostPosted: Sun May 01, 2022 4:39 pm
by Onionist Randosia
I was just trying to run the nstg-web API for recruiting this morning, after a two-week break from running it, and I got this error message that I have never seen before:
Code: Select all
info: Evaluating Template Recipient Language string...
info: Continuous mode
info: Initially sending telegrams to the following nations: kutand_socscoky,new_manosan,woozzzie_shakie_shakie,caskbane,pyongjong,akinara,auruden,bismerick,thesweden,cobuscus,greater_solidity,scalathan
error: Failed to send telegram to kutand_socscoky.
error: { [Error: Request failed: API returned HTTP response code 403]
  responseMetadata:
   { _readableState:
      { objectMode: false,
        highWaterMark: 16384,
        buffer: [Object],
        length: 0,
        pipes: null,
        pipesCount: 0,
        flowing: true,
        ended: true,
        endEmitted: true,
        reading: false,
        sync: true,
        needReadable: false,
        emittedReadable: false,
        readableListening: false,
        resumeScheduled: false,
        destroyed: false,
        defaultEncoding: 'utf8',
        awaitDrain: 0,
        readingMore: false,
        decoder: null,
        encoding: null },
     readable: false,
     _events: { end: [Object], error: [Function], data: [Function] },
     _maxListeners: undefined,
     _mode: 'fetch',
     headers: { 'content-type': 'text/html; charset=utf-8' },
     rawHeaders: [ 'content-type', 'text/html; charset=utf-8' ],
     trailers: {},
     rawTrailers: [],
     _fetchResponse: {},
     url: 'https://www.nationstates.net/cgi-bin/api.cgi?userAgent=node-nsapi%200.1.15%20(maintained%20by%20Auralia%2C%20currently%20used%20by%20%22nstg-web%20(maintained%20by%20Auralia%2C%20currently%20used%20by%20%22Onionist%20Randosia%22)%22)&a=s[CENSORED API KEY STUFF]&to=kutand_socscoky',
     statusCode: 403,
     statusMessage: '' },
  responseText: '\n
Client Not Registered For API
Error: 403 Client Not Registered For API\n

The NationStates API Documentation\n' }


The 'Client Not Registered for API' bit was large and red. There is another person at my school who uses a recruitment API program for a different region, but that gives a different error message whenever we run our APIs at the same time. Can anyone tell me why I am getting this message and what I can do to fix it?

PostPosted: Sun May 01, 2022 4:54 pm
by Frisbeeteria
You were probably using an API key that belonged to a nation that ceased to exist. If we can't contact the keyholder when there is a problem, that key gets removed. I just cleaned those out.

If you are the designated recruiter for your region, you can request a new key.

PostPosted: Sun May 01, 2022 6:03 pm
by Onionist Randosia
Frisbeeteria wrote:You were probably using an API key that belonged to a nation that ceased to exist. If we can't contact the keyholder when there is a problem, that key gets removed. I just cleaned those out.

If you are the designated recruiter for your region, you can request a new key.

Oh ok that's probably it, as I believe the original nation which requested the regional key is CTE'd
I will request a new one
Thanks