Este contenido no está disponible en el idioma seleccionado.

Chapter 4. Troubleshoot API errors


4.1. API errors

Expand
CodeExplanationResolution

400

BadRequest error

Validate that you entered the API call correctly and try again.

401

Unauthorized

Generate a new authorization token.

403

Forbidden

Generate a new authorization token.

404

Not found

Resource not found or does not exist.

429

Too many requests

Reduce the frequency of requests

500

Internal server error

The problem is on Red Hat’s end. Wait a minute and try your request again.

4.2. Troubleshoot error 403

Error 403 is a "not authorized" error, meaning that the authentication you are using for Red Hat Subscription Manager APIs has failed. There are two possible solutions you can try.

Procedure

  1. To authenticate through the Red Hat Subscription Manager gateway, ensure the authorization header includes the text "bearer" before entering your API call:

    $ curl -H "Authorization: Bearer <token>" <api_url>
  2. If the header is correct, create a new token. Refresh tokens last for five minutes.

4.3. Troubleshoot error 429

Error 429 is a “rate limiting” error, meaning that your account has exceeded the number of allowed requests per second. This limit applies to all users of a single Red Hat account.

Procedure

  1. Extract the header of the response, which includes:

    • X-RateLimit-Limit: the total requests/sec allowed
    • X-RateLimit-Remaining: the number of requests/sec remaining (this will be a negative integer)
    • X-RateLimit-Delay: the number of seconds the requester should wait before trying again
  2. Adjust the rate of requests to the X-RateLimit-Limit value and start again once the X-RateLimit-Delay time has passed.
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de la documentación de Red Hat

Legal Notice

Theme

© 2026 Red Hat
Volver arriba