FAQ

Q: How can I avoid hitting the rate limit?

A: Implement your application to keep the number of requests below 300 per hour. If this limit is insufficient, consider the following methods:

• Request Optimization: Use caching or batch processing to reduce unnecessary requests.

• Retry Mechanism: When receiving a 429 Too Many Requests error, implement an exponential backoff strategy for retries.

Q: How should I handle CORS errors?

A: To prevent CORS errors, implement one of the following solutions:

• Use a Proxy Server: Set up a proxy server using tools like Express or Nginx to relay requests.

• Call from the Server Side: Avoid making API calls from the frontend and instead call the API directly from the backend server to bypass CORS restrictions.

For a detailed explanation and solutions for CORS errors, refer to the Handling CORS Errors section.

Q: What should I do if I accidentally expose my API key?

A: Take the following steps immediately:

1. Disable the Exposed API Key: If your API key is exposed, contact our support team immediately to disable it.

2. Generate a New API Key: If necessary, create a new project to generate a new API key and securely store it in a safe location.

3. Review Your Code: Ensure that the API key is not explicitly included in public repositories or client-side code.

Q: What is the difference between the test environment and the production environment?

A:

• Test Environment (https://staging-qube.vercel.app)

  • Used for development and testing API implementations.

  • Test data is utilized, so it does not affect production data.

  • Data may be periodically reset.

• Production Environment (https://www.0xqube.xyz)

  • Used for live operational projects.

  • Handles real data, so ensure thorough testing in the test environment before using it.

For more details, refer to the Environment Segmentation section.

Q: What is the API response if the conversion point is inactive?

A: If the conversion point is inactive, the following response will be returned:

• Status Code: 200 OK

• Response Body:

{
  "message": "The specified conversion point is inactive.",
  "details": {
    "conversionId": "<Conversion ID>"
  }
}

This response indicates that no data has been recorded, and no reward calculations have been performed. Please check with the project administrator if necessary.

For more details, refer to this document.

Q: What should I do if the API returns a 500 Internal Server Error?

A: A 500 Internal Server Error indicates that an unexpected error occurred on the server.

• Wait for some time and try again.

• If the issue persists, contact Qube support with the error message and code for further assistance.

Q: How should I use the error.details field in the response?

A: The error.details field contains specific information about the error, such as the related field and the issue.

Example:

{
  "error": {
    "code": "INVALID_REVENUE",
    "message": "Revenue parameter is required for RevenueShare payment type.",
    "details": {
      "field": "revenue",
      "issue": "Revenue must be provided and should be a positive number."
    }
  }
}

Use this information to take the following actions:

• Identify the missing or invalid parameter based on the field name.

• Address the issue described in the issue field and resend the request.