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

Punchh Payments API

The Payments API from Punchh — 7 operation(s) for payments.

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

This API exposes 26 JSON Schema definitions.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, a JSON-LD context, and 26 JSON Schemas.

This API exposes 9 operations across 7 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://SERVER_NAME_GOES_HERE.punchh.com.

9 operations 7 paths 1 schemas 1 DELETE4 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{server_name}.punchh.com
Resource Areas
1

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 1 DELETE, 4 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Payments 9
GET
/api2/mobile/secure_tokens/{service}
Fetch Client Token
mobile_fetch_client_token 7 params body → 200
GET
/api2/mobile/payments/client_token
Get Client Token
mobile_get_client_token 5 params body → 200
POST
/api2/mobile/payments
Record Payment
mobile_record_payment 5 params body → 200401
GET
/api2/mobile/iframe_payments/new
Get a PAR Pay Token
get-api2-mobile-iframe_payments-new 6 params body → 200400401
POST
/api/pos/payments
Create Payment
pos_create_payment_ssf 2 params body → 200401404422
PUT
/api/pos/payments
Update Payment Status
pos_update_payments 2 params body → 200401404422
DELETE
/api/pos/payments
Void/Cancel Payment
pos_void_payments 2 params body → 200
GET
/api/pos/payments/status
Get Payment Status
pos_get_payments_status 2 params body → 200401422
POST
/api/pos/payments/refund
Refund Payment
pos_refund_payments 2 params body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

menu_items
array
The array contains one or more menu item objects added to an order. You send one of these arrays per API call. See [How To Send Menu Items to Punchh](/docs/dev…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

punchh-payments-api-openapi.yml Raw ↑

Other APIs Punchh publishes across the network.

Punchh POS API
Punchh Api2 API
Punchh Auth API
Punchh Badges API
Punchh Beacons API
Punchh Business Admin Users API
Punchh Business Migration Users API
Punchh Challenges API
Punchh Check In API
Punchh Check Ins API
Punchh Check User Balance API
Punchh Collectibles API
Where this information came from

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