Integrate with clear data and limits.
The API provides informational rates. Production readiness is being validated; the objectives below are not a contractual SLA or a guarantee for payments or fiscal documents.
Server-side access
Send Authorization: Bearer from your backend. Keep keys in a secret store. Production applications share 1,000 requests per Dominican day and 60 per minute per account. Test keys have separate counters and cannot access live data. Each application supports two keys and a temporary third during a 24-hour rotation.
Rates and dates
Quote buy/sell describe the entity's perspective; operation=buy/sell describes the user's action. Use decimal arithmetic and preserve decimal strings. Missing sides are null, never zero. Retain id, entityId, channel, kind, provenance, effectiveDate, publishedAt, datePrecision, lastCheckedAt and expiresAt.
A recent check is not a recent publication. Unknown source dates remain unknown. General source checks run at 08:00, 12:00 and 17:00 America/Santo_Domingo. Consult /v1/coverage and use freshness=current or freshness=stale. Commercial rankings exclude official references and expired quotes.
Errors and caching
200 with empty data means no matching records; 503 means a required dependency is unavailable. For 429, honor Retry-After. Retry temporary failures with backoff, jitter, a timeout and at most three attempts. Keep X-Request-Id for support, never Authorization.
Use ETag with If-None-Match for 304 responses. Conditional requests still authenticate and consume quota. Authenticated responses are not shared-cacheable. JSON pagination exposes Link relations; numeric cursors are not immutable snapshots.
Backend integration
Fetch from the backend, display the source date and state, preserve provenance and handle absent or expired rates explicitly. Payment conversion and fiscal documents require a separate agreement on the applicable source, date and rules.
Objectives and versions
Targets: 99.9% monthly availability, successful-read p95 below 500 ms and 99% of cycles terminal within 30 minutes. Thirty days of external observation are required before opening. No contractual SLA or human 24/7 support is promised.
v1 retains routes, defaults and JSON/XML. Breaking changes require a new version. Mandatory keys require verified onboarding and a fixed 14-day announcement.