Skip to main content

How to Contact Support

For any issues, questions, or assistance, our support team is available to help. You can reach us through the following channels: Email Support: support@explorium.ai Slack Channel: If you have a dedicated Slack channel with us, you can post your question there.

Submitting a Support Request

To help us resolve your issue efficiently, please provide the following details when submitting a request:
  1. Steps to Replicate: Describe the exact steps you took before encountering the issue.
  2. API Endpoint Used: Specify which API endpoint you were using.
  3. Exact Request Sent: Include the request payload.
  1. Expected Response: What result did you expect to receive?
  2. Actual Response: Provide the actual response you received.
  1. Error Message (if any): Copy and paste any error message you encountered.
  2. Correlation ID (if available): This can be found in the API response and helps us track your request faster.

Example Support Request:

Credit Usage Policy:

  • If a request returns an error (e.g., 403 Forbidden, 400 Bad Request), no credits will be deducted.
  • If a request returns no results (i.e., no relevant data is available for the given parameters), no credits will be deducted.
  • Credits are consumed only when valid, billable data is returned from the API.

Common Issues & Troubleshooting

I received a 403 Forbidden error.

  • Check if your API key is valid and has sufficient permissions.
  • Ensure you have available credits for the requested operation.
  • If using a protected endpoint, confirm you have the necessary access rights.

I received a 400 Bad Request error.

  • Verify that all request parameters are formatted correctly.
  • Ensure the required fields are included in the request.

I received a 429 Too Many Requests error.

  • You have exceeded the rate limit for API calls. Implement exponential backoff before retrying.
  • Monitor your API usage and consider upgrading your plan if needed.

I received a 500 Internal Server Error.

  • This could indicate a temporary issue on our side. Try again later, and if the problem persists, contact support with your correlation ID.