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

tread.io Tickets API

The Tickets API from tread.io — 14 operation(s) for tickets.

tread.io Tickets API is one of 58 APIs that tread.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tickets. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 18 operations across 14 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.tread-horizon.com.

18 operations 14 paths 26 schemas 2 DELETE10 GET1 PATCH3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.tread-horizon.com
Authentication
HTTP Bearer
Contact
License
Resource Areas
1

Authentication & Security 1

tread.io Tickets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 18

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

Tickets 18
GET
/v1/companies/{company-id}/orders/{order-id}/tickets
Retrieve Tickets for an Order for a Company
get-v1-companies-company-id-orders-order-id-id-tickets 10 params → 200401404406422
GET
/v1/companies/{company-id}/orders/{order-id}/tickets/rollup_summary
Retrieve Ticket Rollup Summary for an Order for a Company
get-v1-companies-company-id-orders-order-id-id-tickets-rollup-summary 4 params → 200401404406422
GET
/v1/companies/{company-id}/settlements/{settlement-id}/tickets
Retrieve Tickets for a Settlement for a Company
get-v1-companies-company-id-settlements-settlement-id-tickets 6 params → 200401404406
GET
/v1/companies/{company-id}/tickets
Retrieve Tickets that belong to a Company
get-v1-companies-company-id-tickets 9 params → 200401404406422
POST
/v1/direct_uploads
Create a DirectUpload
post-v1-direct_uploads 1 param body → 201401406415422
GET
/v1/jobs/{job-id}/tickets
Retrieve Tickets for a Job
get-v1-jobs-job-id-tickets 9 params → 200401404406422
GET
/v1/orders/{order-id}/ticketsdeprecated
Retrieve Tickets for an Order
get-v1-orders-order-id-id-tickets 9 params → 200401404406422
GET
/v1/orders/{order-id}/tickets/rollup_summarydeprecated
Retrieve Ticket Rollup Summary for an Order
get-v1-orders-order-id-id-tickets-rollup-summary 3 params → 200401404406422
POST
/v1/tickets
Create a Ticket
post-v1-tickets 1 param body → 201400401403404406415422
GET
/v1/tickets
Retrieve Tickets that belong to the current Company
get-v1-tickets 7 params → 200401406422
GET
/v1/tickets/{id}
Retrieve a single Ticket
get-v1-tickets-id 2 params → 200401404406
PATCH
/v1/tickets/{id}
Update a Ticket
patch-v1-tickets-id 2 params body → 200400401403404406415422
DELETE
/v1/tickets/{id}
Delete a Ticket
delete-v1-tickets-id 2 params → 204401403404406422
GET
/v1/tickets/{ticket-id}/ai_metadata
Retrieve a single Ticket's AI metadata
get-v1-tickets-ticket-id-ai-metadata 2 params → 200401404406
PUT
/v1/tickets/{ticket-id}/approve
Approve a Ticket
put-v1-tickets-ticket-id-approve 2 params body → 200400401403404406409415
POST
/v1/tickets/{ticket-id}/image
Update the Image that belongs to a Ticket
post-v1-tickets-ticket-id-image 2 params body → 201400401403404406415422
DELETE
/v1/tickets/{ticket-id}/image
Delete the Image that belongs to a Ticket
delete-v1-tickets-ticket-id-image 2 params → 204401403404406
PUT
/v1/tickets/{ticket-id}/void
Void a Ticket
put-v1-tickets-ticket-id-void 2 params body → 200400401403404406409415

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are DirectUpload-Read (11 properties), Ticket-Create (9 properties), Ticket-Update (8 properties), TicketRollupSummary-Read (7 properties). Each schema is shown below with its type and property counts.

StateError
TicketSource
Material-Read-Nested
object
3 properties 3 required
TicketRollupSummary-Read
object
7 properties 6 required
TicketState
ModelError-Item
object
3 properties 3 required
Error
object
An Error.
1 property 1 required
OrderUnitOfMeasure
Ticket-Read-Nested
Ticket-Create
object
9 properties 1 required
Ticket-Read
UnauthenticatedError
Ticket-Image-Create
object
1 property 1 required
Identifier
object
1 property 1 required
ModelError
A Model-specific error
UnauthenticatedError-Response
object
1 property 1 required
ModelError-Response
object
1 property 1 required
Ticket-Metadata-Read
This model includes AI metadata for a ticket
TicketStateEvent
StateError-Response
object
1 property 1 required
DirectUpload-Create
object
5 properties 4 required
Error-Response
object
1 property 1 required
StateError-Item
DirectUpload-Read
object
11 properties 10 required
Timestamps
object
2 properties 2 required
Ticket-Update
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

treadio-tickets-api-openapi.yml Raw ↑

Other APIs tread.io publishes across the network.

tread.io AccountExternalTruckIdentifier API
tread.io Accounts API
tread.io AddOnCharges API
tread.io AddOns API
tread.io Agave API
tread.io ApprovalAssignments API
tread.io Authentication API
tread.io AutoAddOnAssignments API
tread.io Companies API
tread.io CompanyDayJobStats API
tread.io CompanyShares API
tread.io Compliance API
Where this information came from

This is an independent, third-party profile of tread.io Tickets 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.