Pinch
Pinch provides an at‑home medical spa experience combined with a payments platform that enables businesses to accept online payments for aesthetic treatments. The company offers a suite of APIs for managing customers, processing credit‑card and direct‑debit transactions, handling subscriptions, and integrating with third‑party services. Documentation includes guides, reference API specs, and SDKs for multiple languages, supporting developers to build seamless checkout flows for health‑and‑beauty services.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Pinch the way a machine reads it — 26 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Pinch scores 37.6/100 (thin), with a separate agent-readiness read of 24/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Docs site returns HTTP 429 rate limit errors, preventing access to machine‑readable spec.
The documentation is public — a person can read it, but a machine cannot. This one is Pinch's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.
What we probed
https://docs.getpinch.com.au/reference→ HTTP 429
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Pinch's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/pinch/"
title="Pinch on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/pinch.svg"
alt="Pinch Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/pinch/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/pinch/"
title="Pinch on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/pinch/card.svg"
alt="Pinch Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Pinch
Each block below is one kind of artifact we hold for Pinch. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Pinch API
API for Pinch payments and medical spa services
Pinch Calculate Fees API
The Calculate Fees API from Pinch — 1 operation(s) for calculate fees.
Pinch Connect API
The Connect API from Pinch — 1 operation(s) for connect.
Pinch Fees API
The Fees API from Pinch — 1 operation(s) for fees.
Pinch Merchants API
The Merchants API from Pinch — 2 operation(s) for merchants.
Pinch Payers API
The Payers API from Pinch — 2 operation(s) for payers.
Pinch Payment Links API
The Payment Links API from Pinch — 1 operation(s) for payment links.
Pinch Payments API
The Payments API from Pinch — 3 operation(s) for payments.
Pinch Plans API
The Plans API from Pinch — 2 operation(s) for plans.
Pinch Refund API
The Refund API from Pinch — 1 operation(s) for refund.
Pinch Refunds API
The Refunds API from Pinch — 2 operation(s) for refunds.
Pinch Sources API
The Sources API from Pinch — 1 operation(s) for sources.
Pinch Subscriptions API
The Subscriptions API from Pinch — 3 operation(s) for subscriptions.
Pinch Test API
The Test API from Pinch — 11 operation(s) for test.
Pinch Transfers API
The Transfers API from Pinch — 3 operation(s) for transfers.
Pinch Webhooks API
The Webhooks API from Pinch — 1 operation(s) for webhooks.
Scroll within the panel for all 16 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Pinch Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Pinch API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
PostCalculateFeesResponse
JSON SCHEMAPostMerchantsMerchantidRequest
JSON SCHEMAPostPlansRequest
JSON SCHEMAPostRefundsRequest
JSON SCHEMAPostRefundsResponse
JSON SCHEMAPostSubscriptionsRequest
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Pinch — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/pinch · machine-readable index on apis.io
This is an independent, third-party profile of Pinch, 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.