Skip to main content

Troubleshooting

This guide helps you resolve common issues when working with the OneSource Web3 API.

Authentication Errors​

Invalid API token or Status Code 401​

If you receive this error:

  1. Check API key format to ensure your key starts with BP- followed by 26 characters (i.e., BP-12345678912345678912345678).

  2. Verify header implementation:

    // Correct implementation
    headers: {
      "Content-Type": "application/json",
      "x-bp-token": "BP-12345678912345678912345678"  // Note the exact case of "x-bp-token"
    }

  3. Confirm your subscription status by logging in to your OneSource Dashboard to verify your API key is active and hasn't expired.

  4. Test your API key with a playground to determine if the issue is with your query or the API itself.

Query Error​

Cannot query field X on type Y​

This error occurs when your query references fields that don't exist in our schema. To resolve:

  1. Check field spelling to ensure field names match exactly what's in our schema.
  2. Review schema changes in the GraphQL Schema.
  3. Use Apollo Sandbox to help build valid queries.

Rate Limiting​

Rate limit exceeded​

If you hit rate limits:

  1. Implement caching - if you’re making the same requests over and over, caching the results can cut down on requests.
  2. Optimize queries - only ask for the data you actually need with smaller, focused queries.
  3. Upgrade your plan - if you consistently hit limits, you may need to move to a higher-tier plan that offers higher limits.

Still Need Help?​

If none of the above helps, contact support at support@onesource.io with:

  • The full request you're making.
  • Any error messages you're receiving.