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

Teya Print Receipts (ePOS) API

Create a receipt print job and fetch its status/events

Teya Print Receipts (ePOS) API is one of 16 APIs that Teya publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Print Receipts (ePOS). The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against 2 base URLs: https://api.teya.com, https://api.teya.xyz.

2 operations 2 paths 16 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.teya.com
Resource Areas
1

Paths & Operations 2

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

Print Receipts (ePOS) 2

Create a receipt print job and fetch its status/events

POST
/poslink/v1/receipt-requests
Create a receipt to print (JSON or multipart image)
createPrintJob 2 params body → 201400401403429500
GET
/poslink/v1/receipt-requests/{receipt_id}/status
Get receipt print job with real-time updates
streamEvents 1 param → 200400401403429500

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are ReceiptCreatedResponse (3 properties), Error (3 properties), ReceiptCreateRequest (3 properties), TableHeaderCell (2 properties). Each schema is shown below with its type and property counts.

TableInnerRow
object
1 property 1 required
TableHeaderCell
object
2 properties 1 required
InvalidParams
object
A single failed parameter from a 4xx validation response.
2 properties 2 required
ReceiptCreateRequest
object
Request body to create a new print receipt job
3 properties 3 required
DividerRow
ImageElement
1 required
Element
object
1 property 1 required
SpacerRow
Row
object
1 property 1 required
ReceiptCreatedResponse
object
Response returned after a receipt print job is created
3 properties
QrCodeElement
1 required
TextElement
1 required
Error
object
Error response
3 properties 2 required
TableRow
PrintDocument
object
1 property 1 required
ItemsRow
1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

teya-print-receipts-epos-api-openapi.yml Raw ↑

Other APIs Teya publishes across the network.

Teya Captures API
Teya DCC API
Teya ePOS Registration API
Teya Hosted Checkout API
Teya '@internal' API
Teya Pay at Table API
Teya PayByLink API
Teya Payment Requests API
Teya '@public' API
Teya Refunds API
Teya Reversals API
Teya Stores API
Where this information came from

This is an independent, third-party profile of Teya Print Receipts (ePOS) 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.