The reference your engineers actually need.
The API reference documents Vertlo's REST endpoints in detail: authentication, request and response shapes, idempotency, pagination, error codes, and signed webhooks for every state change.
It is written for engineers integrating payments into a production system, where predictability and accurate error handling matter more than marketing prose.
Reference built for production
Predictable REST
Consistent, versioned resources with clear shapes.
Signed webhooks
Verifiable events for every state change.
Idempotency
Safe retries documented for payment reliability.
Clear errors
Every error code documented with handling guidance.
Inside the API reference
Configured with your acquiring, routing, and reporting during onboarding — and supported by a team that knows the account.
Book a call→Endpoint reference
Every resource with request and response detail.
Auth & environments
Keys, sandbox, and live.
Webhook catalogue
Event types with payloads and signatures.
Errors & idempotency
Codes, retries, and safe request patterns.
What developers reference
Authentication
API keys, environments, and scopes.
Payment endpoints
Create, capture, refund, and query.
Webhook handling
Events, signatures, and retries.
API reference FAQs
Answers to the questions merchants ask most about this part of the platform.
How is authentication handled?
The API uses API keys with separate sandbox and live environments. Secrets use reveal, copy, rotate, and revoke controls and are never exposed by default.
Are webhooks signed?
Yes — every webhook carries a verifiable signature so your systems can trust the payload's origin, with documented retry behaviour.
How do I avoid duplicate charges?
Idempotency keys let you safely retry requests without duplicating actions; the reference documents how to use them across payment endpoints.
Is the API versioned?
Yes — resources are versioned for stability so integrations do not break unexpectedly as the platform evolves.