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

Tyro Payments Menus API

The Menus API from Tyro Payments — 2 operation(s) for menus.

Tyro Payments Menus 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 Menus. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 2 operations across 2 paths, and defines 5 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.

2 operations 2 paths 5 schemas 2 GET

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 Menus 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 2

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

Menus 2
GET
/menus/{tcLocationId}/app/sync
Request latest menu
request-latest-menu 2 params → 204403404409
GET
/menus/{tcLocationId}/app/published
Fetch Latest Menu
fetch-latest-menu 2 params → 200403409

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are item (9 properties), modifier-group (6 properties), section (6 properties), time-slot (5 properties). Each schema is shown below with its type and property counts.

section
object
6 properties 4 required
time-slot
object
5 properties 4 required
modifier-group
object
Modifier groups are a convenience added to the schema for managing the options that can be added to items (e.g. within a menu management app). They are, howeve…
6 properties 3 required
item
object
9 properties 5 required
menu
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tyro-menus-api-openapi.yml Raw ↑

Other APIs Tyro Payments publishes across the network.

Tyro Payments Bookings API
Tyro Payments Connections API
Tyro Payments Locations API
Tyro Payments Loyalty API
Tyro Payments Member API
Tyro Payments Merchants API
Tyro Payments Onboarding API
Tyro Payments Orders API
Tyro Payments Pay Methods API
Tyro Payments Pay Refunds API
Tyro Payments Pay Requests API
Tyro Payments Payments API
Where this information came from

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