Data quality and limits

Use the APIs as directory lookups, not as government-issued certifications. The source guides describe what evidence supports each service.

Locations

Locations combine source-scoped identifiers with an interpreted administrative hierarchy. An older official code can remain useful even when a newer law changes a place's kind or parent. Do not infer that a missing feature in a geometry layer means a place was legally abolished.

Check the active /v1/catalog response for releaseId, knownThrough, qualityStatus, and its release hash. Publication time, source knowledge, and legal effective dates have different meanings; a recent API deployment doesn't make older source information current.

The currentness report states its own evidence cutoff and known conflicts. The source assessment explains source ownership and identifier schemes. For a specific place, use the provenance endpoint in the locations reference.

Taxpayers

Taxpayer name search returns only the tax identifier and registered and commercial names. Exact lookup returns those identity facts together with the registration and checksum classifications, plus available DGII facts such as payment regime, category and electronic-invoicer flag. Missing facts are null; isElectronicInvoicer: null means unknown, while false means the source reported no. Registration state, checksum classification and electronic-invoicer status answer different questions. None is proof of current tax compliance.

An older publication does not by itself cause a 503 response. A last-known record remains available when a newer publication omits the taxpayer. Publication dates, retrieval timestamps and source evidence remain internal; they do not establish when DGII last updated an individual taxpayer. The API does not currently have that authoritative update date and does not return updatedAt. Missing or unavailable profile facts are null; an unknown electronic-invoicer flag must not be treated as false. A temporary failure must not become a negative registration decision.

Name search covers registered and commercial names in the current publication. Searching by identifier can also return a last-known record. Neither search mode calls the DGII form. No matches does not establish non-registration; confirm the selected identifier with exact lookup. Follow response cache headers, with successful responses cacheable for up to 60 seconds.

MICM certification is a separate source available only to authenticated services through the directory API. Its publication, issue and expiry dates are independent of DGII dates. Expired certificates may still be returned with their dates; a null certificate does not establish that a company is uncertified. See the taxpayer guide for fields and access boundaries.

Fuel prices

Fuel prices are qualified from MICM's officially published weekly resolutions. Amounts are decimal strings in DOP, and every record names its unit, sale stage, and inclusive effective interval. Product catalog coverage and a current price are separate claims; a product can have historical records without a usable current schedule. An expired current schedule returns 503 rather than presenting an old value as current.

The historical archive has gaps and unresolved source classifications. An empty date range does not show that a price stayed unchanged, and the service does not calculate between units such as MMBTU and CUBIC_METER. Natural-gas delivery modes and sale stages identify different markets. Read the fuel prices quickstart and fuel prices reference before using records for pricing or compliance decisions.

Responsible use

Use the minimum records needed for your workflow. Avoid unnecessary storage or publication of personal identifiers, and don't treat public-source availability as permission for every downstream use.

Both APIs are read-only. Cache successful responses, avoid bulk enumeration, and handle temporary unavailability. This initial free public service does not promise an SLA or an unlimited request quota.

A first request may take longer while the database resumes.

Documentation provenance

The detailed source guides below are rendered from pinned service-repository revisions. Their original Markdown and SHA-256 hashes are published in the documentation source manifest. API contracts are available as OpenAPI JSON, with original contract hashes in the service index.

Each guide's evidence dates describe its assessment, not today's API deployment.

The service repositories are private. Public source-guide excerpts are available here without repository access; deployment runbooks and unpublished review artifacts remain maintainer-only. No original source PDFs or downloadable catalog databases are distributed by this portal.