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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Pin Payments

Pin Payments Customers API

Store customer profiles with payment sources for repeat billing.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

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

Requests are made against 2 base URLs: https://api.pinpayments.com/1, https://test-api.pinpayments.com/1.

11 operations 7 paths 1 schemas 3 DELETE5 GET2 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://api.pinpayments.com/1
Authentication
HTTP Basic
Contact
Pin Payments
Resource Areas
1

Authentication & Security 1

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

  • basicAuth — HTTP Basic with the API key as the username and an empty password.

Paths & Operations 11

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

Customers 11

Store customer profiles with payment sources for repeat billing.

POST
/customers
Create a customer
body → 201
GET
/customers
List customers
→ 200
GET
/customers/{customer_token}
Retrieve a customer
1 param → 200
PUT
/customers/{customer_token}
Update a customer
1 param → 200
DELETE
/customers/{customer_token}
Delete a customer
1 param → 204
GET
/customers/{customer_token}/charges
List charges for a customer
1 param → 200
GET
/customers/{customer_token}/cards
List cards for a customer
1 param → 200
POST
/customers/{customer_token}/cards
Add a card to a customer
1 param → 201
DELETE
/customers/{customer_token}/cards/{card_token}
Remove a non-primary card from a customer
2 params → 204
GET
/customers/{customer_token}/subscriptions
List subscriptions for a customer
1 param → 200
DELETE
/customers/{customer_token}/subscriptions/{sub_token}
Cancel a customer subscription
2 params → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is CustomerCreate (8 properties). Each schema is shown below with its type and property counts.

CustomerCreate
object
8 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pin-payments-customers-api-openapi.yml Raw ↑

Other APIs Pin Payments publishes across the network.

Pin Payments Cards API
AE Profile APIs.io
Pin Payments Charges API
AE Profile APIs.io
Pin Payments Refunds API
AE Profile APIs.io
#Customers
← Back to P APIs
API Details
ID
pin-payments:pin-payments-customers-api
Base URL
https://api.pinpayments.com/1
Docs
https://pinpayments.com/
Provider
Pin Payments
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=pin-payments-customers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/pin-payments-customers-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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