QR API Request Errors

This article provides an overview of common errors encountered when making API requests to QR API, along with their meanings and how to resolve them.

Introduction

When making API requests to QR API, it's important to understand the various errors that may arise. These errors can occur due to issues like incorrect request formatting or authentication failures. Knowing how to identify and resolve these errors will help ensure smooth and successful API interactions.

A. 400 Bad Request

• Description: This error occurs when the request made to the API is invalid or malformed. The server cannot process the request due to incorrect syntax or missing required parameters
• Example Response:

  {
  "message": "string",
  "code": "string",
  "statusCode": 0
  }

• Common Causes:
  • Incorrect URL endpoint
  • Missing required parameters in the request
  • Invalid data format (e.g., JSON structure errors)
• Resolution:
  • Double-check the API documentation to ensure that the request format and endpoint are correct
  • Verify that all required parameters are included and correctly formatted

B. 401 Authentication Failed

• Description: This error occurs when the API request fails to authenticate. It typically happens when the API key is missing, invalid, or expired
• Example Response: 

  {
  "message": "string",
  "code": "string",
  "statusCode": 0
  }

• Common Causes:
  • Missing API key in the request header
  • Incorrect or expired API key
  • Unauthorized access attempt with an invalid API key
• Resolution:
  • Ensure that the correct API key is included in the request header
  • Verify the API key's validity and renew it if necessary
  • If using an expired key, reactivate it by starting a subscription plan

C. General Tips for Handling API Request Errors

• Logging: Implement logging to capture error responses and diagnose issues quickly
• Retry Mechanism: For temporary issues, implement a retry mechanism in the application to resend the request after a short delay
• Refer to Documentation: Always refer to the API documentation for detailed information on required parameters, authentication methods, and correct request formats

If you have any questions, you can explore more topics in this knowledge base or contact our support team at support@qrapi.io.