Migrate to the English names

From version 2026-11-03 every identifier in the API is in English: routes, fields, values and error codes. Human-readable text (message) stays in Spanish.

If your account existed before that date, it stays on 2026-10-22 (the names you know) for 90 days: nothing breaks today. Production starts in English only, so switch before you go live.

What doesn’t change

If you pay out with a quote, a beneficiary and a payout, almost everything stays the same:

• POST /v1/quotes, POST /v1/payouts, /v1/beneficiaries, /v1/payments, /v1/events, GET /v1/limits/usage and GET /v1/treasury/position, with their fields.
• pago_movil and transferencia in method: they are the names of the Venezuelan payment methods and are not translated.
• The payment.settled, payment.failed and payment.reversed webhooks, their payload and their signature.
• Idempotency-Key, pagination and the error.code values that were already in English (limit_exceeded, insufficient_tenant_funds, quote_expired…).

What changes

Before (2026-10-22)	Now (2026-11-03)
reference: "PRUEBA:SUBMITTED" (also UNKNOWN, SETTLED, TIMEOUT_AFTER_SUBMIT)	reference: "TEST:SUBMITTED"
GET /v1/tenant/me → entorno: pruebas | real	environment: sandbox | production
GET /v1/tenant/capacidades	GET /v1/tenant/capabilities
fondeo.modelo: cierre_diario | prefondeado | cuenta_propia	funding.model: daily_settlement | prefunded | own_account
fondeo.limiteCredito, fondeo.dondeVerSaldo	funding.creditLimit, funding.balanceEndpoint
dispersion.metodos, limites[], tasaVenta[]	payouts.methods, limits[], sellRates[]
POST /v1/treasury/tasa-venta with { "tasa" }	POST /v1/treasury/sell-rate with { "rate" }
tasa, fijadaEn, deHoy	rate, setAt, isToday
GET /v1/treasury/volumen?desde=&hasta=	GET /v1/treasury/volume?from=&to=
pagos, tramos, detalle, comisionRedBs	paymentCount, tiers, lines, networkFeeBs
GET /v1/treasury/fee-volumen (vigenteDesde)	GET /v1/treasury/volume-fee (effectiveFrom)
GET /v1/treasury/inventario (saldoBs, costoUsd, tasaPromedio)	GET /v1/treasury/inventory (balanceBs, costUsd, averageRate)
GET /v1/payments/metricas	GET /v1/payments/metrics
POST /v1/pruebas/sembrar	POST /v1/test-helpers/seed
POST /v1/pruebas/fondeos with { "montoUsd", "montoBs", "referencia" }	POST /v1/test-helpers/fundings with { "amountUsd", "amountBs", "reference" }
POST /v1/pruebas/pagos/{id}/resolver with { "resultado" }	POST /v1/test-helpers/payments/{id}/resolve with { "outcome" }
POST /v1/tenant/webhook/test → entregado, pista	delivered, hint
pruebas_solo_cuenta_de_pruebas	test_account_required
tenant_sin_tasa_venta · fondeo_referencia_reusada	sell_rate_missing · funding_reference_reused

The full list of fields for each route is in the API reference.

How to switch

1. Try it without changing anything

   Send the BC-Version: 2026-11-03 header on your test calls. That request comes back in English; the others, as always.

   curl -s $BASE/v1/tenant/capabilities -H "x-api-key: $KEY" -H "BC-Version: 2026-11-03"

2. Change your code

   The routes and fields in the table. While the window lasts we accept both languages in what you send us, so you can change it piece by piece.

3. Set your account’s version

   curl -s -X PUT $BASE/v1/tenant/api-version -H "x-api-key: $KEY" \
     -H 'content-type: application/json' -d '{"version":"2026-11-03"}'

   From then on everything reaches you in English, webhooks included. If something breaks, go back with {"version":"2026-10-22"} while the window lasts.

How you know something is missing

Every response carries BC-Version with the version it was sent in. If you used an old name (a route, a field, PRUEBA: or version 2026-10-22), the response also carries Deprecation and Sunset (the date it stops existing). When you no longer see them, you’re done.

Production, English only

2026-10-22 does not exist in production: Spanish routes return 404, Spanish fields 400 validation_failed and BC-Version: 2026-10-22 returns 400 api_version_unsupported.