API Map
Explore Cobru's API by product flow: authentication, collections, payouts, cards, services, and the OpenAPI reference.
Cobru's API is organized around the flow an integrator needs to build, not only around individual endpoints. Start with the family that matches your use case and open the interactive reference when you need the exact contract.
Choose a family
Authentication
Tokens, refresh, and base rules for protected Cobru endpoints.
Cobrus
Create hosted payment links, submit method-specific details, and inspect payment state.
Transfers
Move balance between Cobru users and inspect outbound transfers.
Bank withdrawals
Send funds to bank accounts and Bre-B transfer flows.
Cash withdrawals
Create, list, cancel, and inspect cash pickup withdrawals.
Cards
Issue and operate virtual cards exposed by Cobru.
Services
Recharges, Pins, and other transactional services visible in the API.
API reference
Browse the interactive OpenAPI contract with request and response shapes.
Recommended order
- Authentication to stabilize credentials.
- Cobrus if your integration accepts payments.
- Transfers, bank withdrawals, or cash withdrawals if you move balance.
- Cards or services when your product uses those capabilities.
- API reference to verify exact payloads before implementation.
Truth model
Narrative pages explain flow and operational context. The OpenAPI reference shows the grouped contract consumed by the runtime. When an operation comes from legacy materials or observed menu scope, the docs mark that explicitly so assumptions are not treated as verified behavior.