Skip to main content
🤖 The Judit API DOES NOT use the Authorization: Bearer <token> standard. Authentication is performed exclusively by passing the key in a custom HTTP header named api-key. This applies to all endpoints and Base URLs of the Judit API.

1. How to Obtain Your API Key

Your API Key is the unique credential that links your requests to your account and contracted plan.
  1. Contact our commercial team via WhatsApp.
  2. Provide context: Explain your use case and expected request volume.
  3. Receive the Key: Your API Key will be sent securely to your registered email address.
⚠️ Security First: Treat your API Key as a plaintext password. Never expose it in public repositories (e.g., GitHub), front-end code (client browser), or mobile applications without obfuscation.

2. Authentication Standard (api-key Header)

In every request made to the Judit API, regardless of service or module (Queries, Tracking, etc.), you must include the api-key header.

Basic HTTP Request Example

Practical Implementation Examples

Below, we show how to perform an authenticated request using the Asynchronous Queries Base URL (https://requests.production.judit.io), consuming the key from environment variables.

3. Secure Management and Best Practices

To prevent leaking your credential, consolidate the management of your key by following these rules:

1. Use Environment Variables Exclusively

Never hardcode your API Key in the source code:

2. Configure Environment Variables

Linux/macOS:
Windows:
Docker:

3. .env File (Development)

4. Key Rotation

  • Monitor the use of your API Key regularly
  • Request a new key if you suspect it has been compromised
  • Implement rotation in critical environments

Authentication Error Handling

401 Error - Unauthorized

Possible causes:
  • API Key not provided
  • Invalid or expired API Key
  • Badly formatted api-key header
  • Usage limit exceeded

403 Error - Forbidden

Possible causes:
  • Valid API Key but without permission for the resource
  • Resource not available in your plan

API Key Validation

Connectivity Test

Usage Monitoring

Environment-Based Configuration

Configuration Class

Next Steps

Support: If you have authentication problems, contact our technical support.