Changelog
15/10/2026 · Clients: new /api/v4/customer route

Clients: new /api/v4/customer route

15/10/2026

The clients API now has its v4 version, with the same operations we documented:

GET    https://api.saltra.es/api/v4/customer
POST   https://api.saltra.es/api/v4/customer
DELETE https://api.saltra.es/api/v4/customer/{customerID}
PUT    https://api.saltra.es/api/v4/customer/{customerID}/activate

Until today the documentation pointed to /api/web/v3/customer, which is the route the Saltra platform itself uses. Its validation follows the web form and, because of that, creating a client required profile.codigo_postal and profile.parameters even though the documentation listed them as optional. v4 has its own API validation:

  • Required: name, access.email, profile.dni, profile.razon_social and at least one account in profile.account (regimen, cuenta and alias).
  • Optional: profile.codigo_postal, profile.parameters, access.password (if you send it, with password_confirmation), profile.direccion, profile.external_id, not_notify.
  • Legal representative: the four fields of profile.parameters.representativeData (doc, name, surname, job_position) are only required if you send representativeData.

Responses keep the same format (success, message, data, status) and validation errors return 422 with the per-field detail in errors. The clients_* MCP tools already use v4.

What to check in your integration:

  • Change the base URL to https://api.saltra.es/api/v4/customer. The request bodies do not change.
  • /api/web/v3/customer still works, but it is internal to the platform: its validation may change without notice when the web changes. Do not build on it.
  • perPage in the list accepts 50 at most; asking for more returns 50.