Tyro Payments
Tyro Payments is an ASX-listed Australian payments company and one of the country's largest merchant acquirers outside the major banks, holding its own banking licence. Founded in 2003, Tyro provides EFTPOS terminals, in-person and online card acceptance, and integrated payments for more than 70,000 Australian merchants across hospitality, retail and health. Its developer surface, Tyro Connect, is a genuinely API-first platform: a REST API family (served from https://api.tyro.com/connect and secured with OpenID Connect / OAuth 2.0) that links Point of Sale software, ordering, booking, loyalty and reporting apps to Tyro merchants, alongside Tyro.js, mobile SDKs and Tap to Pay (SoftPOS) for card-present and online payments. Home market is Australia.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Tyro Payments the way a machine reads it — 38 machine-readable artifacts across 13 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 — Tyro Payments scores 41.9/100 (developing), with a separate agent-readiness read of 45/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Tyro Payments'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/tyro/"
title="Tyro Payments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tyro.svg"
alt="Tyro Payments Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/tyro/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tyro/"
title="Tyro Payments on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tyro/card.svg"
alt="Tyro Payments 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 Tyro Payments
Each block below is one kind of artifact we hold for Tyro Payments. 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 21
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.
Tyro Payments Bookings API
The Bookings API from Tyro Payments — 2 operation(s) for bookings.
Tyro Payments Connections API
The Connections API from Tyro Payments — 1 operation(s) for connections.
Tyro Payments Locations API
The Locations API from Tyro Payments — 2 operation(s) for locations.
Tyro Payments Loyalty API
The Loyalty API from Tyro Payments — 1 operation(s) for loyalty.
Tyro Payments Member API
The Member API from Tyro Payments — 1 operation(s) for member.
Tyro Payments Menus API
The Menus API from Tyro Payments — 2 operation(s) for menus.
Tyro Payments Merchants API
The Merchants API from Tyro Payments — 7 operation(s) for merchants.
Tyro Payments Onboarding API
The Onboarding API from Tyro Payments — 1 operation(s) for onboarding.
Tyro Payments Orders API
The Orders API from Tyro Payments — 2 operation(s) for orders.
Tyro Payments Pay Methods API
The Pay Methods API from Tyro Payments — 2 operation(s) for pay methods.
Tyro Payments Pay Refunds API
The Pay Refunds API from Tyro Payments — 2 operation(s) for pay refunds.
Tyro Payments Pay Requests API
The Pay Requests API from Tyro Payments — 4 operation(s) for pay requests.
Tyro Payments Payments API
The Payments API from Tyro Payments — 1 operation(s) for payments.
Tyro Payments Readers API
The Readers API from Tyro Payments — 2 operation(s) for readers.
Tyro Payments Referrals API
The Referrals API from Tyro Payments — 2 operation(s) for referrals.
Tyro Payments Refunds API
The Refunds API from Tyro Payments — 1 operation(s) for refunds.
Tyro Payments Registered Card API
The Registered Card API from Tyro Payments — 1 operation(s) for registered card.
Tyro Payments Reporting API
The Reporting API from Tyro Payments — 2 operation(s) for reporting.
Tyro Payments Sales API
The Sales API from Tyro Payments — 2 operation(s) for sales.
Tyro Payments Tables API
The Tables API from Tyro Payments — 2 operation(s) for tables.
Tyro Payments Transactions API
The Transactions API from Tyro Payments — 2 operation(s) for transactions.
Scroll within the panel for all 21 ·
Open Collections 13
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Booking API
OPEN COLLECTIONLocation API
OPEN COLLECTIONLoyalty Data API
OPEN COLLECTIONMenu API
OPEN COLLECTIONOrdering API for App Partners
OPEN COLLECTIONPay API
OPEN COLLECTIONReferrals API
OPEN COLLECTIONRefunds API
OPEN COLLECTIONReporting API
OPEN COLLECTIONSales Data API
OPEN COLLECTIONTable API
OPEN COLLECTIONEmbedded Payments API
OPEN COLLECTIONPay Terminal API
OPEN COLLECTIONScroll within the panel for all 13 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Tyro Webhooks
ASYNCAPISecurity 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Tyro Payments — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
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 14
Properties that don't map to a standard resource type
Scroll within the panel for all 14 ·
← All providers · Data indexed from github.com/api-evangelist/tyro · machine-readable index on apis.io
This is an independent, third-party profile of Tyro Payments, 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.