Troubleshooting

Causes

• Invalid JSON format
• Missing required fields

Solutions

• Validate JSON format
• Check required fields in API docs

Causes

• Missing or empty Authorization header
• Invalid API key format (should be tm_test_xxx... or tm_live_xxx...)
• API key has been deactivated by the endpoint owner

Solutions

• Include Authorization header (e.g., Bearer tm_test_xxx...)
• Use tm_test_xxx... for Sandbox, tm_live_xxx... for Production
• Regenerate key if needed
• Contact the endpoint owner to reactivate your API key

Causes

• Endpoint is deactivated
• Subscription expired or monthly quota exceeded
• Production not deployed (tm_live_ key used)
• This API key belongs to a different endpoint (keys are issued per endpoint)

Solutions

• Verify endpoint is active
• Check subscription status
• Deploy to Production if using tm_live_ key
• Use the API key issued for the endpoint in the URL, and verify the slug is correct

Causes

• Request body exceeds the 100KB size limit
• Large nested arrays or strings in the JSON payload

Solutions

• Reduce payload size by removing or trimming large fields
• Split into multiple smaller requests if the data is genuinely large
• Contact support@3minapi.com if 100KB is insufficient for your use case

Causes

• Missing or wrong Content-Type header
• Content-Type must be application/json

Solutions

• Add header: Content-Type: application/json

Causes

• Monthly request limit exceeded

Solutions

• Upgrade plan or wait for monthly reset
• Monitor usage in dashboard

Includes 500 (Internal Server Error), 502 (Bad Gateway), 503 (Service Unavailable), etc.

Causes

• Temporary server issue
• Upstream service (database) temporarily unavailable
• Service temporarily overloaded or under maintenance

Solutions

• Implement retry with exponential backoff (e.g., 1s → 2s → 4s, max 3 attempts)
• Check service status if errors persist
• Contact support if issue persists: contact@3minapi.com
• Note: 5xx means the request was not received. Once you get 202 Accepted, data processing is guaranteed.

• Verify webhook URL is correct
• Use HTTP or HTTPS URL
• Endpoint must be publicly accessible
• Check webhook status in logs

• Return 2xx whenever you received the delivery — even if your own processing failed
• Respond within 15 seconds
• The system retries automatically for hours — but only for 5xx, 429, and timeouts. A 4xx other than 429 is never retried
• Webhook retries may delay data processing