Skip to main content
The public DNC LATAM API is versioned in the URL path. v1 and v2 are current, supported contracts. Adding v2 did not deprecate v1. Choose the version that matches the job: small synchronous batches on v1, larger or wait-tolerant work on v2. The live machine-readable contract is OpenAPI 3.1 (also on the marketing host).

​
Compatibility

Additive, backward-compatible changes can ship inside the current URL version: new optional fields, new error codes in the published taxonomy, and new headers. Removing or renaming a field, changing a status code meaning, or tightening a limit in a way that rejects previously valid requests is a breaking change.

​
How deprecation is signaled

When a URL version, operation, or field will be removed:
  1. The OpenAPI document marks it deprecated: true.
  2. HTTP responses for that surface add a Deprecation header (true, or an RFC 8594 date).
  3. When a removal date is known, responses also add a Sunset header (HTTP-date) and the docs page for that version states the same date.
  4. This policy page and the OpenAPI info description link the timeline.
No v1 or v2 operation is deprecated today. There is no announced sunset date for either version.

​
What will not happen without notice

DNC LATAM will not silently replace v1 with v2, change the meaning of safe_numbers_to_call, or drop a published error code without the deprecation headers and a documented sunset window. Questions: hello@dnclatam.com.