Skip to main content

REST API

Data​

DataMaxi+ currently supports the following datasets through the REST API.

Authentication​

Private endpoints are protected by an API key, which you can obtain upon registering at https://datamaxiplus.com/login. To learn more about REST API authentication you can refer to the Authentication page.

Limits​

Rate limits are enforced per API key, per minute. The exact cap depends on your plan:

PlanRate limit
Free10 requests / minute
Starter40 requests / minute
Pro60 requests / minute
Pro+1000 requests / minute

Unauthenticated and public metadata requests (those made without a valid API key) fall back to a default of 10 requests / minute.

Rate limits are enforced to ensure fair usage of the API, so it's important to monitor and control the frequency of your requests to avoid hitting these limits.

Exceeding the limit​

When you exceed your limit, the server responds with HTTP status code 429 and the following JSON body:

{ "error": "rate limit exceeded" }

Every 429 carries a Retry-After: 60 header, indicating the number of seconds to wait before retrying. This applies to both the public metadata endpoints (ping and server time) and the credit-metered data endpoints (CEX, Premium, Forex, and so on).

Rate-limit headers​

Data API responses carry the standard rate-limit trio — on successful responses and on 429s alike:

HeaderMeaning
x-ratelimit-limitYour cap for the current window, in requests per minute.
x-ratelimit-remainingRequests left in the current window.
x-ratelimit-resetUnix timestamp (epoch seconds, UTC) at which the window resets.

Pace your requests using x-ratelimit-remaining and x-ratelimit-reset rather than by counting locally, and honor Retry-After when you do receive a 429. Treat the headers as advisory: they are omitted in the rare case where the limiter backend is unavailable, so your client should tolerate their absence.