Support

Need help with the Travelmode API? Here's how to get assistance.

Documentation

• API Overview - Start here
• Authentication - API key setup
• Error Handling - Troubleshooting errors
• Best Practices - Tips for success

Common Issues

"401 Unauthorized"

Possible causes:

• Missing Authorization header
• Invalid or expired API key
• Revoked API key

Solutions:

1. Verify your API key is correct
2. Check the Authorization header format: Bearer tm_your_key
3. Generate a new key from the Developer Portal

"429 Too Many Requests"

Cause: Rate limit exceeded

Solution: Wait for the Retry-After header duration, then retry with exponential backoff.

"409 Conflict"

Cause: Revision mismatch in v1 API operations

Solution: Fetch the latest itinerary, get the current revision, and retry your operation.

Events Not Appearing

Possible causes:

• Event created on wrong trip
• Missing required fields
• Validation errors

Solutions:

1. Verify the tripId in your request
2. Check all required fields are included
3. Review the API response for error details

Debugging Tips

Check Your Request

curl -v "https://travelmode2.replit.app/api/trips" \
  -H "Authorization: Bearer tm_your_key"

The -v flag shows full request/response details.

Validate JSON

Ensure your request body is valid JSON:

echo '{"name": "Test"}' | jq .

Check Rate Limit Headers

curl -i "https://travelmode2.replit.app/api/trips" \
  -H "Authorization: Bearer tm_your_key" | grep X-RateLimit

Health Status

Check API availability:

curl "https://travelmode2.replit.app/api/health"

Contact

For additional support, reach out through the Developer Portal.