UniSea API Usage Guidelines

We provide API access so customers can connect UniSea to their own systems.
These guidelines keep the service stable for all customers.

1. Usage limits

The API limits how many requests you can send and how large each request can be.

• Too many requests return HTTP 429 (Too Many Requests).
• Request bodies over the size limit return HTTP 413 (Payload Too Large).
• Large result sets must be fetched with pagination.

2. Responsible use

Client applications must:

• use pagination and filters instead of fetching complete datasets
• cache data that rarely changes
• on HTTP 429 or 503, wait for the time given in the Retry-After header before retrying
• on other temporary errors, retry with exponential backoff and jitter

3. Prohibited use

The following is not permitted:

• load, performance or security testing without prior written agreement with Unisea
• systematic bulk extraction of data beyond the agreed purpose
• attempts to get around usage limits or access controls, including by using multiple keys or accounts
• sharing API keys with third parties

4. API keys

You are responsible for all use of your API keys. Store keys securely. If you suspect a key has been compromised, rotate it immediately.

5. Enforcement

If your usage affects service stability or breaks these guidelines, Unisea may throttle or temporarily suspend access without prior notice. We will notify you as soon as possible.

6. Changes and availability

Endpoints may be changed or deprecated. We will announce significant changes with reasonable notice. Availability is guaranteed only as set out in your agreement with Unisea.