ayanPDF
Sign in Create account
BayanPDF

PDF processing APIs for your systems

Build privacy-aware integrations with clear keys, scopes, and permissions.

Start with tools View plans
How integration works
  • Upload a file or create a job through `/api/v1`, then poll status until completion.
  • Use Idempotency-Key on retries so jobs or billing actions are not duplicated.
  • Receive a webhook when a job finishes and verify its signature before trusting the event.
Security and limits
  • API keys are shown once, stored as hashes, and can be disabled from the account.
  • Requests use manageable rate limits and scopes depending on plan.
  • Integration logs do not store file content, passwords, or extracted text.
What your team needs
  • A separate sandbox before production integration.
  • Clear error handling for queued, processing, completed, failed, and expired states.
  • A retention and deletion policy aligned with your users’ file sensitivity.
FAQ

Short answers

Is there a versioned API?

Yes, integration routes start at `/api/v1` so future versions can evolve without breaking integrations.

Should webhooks be verified?

Yes. Verify signatures and ignore duplicate or unexpected events.

Is file content logged?

No. Integration logs should not contain file content, extracted text, or passwords.