Authorization token
All API calls require a Bearer token in theAuthorization header.
Format
How to get your token?
After service contracting, you will receive:Production token
Development token
For testing
Corresponding endpoints
Token security
Important:- Never expose your token in client code (browser JavaScript)
- Store it as environment variable or secret
- Rotate it periodically
- Use different tokens for development and production
Optional headers (recommended)
Doctor and patient identifiers
For traceability and regulatory compliance:- Access auditing
- Debugging and technical support
- GDPR/HIPAA compliance
- Usage analytics
Note
These identifiers should be sent as HTTP headers, not in the request body. The Codify API uses headers for tracking metadata to keep the request body focused on the medical content.Available environments
Development
URL: Provided upon direct request Features:More relaxed rate limits
Do not use for real patient data
More verbose logs for debugging
No SLA guarantees
No per-request costs
Development and initial integration
JSON schema testing
Workflow validation
Automated testing
Production
URL: Provided after deployment (customized per client) Features:High availability (99.9% SLA)
Guaranteed processing
24/7 support
Metrics and monitoring
HIS/EHR system integration
Real data processing
Production workflows
HTTP client configuration
Timeouts and retries
For timeout configuration and retry strategies with exponential backoff, see Retry strategy. Basic recommendations:- Timeout: 600 seconds (10 minutes) for Codify API
- Retries: 3 attempts for 5xx and 429 errors
- Exponential backoff: 1s, 2s, 4s…
Additional headers
Content-Type
Should always beapplication/json: