Skip to main content
This section covers the key concepts for working with the PDFEcho API, including authentication, response codes, and rate limits.

​
🧩 Base URL

The API follows REST principles and enforces HTTPS for all requests to ensure data security and privacy. HTTP is not supported. 
https://api.pdfecho.com

​
🔐 Authentication

PDF Echo uses HTTP Basic Authentication for all API requests.
Your API key is used as the username, and the password must be left blank. Here’s how to authenticate using curl: 
curl https://api.pdfecho.com/v1/pdf \
  -u YOUR_API_KEY:
💡 Note: The colon (:) after your API key is required — it indicates an empty password.
Keep your API key secure and never expose it in client-side code or public repositories.

​
📡 Response Codes

We use standard HTTP status codes to indicate the result of API requests:
  • 2xx — Success
  • 4xx — user-related error (e.g., invalid parameters or authentication)
  • 5xx — Infrastructure issues.
StatusDescription
200Request completed successfully.
400Invalid request. Check your parameters.
401Missing API key.
403Invalid API key.
404The requested resource could not be found.
429Too many requests - rate limit exceeded.
5xxIndicates an error with our servers.
For a full list of possible errors, check the Error Codes section.