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

Pagar.me Charges API

Individual payment attempts generated by an order.

Pagar.me Charges API is one of 10 APIs that Pagar.me publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Charges. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 5 paths, and defines 7 schemas. It is described by OpenAPI 3.0.1, at version 5.

Requests are made against a single base URL, https://api.pagar.me/core/v5.

6 operations 5 paths 7 schemas 1 DELETE2 GET2 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
5
Base URL
https://api.pagar.me/core/v5
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

Pagar.me Charges API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic auth with the account secret key as the username and an empty password.

Paths & Operations 6

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

Charges 6

Individual payment attempts generated by an order.

GET
/charges/{charge_id}
Get charge
getCharge 1 param → 200
DELETE
/charges/{charge_id}
Cancel or refund a charge
cancelCharge 1 param → 200
GET
/charges
List charges
listCharges 2 params → 200
POST
/charges/{charge_id}/capture
Capture a charge
captureCharge 1 param body → 200
PATCH
/charges/{charge_id}/card
Update charge card
updateChargeCard 1 param body → 200
PATCH
/charges/{charge_id}/payment-method
Update charge payment method
updateChargePaymentMethod 1 param body → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Charge (11 properties), CreateCustomerRequest (7 properties), Address (6 properties), Paging (3 properties). Each schema is shown below with its type and property counts.

Address
object
6 properties
Customer
Phone
object
3 properties
Charge
object
11 properties
ChargeList
object
2 properties
Paging
object
3 properties
CreateCustomerRequest
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pagarme-charges-api-openapi.yml Raw ↑

Other APIs Pagar.me publishes across the network.

Pagar.me Anticipations API
Pagar.me Cards API
Pagar.me Customers API
Pagar.me Invoices API
Pagar.me Orders API
Pagar.me Plans API
Pagar.me Recipients API
Pagar.me Subscriptions API
Pagar.me Transfers API
Where this information came from

This is an independent, third-party profile of Pagar.me Charges 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.