Authentication

Secure your API requests and access higher rate limits by authenticating with Flimpa.

API Keys

To authenticate with the Flimpa API, you must provide your API key in the X-API-Key HTTP header. You can manage your API keys in the Flimpa developer dashboard.

Keep your keys secure

Your API keys carry many privileges. Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.

bash

curl -X POST https://api.flimpa.com/api/v1/tasks \
  -H "X-API-Key: your_api_key_here" \
  -F "operation=compress-pdf" \
  -F "file=@/path/to/document.pdf"

Task Access Tokens

When you create a task, the API returns a unique accessToken. This access token is required to check the status of the task and download the result. It ensures that only the creator of the task can access its data.

Pass this access token in the X-Task-Access-Token header for all subsequent requests related to that specific task.

bash

curl -X GET https://api.flimpa.com/api/v1/tasks/550e8400-e29b-41d4-a716-446655440000 \
  -H "X-Task-Access-Token: 1735689600000.a1b2c3d4e5f6..."

Anonymous Access

The Flimpa API allows anonymous access for testing and light usage. If you omit the X-API-Key header, your requests will be subject to stricter rate limits (e.g., 20 creations per hour).

For production applications, we strongly recommend using an API key.