Skip to main content

​
Prerequisites

To use Para, you need an API key. This key authenticates your requests to Para services and is essential for integration.
Don’t have an API key yet? Request access to the Developer Portal to create API keys, manage billing, teams, and more.

​
Environments & Base Path

EnvironmentBase URLNotes
BETAhttps://api.beta.getpara.comInternal staging environment.
PRODUCTIONhttps://api.getpara.comRequires production keys.
  • All REST endpoints are versioned under /v1.

​
Auth & Headers

  • X-API-Key: your partner secret key (server-side only).
  • X-Request-Id (optional): supply a UUID for tracing—Para always returns one, generating it when omitted.

​
Allowlisting

Add IPs for any service calling the REST API via the Developer Portal (Security → Allowlist). Once the list has entries, requests from IPs outside it return 401 Unauthorized. Leaving the allowlist empty keeps access open to all IPs.

​
Quick Check

curl -i \
  -H "X-API-Key: sk_..." \
  https://api.sandbox.getpara.com/v1/_status
You should receive 200 with { "status": "ok" }. If you receive 401, verify your API key and confirm your calling IP is allowlisted (when an allowlist is configured).