[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.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) # Skiddle API and MCP server: Let your AI agent run your Skiddle events. > Skiddle has a public events API, still in beta and for non-commercial use only, but no MCP server and no endpoint for guestlists, refunds or tickets (checked 31 Oct 2026). Cotlet runs 15 Skiddle tools hosted, over MCP for agents and REST for scripts. Send guestlist tickets, refund orders, change tickets and read sales in your Skiddle promoter account. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST. [MCP setup](https://cotlet.dev/integrations/skiddle-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/skiddle-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Skiddle - Page: https://cotlet.dev/integrations/skiddle-api-mcp-server ## What can you automate in Skiddle? - Send guestlist tickets to artists and staff - Refund one ticket for a customer - Check ticket sales every morning - Close tickets on the night - Launch a discount code - Copy an event for the next date ## Does Skiddle have an MCP server or an API? - The API needs a key from a form, and Skiddle says it monitors requests and may rate-limit or block excessive ones. Commercial use needs written approval from api@skiddle.com. - Skiddle's GitHub repositories are the events web API wiki (22 stars, last push 4 Mar 2020) and a PHP SDK for listings (2 stars, last push 21 Mar 2024). - Zapier and n8n have no Skiddle app (both pages answer 404, 31 Oct 2026). Make answered 403 and was not checked. | What you need | Skiddle public API | Cotlet | |---|---|---| | Search public events | Yes | Yes, your own events | | Read orders and sales reports | No | Yes | | Send guestlist tickets | No | Yes, after your OK | | Refund an order or ticket | No | Yes, after your OK | | Close, reopen or resize a ticket | No | Yes | | Commercial use | Written approval first | Your own account | Checked 31 Oct 2026. Sources: [Skiddle API](https://www.skiddle.com/api/), [Skiddle web API on GitHub](https://github.com/Skiddle/web-api), [Promotion Centre help: Order Admin](https://help.promotioncentre.co.uk/en/articles/9362829-order-admin) ## How does Cotlet connect to Skiddle? 1. **Sign in to Skiddle.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your Skiddle password, and no guestlist ticket, refund or receipt goes out until you approve it. ## Connect Skiddle to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Enable Skiddle for agents.** Open a free Cotlet account, log in to Skiddle in its Cloud Browser and press Enable for agents. 2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as a new MCP server or connector in your agent. 3. **Sign the connection.** Chat apps open a Cotlet sign-in page. Code editors, n8n and scripts use an API key from the console. Skiddle rides on `https://cotlet.dev/mcp/v1` together with the other apps on your account. If you switch Skiddle on after connecting, refresh the connector to load the ticket tools. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-skiddle \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-skiddle": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-skiddle] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: skiddle_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: skiddle_write ``` ## How to use the Skiddle REST API ### Create your Cotlet API key Create a Cotlet API key with access to Skiddle and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect Skiddle in Cotlet and enable it for agents. Account access: Your own Promotion Centre promoter account, or a team member invited with the Listings + Tickets and Customer Data permissions. ### Make your first Skiddle API request REST: ``` curl https://cotlet.dev/api/v1/skiddle/events \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read events and apply the operation limits A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "skiddle", "tool": "list_events", "result": { "events": [ { "event_id": "5821140", "name": "Warehouse Sessions", "starts_at": "2026-11-14T22:00:00+00:00", "status": "live", "visibility": "public", "tickets_sold": 412 }, { "event_id": "5821377", "name": "Rooftop Social", "starts_at": "2026-11-21T19:00:00+00:00", "status": "live", "visibility": "public", "tickets_sold": 198 } ] } } ``` Lists the events on the Promotion Centre dashboard, soonest first. By default it returns active upcoming events; status switches to past, draft, embargoed, deleted or suspended events. Each row carries the event_id the other tools take. Use get_event for the full listing. `status`: upcoming, past, draft, embargoed, deleted or suspended. Default upcoming. Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination. ### Skiddle workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | The tickets of an event with price, allocation and sales state. Use `list_tickets` in your configured sales report. | | Make | HTTP > Make a request | Ticket sales for chosen events in a date range. Use `get_ticket_sales` in your configured sales report. | | Python or Node.js | REST API | Orders of one event, found by name, email, postcode or order ID. Use `list_orders` in your configured sales report. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Skiddle; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/skiddle-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Skiddle API endpoints and MCP tools ### Events and tickets Active upcoming events by default, other states on request. Price cannot change once a ticket has sold; Skiddle wants a new ticket instead. - **List events** (`list_events`, read): Your events with date, status and tickets sold. - **Get event** (`get_event`, read): One event with venue, visibility and ticket totals. - **List tickets** (`list_tickets`, read): The tickets of an event with price, allocation and sales state. - **Change ticket allocation** (`set_ticket_allocation`, write): Set how many tickets of a type can be sold. - **Close a ticket** (`close_ticket`, write): Take a ticket off sale. - **Reopen a ticket** (`reopen_ticket`, write): Put a closed ticket back on sale. - **Copy an event** (`copy_event`, write): Create a new event from an existing listing. ### Orders and refunds Orders are found by name, email, postcode or order ID, the four keys Order Admin searches by. Refunds are per order or per ticket. - **List orders** (`list_orders`, read): Orders of an event, found by name, email, postcode or order ID. - **Get order** (`get_order`, read): One order with its tickets, customer details and refund state. - **Refund an order** (`refund_order`, write, asks first): Refund a whole order or one ticket of it. - **Resend ticket receipt** (`resend_order_receipt`, write, asks first): Email the ticket receipt of an order to the customer again. ### Guestlists, codes and sales Guestlist tickets are hidden from the public listing. Sales figures are ticket face value without booking fees. - **Add guests to the guestlist** (`add_to_guestlist`, write, asks first): Issue free guestlist tickets to a guest by email. - **Create discount codes** (`create_discount_code`, write): Create a promotion with one or more discount codes. - **List discount codes** (`list_discount_codes`, read): Promotions and their discount codes with usage. - **Get ticket sales** (`get_ticket_sales`, read): Ticket sales for chosen events within a date range. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/skiddle-api-mcp-server#tools ## Who can see my Skiddle session, and how do I revoke it? - **What we store.** Your logged-in Promotion Centre profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 15 Skiddle tools. Never the cookie or your bank details. - **What the session sees.** What your login opens: events, orders, buyer names and emails, guestlists. - **What no tool touches.** Bank details, payouts, finance reports, team members, cancelling or postponing an event. - **Use a team member if you like.** Skiddle lets you invite users with set permissions. Log in as one with Listings + Tickets and Customer Data for the agent. - **How to cut access.** Disable for agents, reset the browser or delete the API key. Qualys SSL Labs, securityheaders.com and Mozilla Observatory grade our site A+ ([live results](https://cotlet.dev/security.md)). A SOC 2 report or third-party pentest does not exist yet. ## Is it against Skiddle's terms? Account safety > The Promoter must keep all account credentials secure and is responsible for all activity carried out through its account by its personnel, agents or any person given access to the account. > > [Skiddle promoter terms and conditions, clause 5.1, read 31 Oct 2026](https://promotioncentre.co.uk/terms-and-conditions/) The promoter terms never mention robots, bots, scraping or AI agents. Clause 5.1 puts everything done in the account on you, agent included, and clause 17.2 lets Skiddle suspend access when it "reasonably considers that continued use of the Services would create legal, regulatory, financial, operational or reputational risk". Clause 15.3 forbids selling or sharing customer details with unauthorised third parties. The API's non-commercial limit covers the public API, which Cotlet does not use. We found no public case of a promoter closed for automation (checked 31 Oct 2026). How we keep your account looking like you: - Your own promoter or team login, typed in by you - One Cloud Browser with its own IP and cookies - Guestlist tickets, refunds and receipts wait for your OK - No tool cancels an event, touches payouts or invites users - If Skiddle objects, we pause the Skiddle tools for everyone within 24 h > Customer details are for messages about the event the customer bought. Skiddle bans their use for promoting other events without an opt-in. ## What happens when Skiddle changes? - **12 h** between tests of the Skiddle event and order reads - **24 h** between tests of the guestlist and refund steps - **$0** for a call to a Skiddle tool paused for repair Skiddle replaced its old promotion centre with a new one (the old login is still listed as "legacy"). When it reworks Order Admin or the guestlist screen, the fix lands on our side. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Finds the right order.** Name or email plus the event, so another event of the same buyer stays untouched. 2. **Reads the tickets.** The order page shows each ticket and what was already refunded. 3. **Waits for your OK.** Order, ticket and amount show up in your Cotlet console. 4. **Reports what happened.** Tickets sent, amounts refunded and guests not found. | Action | Undo | |---|---| | Guestlist tickets | No, the email with the tickets is out | | Refund an order or ticket | No, the money goes back to the buyer | | Resend a receipt | No, but a second copy harms nothing | | Close a ticket | Reopen it, with a new closing time | | Reopen a ticket | Close it again | | Change an allocation | Set the old number back | | Create discount codes | Deactivate them in Discount Codes | | Copy an event | Edit or delete the private copy | 3 of 8 writes ask first: add_to_guestlist, refund_order, resend_order_receipt. They email a guest or move money. The other 5 change your listing and can be reversed in one step, and the 7 reads run at once. Turn the wait off per tool once a nightly run has earned your trust. > To cancel or postpone a whole event, use Skiddle's own procedure. It refunds every customer, so no tool does it. MCP call: ``` { "name": "add_to_guestlist", "arguments": { "event_id": "5821140", "ticket_id": "90120", "name": "Tom Berg", "email": "tom.berg@example.com", "quantity": 2 } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/skiddle/events/5821140/guestlists \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"ticket_id":"90120","name":"Tom Berg","email":"tom.berg@example.com","quantity":2}' ``` Response: ``` { "event_id": "5821140", "ticket_id": "90120", "name": "Tom Berg", "email": "tom.berg@example.com", "quantity": 2, "status": "sent" } ``` A cron job or script reaches the same tools over REST at `/api/v1/skiddle`, with the same key and price. The tools table lists the REST path of each tool. ## How much does the Skiddle MCP server cost? **About $15 a month** for a promoter with 4 events a month, 2,630 credits. Skiddle keeps charging its booking fee as before. | Job | Calls | Credits | |---|---|---| | Guestlist tickets to artists and staff | 3 × 4 | 120 | | Refund one ticket for a customer | 3 × 5 | 150 | | Morning sales check | 2 × 30 | 600 | | Close and reopen tickets on the night | 3 × 4 | 120 | | Discount code for a last-week push | 3 × 2 | 60 | | Copy an event for the next date | 2 × 4 | 80 | | Cloud Browser, 30 days | | 1,500 | | Total | | 2,630 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Same price on Essential and Growth The month is our example: 4 events, 5 single-ticket refunds, 4 guestlist runs and a daily sales check. Skiddle costs the promoter nothing up front; the booking fee is 10% of face value plus 27p, at least £1, and the customer pays it unless you choose to (31 Oct 2026). Dollars at the $29 pack rate. ## Skiddle MCP server on GitHub or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [pipeworx-io/mcp-skiddle](https://github.com/pipeworx-io/mcp-skiddle) | Searches public events, reads one event and lists categories, through a hosted gateway. | 0 stars, last push 29 Oct 2026; listings only, no promoter login. | | [kami4ka/skiddle-scraper](https://github.com/kami4ka/skiddle-scraper) | A Python scraper of event listings through a scraping service. | 0 stars, last push 2 Jan 2026; public pages only. | | Your own script on the [Skiddle API](https://www.skiddle.com/api/) | Event search from your own code, with a PHP SDK. | Needs a developer and an API key, non-commercial unless Skiddle approves in writing, and no orders or guestlists. | Pick the API if you build a listings site. Pick Cotlet when the agent should do your promoter admin: send the guestlist, refund the customer, close the tickets. ## Who runs Cotlet Take Group sp. z o.o. builds and runs Cotlet. The company is registered in Poland, EU (VAT PL6342984273), has worked since 2019 and was founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Skiddle tools to contact@cotlet.dev. ## Skiddle API and MCP: questions ### How do I get access? Create a free account at https://cotlet.dev, pick Skiddle under Integrations in the console and log in to the Promotion Centre in its Cloud Browser. Your trial starts at once and asks for no card. ### How do I connect Skiddle to ChatGPT or Claude? Sign up at cotlet.dev, log in to Skiddle once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Skiddle account through Cotlet, in their phone apps too. ### What can ChatGPT do in Skiddle? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Skiddle: send guestlist tickets to artists and staff; refund a customer who cannot come; check ticket sales every morning. You ask in plain words, and anything that reaches other people waits for your OK first. ### Which Skiddle account does my agent need? A Promotion Centre promoter login. Skiddle lets you invite team members with set permissions; Listings + Tickets covers events and tickets, and Customer Data is needed for order details. Log in as such a team member for the agent. Cotlet does not use the public Skiddle API (checked 31 Oct 2026). ### Can my agent use customer details to market my next event? No. Skiddle allows customer data only for messages about the event the customer bought, and the promoter terms limit direct marketing to opted-in customers. The tools return order details for event admin, such as entry times or a refund. ### Does Skiddle have webhooks or Zapier? No. Zapier and n8n have no Skiddle app (404, 31 Oct 2026). Run the Cotlet tools on a schedule over REST instead of waiting for a trigger. ### Which login does it use, the new or the legacy one? The new Promotion Centre at app.promotioncentre.co.uk. Skiddle lists the old login as legacy, and the help articles the tools follow describe the new screens. ### Can the agent cancel or postpone an event? No. Cancelling triggers face-value refunds for every customer, so you do it yourself in Manage Event. refund_order handles single orders and tickets only. ### Is the MCP server different from the REST API? Only the entrance differs. Both carry the same 15 tools, inputs and answers, one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Skiddle? No. Cotlet is independent and not affiliated with Skiddle Ltd. ### Can I use the Skiddle API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.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.