Skip to main content
Version: v1

Paradarum CDN API

The Paradarum Developer API lets you automate your CDN: purge cache, manage properties and rules, pull statistics, and open support tickets from your own tooling or CMS plugins.

Base URL​

https://api.paradarum.com

All paths are prefixed with /api and are case-insensitive (/api/property and /api/Property are equivalent). There is no version segment in the URL.

Authentication​

There are two ways to authenticate. Most automation should use an API key.

ModeHeaderUse it for
API keyX-API-Key: pdm_…Automation, CMS plugins, cache purge. Create keys in the panel under Account → API Keys.
Bearer (JWT)Authorization: Bearer <jwt>The panel / interactive sessions. Obtain a token from POST /api/auth/login.

Send the raw key as the X-API-Key value — there is no Bearer word for API keys. Your account is derived from the credential, so you never send an accountId for property or purge endpoints (the Tickets endpoints are the exception and take an accountId query parameter).

Response envelope​

Every response is wrapped in a standard envelope:

{
  "succeeded": true,
  "message": "",
  "data": { },
  "pageNumber": 1,
  "pageSize": 10,
  "totalPages": 1,
  "totalRecords": 1
}

succeeded is true for any HTTP status below 400. There is no machine-readable error code — branch on the HTTP status and read message. The pagination fields are only meaningful on list endpoints.

Rate limits​

No rate limiting is enforced on the public API today. Purge is asynchronous: a 200 with a jobCount means the purge was queued, not that the cache is already cleared.

Authentication​

Send your raw API key (pdm_…) as the header value.

Security Scheme Type:

apiKey

Header parameter name:

X-API-Key