This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
Not from the company, and here with a question? You are welcome here — we would rather be the front line and point you the right way than have a good report go nowhere. What this repository can answer is narrow, though, so it is worth knowing who you are actually looking for:
- A question about how the API works, an account, billing, or a bug in the service — that is the company's own support, not us. We profile this API; we do not operate it and cannot see your account.
- A bug in an open-source project we only catalog — file it on that project's own repository. This has happened with a real and correct bug report that reached us instead of the people who could fix it, which helped nobody.
- Anything about this listing itself — the description, the tags, the rating, a missing or wrong artifact — is ours. Open an issue here.
- Not sure, or something general about API Evangelist or APIs.io — open an issue on the APIs.io Inbox and we will route it.
This repository contains no software, and we will never ask you to download anything. There is no build, release, installer, or binary here — only text and machine-readable API descriptions, so there is nothing here that can be "corrupt" or need "repairing". Any issue, comment, or email claiming otherwise and offering a download link is not from us and is hostile. Do not follow the link; it is a lure. Report it to GitHub and, if you like, tell us at info@apievangelist.com so we can take it down.
On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
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.
Areas: Payments · Australia · Merchant Acquiring · Payment Gateway · In-Person Payments · EFTPOS · Point-of-Sale · Online Payments · Tap to Pay
Everything profiled for Tyro Payments is published on APIs.io rather than in this repository. Start at the provider page — apis.io/providers/tyro/ — or go straight to one of the APIs or properties below.
- 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 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.
Each property below is a page on APIs.io carrying the machine-readable artifact and what it says.
Event-driven and webhook contracts.
Model Context Protocol servers that expose the API to agents.
Which operations an agent can call, which act, and which need a human in the loop.
The data models the API reads and writes.
- Booking
- Connection Response
- Request body to create a test payment
- Request body to deregister a member's card
- Request body to deregister a member
- Embedded Payments Transaction Response
- Existing Order
- Get order
- Online/Offline status response
- Line Item
- List Refunds Response
- Location
- Loyalty Activity object
- Loyalty Card object
- Menu
- Merchant
- Merchant
- Request body to submit a merchant onboarding decision
- Merchant onboarding request response
- Money Positive Amount
- Money Positive Amount With Description
- New booking request
- New Order
- New Pay Request
- New Pay Request
- …and 16 more published on APIs.io
Linked-data contexts for the provider's vocabulary.
Postman and Open Collection request collections.
- Booking API
- Location API
- Loyalty Data API
- Menu API
- Ordering API for App Partners
- Pay API
- Referrals API
- Refunds API
- Reporting API
- Sales Data API
- Table API
- Embedded Payments API
- Pay Terminal API
OpenAPI overlays, including conversational phrasing for each operation.
- Tyro Bookings Api Overlay
- Tyro Connections Api Overlay
- Tyro Locations Api Overlay
- Tyro Loyalty Api Overlay
- Tyro Member Api Overlay
- Tyro Menus Api Overlay
- Tyro Merchants Api Overlay
- Tyro Onboarding Api Overlay
- Tyro Orders Api Overlay
- Tyro Pay Methods Api Overlay
- Tyro Pay Refunds Api Overlay
- Tyro Pay Requests Api Overlay
- Tyro Payments Api Overlay
- Tyro Readers Api Overlay
- Tyro Referrals Api Overlay
- Tyro Refunds Api Overlay
- Tyro Registered Card Api Overlay
- Tyro Reporting Api Overlay
- Tyro Sales Api Overlay
- Tyro Tables Api Overlay
- Tyro Transactions Api Overlay
Spectral rulesets for the provider's contracts.
Authentication, trust centre, and vulnerability disclosure.
Published request limits.
Links to the company's own pages. This repository publishes no copy of their specifications — the canonical document is theirs and lives at the URLs below.
- Website
- Documentation
- Getting started
- API reference
- Pricing
- Support
- Blog
- Security
- Terms of service
- Privacy policy
- GitHub
- Status
Kin Score 40.2 — developing · rubric 0.25.0 · scored 2026-10-23
| Facet | Score |
|---|---|
| Discoverability | 78.6 |
| Contract quality | 60.3 |
| Contract governance | 18.2 |
| Operational transparency | 42.1 |
| Developer ergonomics | 49.4 |
| Access clarity | 0.0 |
Agent readiness 42.3 — agent-ready (gated down from agent-native)
| Agent-readiness dimension | Result |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived (partial credit) |
| Reversibility Documented | documented (partial credit) |
| MCP Server | — |
| Auth Clarity | served (partial credit) |
| Idempotency | — |
| Error Semantics | documented (partial credit) |
| OpenAPI Examples | verified |
| Rate Limit Signal | — |
| Event Surface Described | yes |
| Agent Skills | derived (partial credit) |
| Well Known Catalog | — |
| Consent Identity | — |
| Agent Card | — |
| Dry Run Mode | — |
| Delegated Identity | served (partial credit) |
| Protected Resource Metadata | — |
| Dynamic Client Registration | yes |
| Agentic Commerce | — |
| Pagination Ratio | — |
| Operation Distinctiveness | — |
Regulatory alignment 22.3 — Payments
The rubric is published at github.com/api-evangelist/kin-score. The per-check breakdown behind these numbers — which checks were earned, partial or missed — along with score history and how this provider compares to its peers, is available at apis.io/providers/tyro/.
API Evangelist profiles a company's public API surface the way a developer would find it: the website, developer portal and documentation, the specifications it publishes, its public repositories, and its pricing, status and changelog pages. From that it derives the properties above — contracts split per API, workflows, schemas, collections, governance rules, plans and rate limits — and scores them against the published Kin Score rubric.
The artifacts are published on APIs.io, not in this repository. This repository is the public record for Tyro Payments: the place to say something is wrong, missing or out of date, and to ask for a re-score or a removal.
- Something about this listing — a wrong description, a missing API, a stale artifact or a question about the rating: open an issue on this repository.
- A new API, or one that is not in the catalog yet — submit it on APIs.io.
- Anything else — the APIs.io inbox or info@apievangelist.com.