Esco catalogues

Read-only lookups served live from Esco. Every one of them returns the same shape — an array of { codigo, descripcion } — and in every case the value you send in an account-opening body is codigo, never descripcion.

[
  { "codigo": "16", "descripcion": "SERVICIOS DE ASESORAMIENTO" },
  { "codigo": "4",  "descripcion": "CULTIVO DE CEREALES" }
]

Field	Type	Description
codigo	string	The value to send. Compared case-insensitively on validation
descripcion	string	Human-readable label. Never send this

paises is not paises-cv

Allaria keeps two separate country catalogues with different codes: this one (Esco) and Caja de Valores. Sending an Esco code where a Caja de Valores value is expected fails with 422.

Field	Takes
nacionalidad, codigo_pais_domicilio, tributa_exterior_pais_codigo	The Esco codigo
lugar_nacimiento	The Caja de Valores name

The endpoints

Endpoint	Feeds these fields
GET/v1/aperturas/actividades	actividad on both account-opening endpoints, and on each person of a business account
GET/v1/aperturas/paises	nacionalidad, codigo_pais_domicilio, tributa_exterior_pais_codigo
GET/v1/aperturas/provincias	codigo_provincia_domicilio
GET/v1/aperturas/tipos-documento	tipo_documento
GET/v1/aperturas/tipos-registracion-juridica	tipo_registracion_juridica on Open business account
GET/v1/aperturas/tipos-riesgo-comitente	Reference only — the risk levels Esco recognises

Document types are tenant-specific

tipos-documento can be seeded per tenant, so the codes are not a fixed contract. Query the endpoint rather than hardcoding.

On the default catalogue 6 is the Argentine DNI, and several validations key off it:

• tipo_documento is the DNI code: documento, numero_tramite_dni, cuil and tipo_contribuyente_iva are validated more strictly.
• Any other code: they are validated as for a foreign holder.

Request

Headers

Field	Type	Required	Description
Authorization	string	Yes	Access token in Bearer ACCESS_TOKEN format

Not applicable: Path Parameters, Query Parameters, Body.

Response

2XX Success

See the shape at the top of this page.

Error Codes

Status	Description
401	Unauthorized — invalid or missing access token
403	Forbidden — your credentials are not authorized for Aperturas
500	Internal Server Error — Esco is unreachable or returned an error. These catalogues are proxied live, so a 500 here usually means Esco is down, not that your request was wrong

Code Example

Every endpoint on this page takes the same request. Substitute the path.

cURL

curl -X GET "https://b2b.allaria.cloud/v1/aperturas/actividades" \
  -H "Authorization: Bearer ACCESS_TOKEN"

JavaScript

const response = await fetch('https://b2b.allaria.cloud/v1/aperturas/actividades', {
  method: 'GET',
  headers: { 'Authorization': 'Bearer ACCESS_TOKEN' }
});
const actividades = await response.json();

Python

import requests
response = requests.get(
  'https://b2b.allaria.cloud/v1/aperturas/actividades',
  headers={'Authorization': 'Bearer ACCESS_TOKEN'}
)
actividades = response.json()

Node.js

const axios = require('axios');
const response = await axios.get('https://b2b.allaria.cloud/v1/aperturas/actividades', {
  headers: { Authorization: 'Bearer ACCESS_TOKEN' }
});
const actividades = response.data;

Caching

These lists change rarely, and every account-opening request re-validates against them. Cache them on your side and refresh periodically rather than fetching on every request.