DAVATEL API Migration (One-time)

Service Agreement 2026-08-11 · API v1.1

Objective

This update synchronizes the API with the current DAVATEL form. To avoid the need for future modifications, do not use a static form; instead, refer to the dynamic endpoints for fields and requirements.

Workflow to be implemented

  1. GET /api/v1/order-fields
  2. The customer selects a primary plan and any additional services.
  3. POST /api/v1/order-requirements
  4. Display exactly the fields/requirements returned.
  5. POST /api/v1/orders such as multipart/form-data.
  6. Save the referencia returned data and consult GET /api/v1/orders/:referencia.

New mandatory checks

Compatibility

Example of product details

[
  {
    "tarifa_id": 2,
    "unidades": [
      {"moviles":[{"tipo":"PORTABILIDAD","sim":"ESIM","numero":"600000000"}]}
    ]
  }
]

Validation before publishing

  1. New mobile subscription + SIM.
  2. Mobile subscription with number portability + eSIM + phone number.
  3. If the IBAN is missing, it must return HTTP 400.
  4. If a SIM/eSIM is missing, it must return HTTP 400.
  5. If the phone number is missing during portability, it must return HTTP 400.
  6. If the province is missing for fiber service at a different address, it must return HTTP 400.
  7. A successful subscription must return HTTP 201, referencia and contrato_version.
  8. Check the created reference and verify its status.

Documentation

Developer Portal · See also API_DISTRIBUIDORES_DAVATEL.md, openapi-davatel-v1.yaml and the Postman collection included in the technical package.