CloudConvert API vs iLoveAPI

CloudConvert API

API keys and OAuth tokens carry six scopes, the terms promise 99.9 per cent monthly uptime with refunds, and uploaded files are deleted within 24 hours. No OpenAPI document or changelog was found, and the per-credit price is drawn by a script on the pricing page.

iLoveAPI

Per-tool credit costs are public, 2,500 free credits arrive each month on a sign-up that asks for no card, and five official libraries are MIT. No OpenAPI file, status page or published rate-limit numbers were found, and the governing terms date from 14 February 2017.

CloudConvert API

1. Build each job from an import task, one or more processing tasks and an export/url task, then read the download links from the export task's result.files
2. Call GET /v2/operations with include=options to find the options a format pair accepts before creating a convert task
3. Do not retry a failed task automatically. CloudConvert retries retryable errors itself, and a retry endpoint creates a new task
4. Download output within 24 hours. Tasks, files and export URLs are deleted after that
5. Use https://sandbox.api.cloudconvert.com/v2 for tests. It consumes no credits and accepts only a fixed set of approved test files

iLoveAPI

1. Run four calls per job. GET /v1/start/{tool}/{region} returns a server and a task, then send upload, process and download to that server
2. Sign a JWT with the project secret key and send it as Authorization: Bearer. Tokens expire after one hour
3. Download results promptly. The reference says files are deleted one to two hours after processing, depending on tier
4. Back off exponentially on 429 and read the rate-limit headers on each response. No limit numbers are published
5. Add debug=true to any request to have the server echo the parameters without processing or spending credits