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

Teamleader Tickets API

The Tickets API from Teamleader — 9 operation(s) for tickets.

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

This API exposes 6 JSON Schema definitions.

Tagged areas include Ticketing. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 9 operations across 9 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 2026-09-22.

Requests are made against a single base URL, https://api.focus.teamleader.eu.

9 operations 9 paths 17 schemas 9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-09-22
Base URL
https://api.focus.teamleader.eu
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 9

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

Tickets 9
POST
/tickets.addInternalMessage
Adds an internal message to a ticket
post_tickets_addInternalMessage body → 200
POST
/tickets.addReply
Adds a message to a ticket
post_tickets_addReply body → 200
POST
/tickets.create
Create a ticket
post_tickets_create body → 201
POST
/tickets.getMessage
Gets the ticket message
post_tickets_getMessage body → 200
POST
/tickets.importMessage
Imports an existing message to a ticket
post_tickets_importMessage body → 200
POST
/tickets.info
Get details for a single ticket
post_tickets_info body → 200
POST
/tickets.list
Get a list of tickets
post_tickets_list body → 200
POST
/tickets.listMessages
Lists messages of a ticket
post_tickets_listMessages body → 200
POST
/tickets.update
Update a ticket
post_tickets_update body → 204

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are PostTicketsInfoResponse (14 properties), PostTicketsCreateRequest (10 properties), PostTicketsUpdateRequest (10 properties), PostTicketsGetmessageResponse (8 properties). Each schema is shown below with its type and property counts.

PostTicketsAddreplyRequest
object
4 properties 2 required
PostTicketsListmessagesRequest
object
3 properties 1 required
PostTicketsGetmessageRequest
object
1 property 1 required
PostTicketsAddinternalmessageResponse
object
1 property
PostTicketsImportmessageResponse
object
1 property
PostTicketsListResponse
object
1 property
PostTicketsImportmessageRequest
object
5 properties 4 required
PostTicketsCreateResponse
object
1 property
PostTicketsAddreplyResponse
object
1 property
PostTicketsCreateRequest
object
10 properties 3 required
PostTicketsListRequest
object
2 properties
PostTicketsListmessagesResponse
object
2 properties
PostTicketsUpdateRequest
object
10 properties 1 required
PostTicketsInfoResponse
object
14 properties
PostTicketsAddinternalmessageRequest
object
4 properties 2 required
PostTicketsGetmessageResponse
object
8 properties
PostTicketsInfoRequest
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

teamleader-tickets-api-openapi.yml Raw ↑

Other APIs Teamleader publishes across the network.

Teamleader Contacts API
Teamleader Daysoff API
Teamleader Deals API
Teamleader Expenses API
Teamleader Files API
Teamleader Invoices API
Teamleader Leveltwoareas API
Teamleader Lostreasons API
Teamleader Tasks API
Teamleader Ticketstatus API
Teamleader Timers API
Teamleader Useravailability API
Where this information came from

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