Service status

API
Operational

Authenticated v1 requests are available over HTTPS.

FORMAT
JSON · UTF-8

Dates use ISO 8601 and rates are quoted against DZD.

Your first request

Put your key in an environment variable, then request the latest EUR parallel-market rate.

curlLatest parallel rates
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 a request ID. Authenticated responses also expose burst and monthly quota headers.

Available data

Choose the smallest endpoint that answers your question. This keeps payloads and quota usage easy to reason about.

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 use exponential backoff with jitter.
Cache by freshness
Exchange-rate data changes less often than application traffic. Cache the response your product can safely reuse.
Log request IDs
Keep the returned X-Request-Id with errors so support can trace a request without seeing your key.