One REST API for the same file work your team does in the app.
Archive, PDF, conversion, optimization, and toolkit jobs over HTTP. Idempotency keys, quote-before-run pricing, async polling, and webhooks ship as guarantees — not as marketing words. Same engine as the dashboard, same workspace, same bill.
One REST API for the same file work your team does in the app.
Archive, PDF, conversion, optimization, and toolkit jobs over HTTP. Idempotency keys, quote-before-run pricing, async polling, and webhooks ship as guarantees — not as marketing words. Same engine as the dashboard, same workspace, same bill.
What it covers
- Generate an API key: Create credentials in the authenticated workspace when the workflow is ready to move from manual runs to backend automation.
- Submit the file job you actually need: Call the platform workflow for archive extraction, packaging, optimization, conversion, PDF actions, async processing, or connector-aware operations.
- Retrieve status, artifacts, and usage from the same system: Use the canonical job and artifact model instead of rebuilding billing, result retrieval, and support visibility outside Eazier.
Trust points
- One engine — the dashboard and the API call the same edge functions and workers.
- API keys, usage, and billing live in the same workspace as the team's manual runs. No second console.
- Async jobs, artifacts, and connectors share one model with the in-app history.