What api.exchangedz.com does

This is the customer-facing data gateway for EXDZ. It authenticates your API key, reads already-published market records from the production PostgreSQL database, applies scopes and quotas, and returns predictable JSON over HTTPS.

Reads published data

Authenticates requests, filters records, paginates results and tracks usage.

Does not run data jobs

Scraping and payment processing happen outside this read-only API.

Service contract

BASE URLhttps://api.exchangedz.com
VERSIONv1
FORMATJSON · UTF-8
QUOTEDZD

Your first request

Store your key in a server-side environment variable, then request the latest EUR parallel-market observation.

Request example
shellcURL
curl "https://api.exchangedz.com/v1/rates/latest?currency=EUR&source=parallel" \
  -H "Authorization: Bearer $EXDZ_API_KEY"
json200 response
{
  "data": [
    {
      "currency": "EUR",
      "names": { "en": "Euro", "fr": "Euro", "ar": "يورو" },
      "type": "currency",
      "source": "parallel",
      "quote": "DZD",
      "buy": 274.67,
      "sell": 277.17,
      "updatedAt": "2026-08-24T00:00:00.000Z"
    }
  ],
  "meta": {
    "requestId": "req_01J6EXDZ...",
    "count": 1,
    "source": "parallel",
    "quote": "DZD",
    "currencies": ["EUR"]
  }
}

Every response includes an X-Request-Id. Authenticated responses also expose burst and monthly quota headers.

Available data

Choose the smallest endpoint that answers your question. One valid request consumes one quota unit.

Production basics

Keep keys server-side
Never commit a key or place it in public browser code. Load it from a secret environment variable.
Handle 429 responses
Read Retry-After and retry with exponential backoff and jitter.
Cache by freshness
Rate data changes less often than application traffic. Cache responses for the period your product can safely reuse.
Log request IDs
Keep X-Request-Id with errors so support can trace a request without seeing your key.