Skip to main content
V1 is deprecated. V2 preserves V1 data in equivalent Venezuelan operations and adds global IDs and countries. You can keep your V1 integration active while adapting routes.

Route changes

The flat /v1/fx/bcv/currencies table has no identical V2 JSON response. Keep that V1 request if you depend on its exact shape. Review all V2 endpoints before changing a route.

Reusable fields

Venezuelan market mapping

These pairs come from Venezuela’s public snapshot rate registry. Use the API’s returned value; do not construct id from market. Additional BCV references have their own IDs and do not replace V1 markets. Example V1 rate:
The same rate in V2 Free adds id:
Basic adds identity and freshness metadata to /rates; Growth adds descriptions and analysis; Pro retains those fields and enables more operations. See the plan matrix. In V2, category remains a query filter (?category=crypto_p2p), but the rate JSON uses type: "p2p". Do not substitute effective_date or fetched_at for updated_at. The /markets catalogue differs: V2 required_plan is an internal plan ID, while V1 can use a display name or null. Adapt clients that consume this field. V2 rate JSON does not emit category or as_of: use type and updated_at. The index.as_of field belongs only to the index inherited from V1.