403 error -> Your token {} is no more valid!

  • hanmart

    14 berichten

    Polen

    HI,
    From some time we are receiving API error
    ```
    403 error -> Your token {} is no more valid!
    ```

    Even is actual one from Link (https) "See my API Keys"

    It's looks like issue occur from "Renewal failure" event from 2026-04-08 08:44, and re-activation was taken in same day. We received same api keys on mail, but key is not activated on your side
  • @thomas
    Beheerder

    351 berichten

    België

    HI,
    From some time we are receiving API error
    ```
    403 error -> Your token {} is no more valid!
    ```

    Even is actual one from Link (https) "See my API Keys"

    It's looks like issue occur from "Renewal failure" event from 2026-04-08 08:44, and re-activation was taken in same day. We received same api keys on mail, but key is not activated on your side
    • Aangemaakt 5 jun 2026 op 01:55
    • #2031359
    Hello hanmart,

    Your API keys are working properly; they have been activated. Which call are you trying to make when you encounter the error?
    Please note that the token is only valid for a limited time. You will need to retrieve a new one regularly.

    Please ensure you are using the API as described in the documentation here: Link (https)

    Best Regards,
    --
    Thomas
    Delcampe Team
  • hanmart

    14 berichten

    Polen

    Hello hanmart,

    Your API keys are working properly; they have been activated. Which call are you trying to make when you encounter the error?
    Please note that the token is only valid for a limited time. You will need to retrieve a new one regularly.

    Please ensure you are using the API as described in the documentation here: Link (https)

    Best Regards,
    --
    Thomas
    Delcampe Team
    • Aangemaakt 8 jun 2026 op 11:11
    • #2032259
    Hi Thomas,
    After verification token is working from localhost, but it's looks like IP of our server is blocked: 104.248.241.248

    For every request we receive 429 response, even I disabled all scheduled jobs on our side, so rate limit should be not extended
  • @fred
    Beheerder

    173 berichten

    België

    Hi Thomas,
    After verification token is working from localhost, but it's looks like IP of our server is blocked: 104.248.241.248

    For every request we receive 429 response, even I disabled all scheduled jobs on our side, so rate limit should be not extended
    • Aangemaakt 15 jun 2026 op 05:47
    • #2034365
    Hi hanmart,

    I'm seeing a lot of 200 response coming form your IP in our logs this morning.

    We have a limit of 180 requests per minute, any subsequent requests will fail with an HTTP code 429. Is it possible that you did more requests than the limite?

    Fred
  • hanmart

    14 berichten

    Polen

    Hi hanmart,

    I'm seeing a lot of 200 response coming form your IP in our logs this morning.

    We have a limit of 180 requests per minute, any subsequent requests will fail with an HTTP code 429. Is it possible that you did more requests than the limite?

    Fred
    • Aangemaakt 16 jun 2026 op 05:23
    • #2034800
    HI, After digging deeper I found issue with deployment from old git origin. After fixing issue it's working as expected, thanks for taking care of the report