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
Tyro Payments

Tyro Payments Bookings API

The Bookings API from Tyro Payments — 2 operation(s) for bookings.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Bookings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 3 operations across 2 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.tyro.com/connect.

3 operations 2 paths 23 schemas 1 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.tyro.com/connect
Authentication
OpenID Connect
Resource Areas
1

Authentication & Security 1

Tyro Payments Bookings API declares 1 security scheme for authenticating requests. It supports OpenID Connect (JWT) discovered at https://auth.connect.tyro.com/.well-known/openid-configuration.

Paths & Operations 3

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

Bookings 3
POST
/bookings
Create Booking
create-booking-request 3 params body → 201400403
GET
/bookings/{bookingId}
Get Booking
get-booking 3 params → 200403404
PATCH
/bookings/{bookingId}
Update Booking
patch-booking 4 params body → 204400403404

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are booking (12 properties), new-booking-request (10 properties), update-booking-request (10 properties), customer (7 properties). Each schema is shown below with its type and property counts.

section
object
The section within the venue
2 properties
room
object
1 property 1 required
new-booking-request
object
The message to be sent to Tyro Connect in order to mark the booking as seated.
10 properties 4 required
table
object
1 property
payment
object
2 properties
tableAsset
object
7 properties 1 required
tableStatus
string
The current table status of the booking The supported statuses are: SEATED - indicates that the customer connected to the booking has been seated. DINING - ind…
arrivalStatus
string
The customer's arrival status in relation to the booking
acceptHeaderBooking1_0
string
Specifies which version of the API to use. If no value is provided then 0.1 version will be used
booking
object
12 properties 4 required
bookingReference
string
Reference for the booking. It is used to facilitate identification of the booking in the app and pos systems and must be unique per location and booking partne…
reason
string
The reason the booking was rejected or cancelled. Provided only when bookingStatus is REJECTED, CANCELLEDBYMERCHANT or CANCELLEDBYCUSTOMER
bookingStatus
string
The current status of the booking
address
object
The customer address
6 properties
assetUpdate
object
7 properties
payments
array
A list of payments applied to the booking.
customer
object
The customer making the booking
7 properties
time
string
The format of the date time is the notation as defined by [RFC 3339, section 5.6](https://tools.ietf.org/html/rfc3339section-5.6)
payment-with-description
origin
object
Information relevant to the booking partner that this booking was created with
2 properties 1 required
update-booking-request
object
The message to be sent to Tyro Connect in order to update the booking
10 properties
roomAsset
object
The section within the venue
2 properties 2 required
numberOfPeople
number
The number of expected guests

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tyro-bookings-api-openapi.yml Raw ↑

Other APIs Tyro Payments publishes across the network.

Tyro Payments Connections API
AE Profile APIs.io
Tyro Payments Locations API
AE Profile APIs.io
Tyro Payments Loyalty API
AE Profile APIs.io
Tyro Payments Member API
AE Profile APIs.io
Tyro Payments Menus API
AE Profile APIs.io
Tyro Payments Merchants API
AE Profile APIs.io
Tyro Payments Onboarding API
AE Profile APIs.io
Tyro Payments Orders API
AE Profile APIs.io
Tyro Payments Pay Methods API
AE Profile APIs.io
Tyro Payments Pay Refunds API
AE Profile APIs.io
Tyro Payments Pay Requests API
AE Profile APIs.io
Tyro Payments Payments API
AE Profile APIs.io
#Bookings
← Back to T APIs
API Details
ID
tyro:tyro-bookings-api
Base URL
https://api.tyro.com/connect
Docs
https://docs.connect.tyro.com/app/apis/pay
Provider
Tyro 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=tyro-bookings-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/tyro-bookings-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 Tyro Payments Bookings 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.