Skiddle API · unofficial, by Cotlet

Create your own Skiddle API

Skiddle's public API lists events for non-commercial use; no API for a promoter's own orders, tickets or guestlist was found (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Skiddle 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 Skiddle session and returns only what your login can see.

Try it free now

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

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

curl
curl -X POST "https://cotlet.dev/api/v1/custom/sales-by-ticket-type" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event": "Warehouse Sessions"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/sales-by-ticket-type";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ event: "Warehouse Sessions" }),
});
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/sales-by-ticket-type",
    headers={"Authorization": f"Bearer {key}"},
    json={"event": "Warehouse Sessions"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "ticket_type": "Early bird",
      "price": "£12.00",
      "sold": 250,
      "left": 0
    },
    {
      "ticket_type": "General",
      "price": "£16.00",
      "sold": 162,
      "left": 88
    }
  ]
}

01 Build

How do you build a Skiddle endpoint with Cotlet?

  1. Sign in to Skiddle in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "For this event, list each ticket type with price, sold and left."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as an event or a date, and the fields it returns.

  4. 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 Skiddle session.

02 Endpoints

Example endpoints you could build for Skiddle

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

  • POST /api/v1/custom/sales-by-ticket-type

    Sales by ticket type

    Price, sold and left for each ticket type of an event

  • POST /api/v1/custom/upcoming-events

    Upcoming events

    Date, tickets sold and status of each event

  • POST /api/v1/custom/find-order

    Find an order

    Buyer, tickets and date of a matching order

  • POST /api/v1/custom/new-orders

    New orders since a time

    Orders placed since the last check, per event

  • POST /api/v1/custom/add-guest writes

    Add a guest

    A guestlist ticket for the name you give, after your OK

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

Request

curl -X POST "https://cotlet.dev/api/v1/custom/sales-by-ticket-type" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event": "Warehouse Sessions"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "ticket_type": "Early bird",
      "price": "£12.00",
      "sold": 250,
      "left": 0
    },
    {
      "ticket_type": "General",
      "price": "£16.00",
      "sold": 162,
      "left": 88
    }
  ]
}

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 Skiddle endpoints for?

  • Schedule Cotlet endpoint Slack or email

    A daily sales count in n8n or Make.

    Tickets sold per event, sent to Slack or email each morning.

  • Schedule endpoint Google Sheets

    A sales sheet for the team.

    Sales by ticket type pulled into Google Sheets every hour on sale day.

  • Your form endpoint guestlist

    A guestlist form.

    Names from your own form added to the guestlist after a yes from you.

  • Chat agent endpoint tickets left

    Your own fan chatbot.

    A chat agent that checks tickets left before it answers a fan.

04 Access

What can an endpoint see and change?

An endpoint works in your own Skiddle session, so it can read and change only what your Skiddle login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as adding a guest, 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.

05 Official API

Does Skiddle have an official API?

Skiddle: "the Skiddle API is read only" and "for non-commercial use only", with public events, venues and artists (checked 20 Nov 2026). The Promotion Centre downloads an event's customer lists as a CSV. The full picture with sources: Does Skiddle have an API or MCP server?

Want ChatGPT or Claude to work in Skiddle instead of code? See the Skiddle MCP server.

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.

Skiddle API with Cotlet: questions

Is this an official Skiddle API?

No. Cotlet is independent and not affiliated with Skiddle. The endpoints you build run in your own signed-in Skiddle 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 Skiddle changes its screens?

An endpoint works while Skiddle works the way it did when you built it. If Skiddle 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.

Build your first Skiddle endpoint

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

Try it free now

No card. Takes about 5 minutes.