Troubleshooting

This guide provides solutions to common issues you might encounter when using the DX Portal and APIs.

Authentication Issues

Invalid Client Credentials

Problem: You receive an "Invalid client credentials" error when trying to obtain an access token.

Solution:

• Verify that you're using the correct Client ID and Client Secret.
• Ensure that you're using the correct authentication endpoint for your environment.
• Check that your app has not been disabled or deleted.
• Make sure you're using the correct grant type (client_credentials).

Token Expiration

Problem: Your API requests fail with an "Invalid token" or "Token expired" error.

Solution:

• Access tokens have a limited lifespan (typically 1 hour).
• Request a new access token when the current one expires.
• Implement token refresh logic in your application to automatically obtain a new token when needed.

API Request Issues

Invalid Request Format

Problem: You receive a 400 Bad Request error when making an API call.

Solution:

• Check that your request body is properly formatted JSON.
• Verify that all required parameters are included.
• Ensure that parameter values are of the correct data type.
• Review the API documentation for the specific endpoint you're calling.

Authorization Errors

Problem: You receive a 403 Forbidden error when making an API call.

Solution:

• Verify that your access token is valid and has not expired.
• Check that your app has been granted access to the API you're calling.
• Ensure that you're including the correct headers in your request.
• Verify that you have the necessary permissions for the operation.

Environment-Specific Issues

Sandbox Environment

Problem: Changes made in the Sandbox environment are not reflected in Production.

Solution:

• The Sandbox environment is separate from Production.
• Changes made in Sandbox do not affect Production data.
• This is by design to allow safe testing without impacting production systems.

Common Error Codes

Getting Additional Help

If you're still experiencing issues after trying the solutions above, visit the Support page for additional resources.