Wompi Transactions API
Create and track payment transactions.
Wompi Transactions API is one of 7 APIs that Wompi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Transactions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 3 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.0.3, at version 1.0.
Requests are made against 2 base URLs: https://production.wompi.co/v1, https://sandbox.wompi.co/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Wompi Transactions API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (PublicKey).
It accepts HTTP bearer tokens (PrivateKey).
PublicKey— Bearer authorization with the merchant PUBLIC key (pubprod... / pubtest...). Safe for client-side use; grants tokenization, merchant read, transaction create/r…PrivateKey— Bearer authorization with the merchant PRIVATE key (prvprod... / prvtest...). Server-side only; required for payment sources, voids, and payment links.
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Create and track payment transactions.
Schemas 5
The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are TransactionRequest (8 properties), PaymentMethodPse (6 properties), PaymentMethodCard (3 properties), PaymentMethodNequi (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Wompi 6
Other APIs Wompi publishes across the network.