API V2 Overview

Quick Start

The EditingTools.io API can be used to generate, convert, manage and process data on EditingTools.io. It provides access to various resources via a REST interface. All request parameters and results are encoded in UTF-8. HTTP error codes are used to signal errors. Authentication is based on fixed keys, and data transport is secured by SSL.

Whats new in Version 2?

• The API allows now multiple API keys for each EditingTools.io account.
• The API allows rights management for API keys, which makes it possible to control what they can do.
• The API now supports localized language output.
• The output JSON structure was streamlined, and more data was added.
• Better API documentation and more examples.
• Better error handling.
• Callbacks (for Processes)
• Outputs provides now UTC (ISO 8601) timestamps.

API KEY

The new API version supports the use of multiple API KEYs for each EditingTools.io account.

User-Related

Access user-related data, such as generated files and processes, via the API.

Tools

Integrate our tools into your workflow using our individual APIs.

Endpoint URL

The endpoint URL for the API version 2 always begins with:

https://api.editingtools.io/v2

Authentication

This API requires Basic Authentication. The "Authorization" header should be set with the Base64 encoded string of "apikey:YOUR_API_KEY".

Authorization: Basic <base64Encoded(apikey:YOUR_API_KEY)>

Data Handling

Request parameters must be UTF-8 encoded. Results are returned as UTF-8-encoded JSON. By default, datasets will be inside the data tag.

Error Handling

This API service uses standard HTTP response codes to indicate whether a method was completed successfully. HTTP response codes in the 2XX range indicate success. Responses in the 4XX range indicate some sort of failure, while responses in the 5XX range indicate an internal system error that cannot be resolved by the user. The following error codes are used by the API:

Rate Limits

To prevent abuse and spam, the API has limits at various levels. If you receive error code 429 (Too Many Requests), it means you have reached a rate limit.

If you receive a rate limit error, you should stop making requests temporarily. If the retry-after response header is present, you should not retry your request until after that many seconds has elapsed. To prevent rate-errors, we recommend to wait 300 ms to 800 ms between requests to the same endpoint.

Also there is a general limit to the api and all requests made:

The general limits per minute and per hour can be changed upon request.

Upload Limits

The maximum upload size for any single request — including file uploads — is 100 MB. This is a hard limit and applies regardless of your API plan or usage level.

If your request exceeds this size, it will be rejected before reaching our servers. To ensure successful uploads:

• Make sure uploaded files are under 100 MB.
• For larger media, consider splitting files before upload.
• Requests close to the limit may still fail due to encoding or header overhead.

Timezone

This API endpoint returns the time as an ISO 8601 timestamp in the UTC time zone. These timestamps look like 2025-01-10T15:05:06Z.

Localization and Languages

This API supports multiple languages. For instance, it can display the text of a status message in a different language.

Accept-Language: LANGUAGE

Example

To set the preferred response language to Spanish, add this header:

Accept-Language: es

cURL Example

To apply the language in a cURL request, add the following header:

-H "Accept-Language: es"

Available Languages

The following list contains all the currently available languages. Note that setting a language header does not guarantee a translated response, as not all texts are translated. If no language is set or a translation is unavailable, the default response will be in English.