What may cause 429 error with low number of requests?

Hello, what if I have: HTTP/1.1 429 Too Many Requests. What should I do?

https://docs.newrelic.com/docs/apis/rest-api-v2/basic-functions/api-overload-protection-handling-429-errors/

Thank you, I read it. But I did not do a lot of requests.

Content-Length: 299

  • upload completely sent off: 299 out of 299 bytes
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • old SSL session ID is stale, removing
  • Mark bundle as not supporting multiuse
    < HTTP/1.1 429 Too Many Requests
    < Date: Tue, 22 Nov 2022 16:57:22 GMT
    < Content-Type: application/json; charset=UTF-8
    < Content-Length: 2
    < Connection: keep-alive
    < CF-Ray: 76e3342cfd40e76e-DFW
    < Access-Control-Allow-Origin: *
    < Retry-After: 9
    < CF-Cache-Status: DYNAMIC
    < access-control-allow-credentials: true
    < access-control-allow-methods: GET, POST, PUT, HEAD, OPTIONS
    < Server: cloudflare
    <
    {}* Connection #0 to host metric-api.newrelic.com left intact

I have moved your question to a new topic (the one where you posted was marked Solved). A support engineer will help you as soon as possible.

1 Like

Also after next command run I have following note:
*Note: Unnecessary use of -X or --request, POST is already inferred.*

That is just telling you that the -X or --request parameter on your curl command is not necessary. You may ignore that message.

1 Like