Skip to content
English
Submit Ticket
  • There are no suggestions because the search field is empty.

What can I do if I encounter errors with the OpusDNS API?

Handling API Errors

When using the OpusDNS API, it’s important to differentiate between error types to understand what went wrong. Each error is indicated by a status code, such as 400, 401, 403, 404, 405, 409, 422, 502, and others. The code helps you identify the nature of the problem:

  • 400 (Bad Request): The request is malformed or contains invalid parameters.

  • 401 (Unauthorized): The request lacks valid authentication credentials.

  • 403 (Forbidden): Access to the requested resource is denied despite valid authentication.

  • 404 (Not Found): The requested resource does not exist.

  • 405 (Method Not Allowed): The HTTP method used is not allowed for this resource.

  • 409 (Conflict): The request conflicts with the current state of the resource.

  • 422 (Validation Error): The request is correctly formatted but includes data that does not meet validation rules.

  • 502 (Bad Gateway): The API gateway received an invalid response from the server.

You can find these error codes, along with examples for each specific API request, in the OpusDNS API documentation.

Steps to resolve errors:

  1. Check your input carefully: Verify formats, lengths, required fields, and common typos.

  2. Review the API documentation: Ensure your request complies with all requirements.

  3. Check TLD Requirements: Different requirements apply depending on the registration or transfer of specific TLDs.

  4. Contact Support if needed: If you can’t identify the issue, reach out to our support team: