Error Messages Reference¶
Guide to Dxtra platform error messages with explanations and resolution steps.
API Authentication Errors¶
401 Unauthorized¶
Your authentication credentials are missing, invalid, or expired.
Error example:
Solution: 1. Include the Authorization header in your requests 2. Format: Authorization: Bearer YOUR_JWT_TOKEN 3. Generate a new API key from Dashboard > Settings > API Keys if needed
Error example:
Solution: 1. JWT tokens expire after 1 hour for security 2. Exchange your API key for a fresh JWT token:
curl -X POST https://auth.dxtra.ai/v1/signin/pat \
-H "Content-Type: application/json" \
-d '{"personalAccessToken": "YOUR_API_KEY"}'
- Use the new
accessTokenfrom the response
Error example:
Solution: 1. Verify your API key is correct (no extra spaces/characters) 2. Check if the API key has been revoked or expired 3. Generate a new API key from the Dashboard 4. Ensure you're using the correct Data Controller's API key
403 Forbidden¶
Your credentials are valid, but you lack permission for the requested action.
Error example:
Solution: 1. Check your current role in Dashboard > Settings > Team 2. Required permissions by action: - View data: Viewer role or higher - Modify settings: Editor role or higher - Manage integrations: Administrator role or higher - Manage team: Administrator role or higher 3. Ask an Administrator to upgrade your role if needed
Error example:
Solution: 1. Verify you're using the correct API key for the intended Data Controller 2. Check if you have access to the specific Data Controller in the Dashboard 3. Ensure the X-Hasura-Role header is set correctly (usually user)
500 Internal Server Error¶
An unexpected error occurred on our servers.
Immediate actions:
- Retry Request: Wait 30 seconds and try again (temporary issues often resolve quickly)
- Check Request Format: Ensure your request payload is valid JSON
- Contact Support: If error persists, note the timestamp and request details
Report Server Errors
Server errors (5xx) are logged automatically, but reporting helps investigation. Include:
- Timestamp of the error
- Request URL and method
- Request payload (remove sensitive data)
Integration Errors¶
Connection Failures¶
Error: Failed to connect to Shopify store
| Issue | Solution |
|---|---|
| Invalid Shop Domain | Use format your-shop.myshopify.com (not .shopify.com) |
| Incorrect Access Token | Regenerate token in Shopify Admin > Settings > Apps |
| Missing Permissions | Grant: read_customers, read_orders |
| Shopify Plan Limits | Some plans have limited API access |
Error: Failed to authenticate with Mailchimp
| Issue | Solution |
|---|---|
| Expired API Key | Generate new key in Mailchimp > Account > Extras > API keys |
| Wrong Data Center | API key suffix (e.g., us1, us2) must match your account |
| Account Suspended | Contact Mailchimp support for account status |
| Rate Limits | Wait 10 minutes before retrying connection |
Error: Stripe webhook validation failed
| Issue | Solution |
|---|---|
| Wrong Webhook URL | Use: https://conduit.dxtra.ai/integrations/stripe/event?did=YOUR_DID&dxKey=YOUR_KEY |
| Missing Webhook Events | Enable: customer.created, customer.updated, customer.deleted |
| Incorrect Signing Secret | Copy signing secret exactly from Stripe Dashboard (starts with whsec_) |
| HTTPS Required | Webhook endpoints must use HTTPS |
Webhook Signature Errors¶
Each integration uses different signature validation:
| Integration | Signature Type | Header |
|---|---|---|
| Shopify | HMAC-SHA256 (Base64) | X-Shopify-Hmac-Sha256 |
| Stripe | Stripe Signature | Stripe-Signature |
| Mailchimp | Query params (did, dxKey) | N/A |
Common signature errors:
Invalid signature: Webhook secret is incorrect or body was modifiedSignature verification failed: Check that raw request body is preservedMissing signature header: Platform isn't sending signature headers
Data Synchronization Issues¶
Error: Data sync failed
Troubleshooting steps:
- Check Integration Status:
- Go to Dashboard > Integrations
- Look for warning icons or error messages
-
Click "View Details" for specific error information
-
Common sync issues:
| Status | Meaning | Solution |
|---|---|---|
| Rate Limited | Too many API calls | Wait 1 hour, sync will resume automatically |
| Authentication Failed | Credentials expired | Reconnect integration with fresh credentials |
| Paused | Manual pause or error | Click "Resume" or fix underlying issue |
| Processing | Sync in progress | Allow up to 30 minutes for large datasets |
- Manual Sync Options:
- Click "Sync Now" for immediate retry
- "Reconnect Integration" for authentication issues
- "View Logs" for detailed error information
Error: Invalid data format detected during sync
Resolution steps:
- Identify problematic records:
- Check integration logs for specific record IDs
-
Look for patterns (e.g., missing required fields)
-
Common data issues:
- Empty or null required fields (name, email)
- Invalid email format
- Unsupported characters in data
-
Date format mismatches
-
Fix at the source:
- Clean data in the third-party service
- Retry sync after data correction
Website Integration Errors¶
Consent Widget Issues¶
Error: Dxtra consent widget failed to load
Debugging checklist:
- Script URL: Verify
https://transparencycenter.dxtra.ai/embed.jsis accessible - Domain Verification: Ensure your domain is added to Data Controller settings
- HTTPS: Consent widgets require HTTPS websites
- Content Security Policy: Add
transparencycenter.dxtra.aito allowed domains - Ad Blockers: Test with ad blockers disabled
Testing script:
<script>
console.log('Loading Dxtra widget...');
const script = document.createElement('script');
script.src = 'https://transparencycenter.dxtra.ai/embed.js';
script.onload = () => console.log('Widget loaded successfully');
script.onerror = () => console.error('Widget failed to load');
document.head.appendChild(script);
</script>
Error: Consent preferences not being saved
| Issue | Solution |
|---|---|
| Third-party cookies disabled | Widget requires first-party cookies |
| Privacy modes | Test in normal browser mode |
| Cache issues | Clear browser cache and cookies |
| JavaScript errors | Check browser console for error messages |
| Multiple widgets | Only one widget instance per page |
Getting Additional Help¶
Error Not Listed?¶
Can't find your specific error?
Before contacting support:
- Search Documentation: Use Ctrl+K to find specific errors
- Browser Console: Check developer tools for additional error details
- Test Environment: Try reproducing in a different browser
Support Information to Include¶
Help us help you faster
When contacting support, include:
- Error Message: Exact text of the error
- Timestamp: When the error occurred (including timezone)
- Request Details: URL, method, and payload (sanitize sensitive data)
- Browser/Environment: Browser version, operating system
- Steps to Reproduce: What you were trying to do when the error occurred