[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create your own Tiqets API

> No Tiqets API for travelers was found. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/tiqets

Tiqets' Distributor API is for distribution partners and affiliates, not for travelers (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Tiqets account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Tiqets session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=tiqets)

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Tiqets. Tiqets is a trademark of its owner. If Tiqets's own integrations cover what you need, use them first.

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/upcoming-bookings" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"month": "2026-12"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/upcoming-bookings";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ month: "2026-12" }),
});
const { data } = await res.json();
```

Python

```
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/upcoming-bookings",
headers={"Authorization": f"Bearer {key}"},
json={"month": "2026-12"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"date": "2026-12-05",
"attraction": "Art museum",
"entry_time": "10:00",
"tickets": 2
},
{
"date": "2026-12-06",
"attraction": "Canal cruise",
"entry_time": "15:00",
"tickets": 2
}
]
}
```

01 Build

## How do you build a Tiqets endpoint with Cotlet?

1. 01  
www.tiqets.com  
Signed in  
### Sign in to Tiqets in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List my Tiqets bookings in December with attraction, date, entry time and tickets.  
### Do the job once with your agent.  
For example: "List my Tiqets bookings in December with attraction, date, entry time and tickets."
3. 03  
Save endpoint  
Name  
upcoming-bookings  
Input  
month  
Returns  
date, attraction, entry\_time, tickets  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a month or a city, and the fields it returns.
4. 04  
$ POST /api/v1/custom/upcoming-bookings  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in Tiqets session.

02 Endpoints

## Example endpoints you could build for Tiqets

Cotlet ships no fixed list of Tiqets endpoints. You decide which endpoints you build and what each one returns.

- POST `/api/v1/custom/upcoming-bookings`  
### Bookings in a month  
Attraction, date, entry time and tickets of each booking
- POST `/api/v1/custom/tickets-in-city`  
### Tickets in a city  
Museums and attractions for a date, with price
- POST `/api/v1/custom/entry-times`  
### Entry times  
Open entry times of a ticket for a date
- POST `/api/v1/custom/free-cancellation`  
### Bookings with free cancellation  
Bookings you can still cancel for free, with the deadline
- POST `/api/v1/custom/cancel-booking` writes  
### Cancel a booking  
A cancellation of the booking you name, under its own terms
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/upcoming-bookings" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"month": "2026-12"}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"date": "2026-12-05",
"attraction": "Art museum",
"entry_time": "10:00",
"tickets": 2
},
{
"date": "2026-12-06",
"attraction": "Canal cruise",
"entry_time": "15:00",
"tickets": 2
}
]
}
```

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

## What can you use your Tiqets endpoints for?

- Schedule Cotlet endpoint Calendar  
### A trip calendar.  
Your booked visits pulled each week into Google Calendar.
- Schedule endpoint Phone message  
### A reminder before each visit.  
The evening before, the entry time sent to your phone.
- Month end endpoint Google Sheets  
### A travel expense sheet.  
Bookings and prices by month, pulled into Google Sheets.
- Chat agent endpoint entry times  
### Your own travel assistant.  
A chat agent that checks entry times before it suggests a plan for the day.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Tiqets session, so it can read and change only what your Tiqets login can. You choose what each endpoint does when you build it.

An endpoint that changes something, such as cancelling a booking, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

DRY RUN · nothing sent

$ POST /api/v1/custom/cancel-booking

would POST www.tiqets.com/... cancel the canal cruise booking on Dec 6

`cancel-booking`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Tiqets have an official API?

No Tiqets API for travelers was found (checked 20 Nov 2026). Tiqets' Distributor API is for distribution partners and affiliates, with around 200 orders a month as the minimum, and its Supplier API is for venues. The full picture with sources: [Does Tiqets have an API or MCP server?](https://cotlet.dev/api-status/tiqets.md)

Want ChatGPT or Claude to work in Tiqets instead of code? See the [Tiqets MCP server](https://cotlet.dev/integrations/tiqets-api-mcp-server.md).

0/3

Official API

Partners only

[Full API & MCP report](https://cotlet.dev/api-status/tiqets.md)

06 Pricing

## What does it cost?

per successful call

 10 credits

when a call fails

 0

in the smallest pack

≈ 500 calls

free trial, no card

 7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

## Tiqets API with Cotlet: questions

### Is this an official Tiqets API?

No. Cotlet is independent and not affiliated with Tiqets. The endpoints you build run in your own signed-in Tiqets account.

### Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

### What happens when Tiqets changes its screens?

An endpoint works while Tiqets works the way it did when you built it. If Tiqets changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

### How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

POST /api/v1/custom/<name>

## Build your first Tiqets endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=tiqets)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
