How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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 Transaction. 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.2.0, at version 1.0.

Requests are made against 2 base URLs: https://production.wompi.co/v1, https://sandbox.wompi.co/v1.

3 operations 3 paths 5 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://production.wompi.co/v1
Authentication
HTTP Bearer, HTTP Bearer
Terms of Service
Resource Areas
1

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.

Transactions 3

Create and track payment transactions.

POST
/transactions
Create a transaction
createTransaction body → 201422
GET
/transactions/{id}
Get a transaction
getTransaction 1 param → 200404
POST
/transactions/{id}/void
Void a card transaction
voidTransaction 1 param → 201

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.

TransactionResponse
object
1 property
TransactionRequest
object
8 properties 7 required
PaymentMethodPse
object
6 properties
PaymentMethodNequi
object
2 properties
PaymentMethodCard
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wompi-transactions-api-openapi.yml Raw ↑

Other APIs Wompi publishes across the network.

Wompi Events (Webhooks)
Wompi Merchants API
Wompi Payment Links API
Wompi Payment Sources API
Wompi PSE API
Wompi Tokenization API
Where this information came from

This is an independent, third-party profile of Wompi Transactions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.