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

dLocal Payments API

Create and manage payment transactions

dLocal Payments API is one of 17 APIs that dLocal publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 5 operations across 5 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 2.1.

Requests are made against 2 base URLs: https://api.dlocal.com, https://sandbox.dlocal.com.

5 operations 5 paths 11 schemas 2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.1
Base URL
https://api.dlocal.com
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

dLocal Payments API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (HmacAuth). By default, every request must be authenticated.

  • HmacAuth — HMAC-SHA256 signature. Format: "V2-HMAC-SHA256, Signature: {hmacvalue}" Signature = HMAC-SHA256(X-Login + X-Date + RequestBody, SecretKey)

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Payments 5

Create and manage payment transactions

POST
/payments
Create a Payment
createPayment body → 200400401500
POST
/secure_payments
Create a Secure Payment (with Card Data)
createSecurePayment body → 200400
GET
/payments/{payment_id}
Retrieve a Payment
getPayment 1 param → 200404
GET
/payments/merchant_order_id/{order_id}
Retrieve a Payment by Order ID
getPaymentByOrderId 1 param → 200
POST
/payments/{payment_id}/cancel
Cancel a Payment
cancelPayment 1 param → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are CreatePaymentRequest (23 properties), Payment (18 properties), CardInput (12 properties), Payer (8 properties). Each schema is shown below with its type and property counts.

Address
object
6 properties
CreatePaymentRequest
object
23 properties 6 required
Payment
object
18 properties
Split
object
3 properties
CardOutput
object
6 properties
DeviceInfo
object
2 properties
Submerchant
object
4 properties
Payer
object
8 properties 2 required
CardInput
object
12 properties
Error
object
3 properties
WalletInput
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dlocal-payments-api-openapi.yml Raw ↑

Other APIs dLocal publishes across the network.

dLocal Payouts API
dLocal Platforms API
dLocal Verification API
dLocal Accounts API
dLocal Balance API
dLocal Bank Accounts API
dLocal Chargebacks API
dLocal Currency API
dLocal Documents API
dLocal KYC API
dLocal Payment Methods API
dLocal Payouts API
Where this information came from

This is an independent, third-party profile of dLocal Payments 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.