Skip to main content

Authorization token

All API calls require a Bearer token in the Authorization header.

Format

How to get your token?

After service contracting, you will receive:

Production token

Development token

For testing

Corresponding endpoints

Token security

Never expose your token in client-side code (browser JavaScript). Store it as an environment variable or secret, rotate it periodically, and use different tokens for development and production.

Doctor and patient identifiers

For traceability and regulatory compliance:
Usage:
  • Access auditing
  • Debugging and technical support
  • GDPR/HIPAA compliance
  • Usage analytics
Note: These identifiers are logged for auditing purposes but do not affect request processing.

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

Recommended usage:

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

Recommended usage:

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 be application/json:

User-Agent (optional)

Recommended to identify your application:

Complete configuration example

Python

JavaScript (Node.js)


Security and best practices

Use environment variables for tokens

Hardcode tokens in source code

Implement appropriate timeouts

Expose tokens in client (browser)

Configure automatic retries

Share tokens between environments

Always use HTTPS

Disable SSL certificate validation

Include doctor/patient identifiers for auditing

Ignore authentication errors


Next steps

Request/response structure

View examples

Error handling