> For the complete documentation index, see [llms.txt](https://syticks.gitbook.io/merpi-by-syticks/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://syticks.gitbook.io/merpi-by-syticks/explore-the-api-reference.md). # Explore the API Reference The MERPI API is organized into five sections, each covering a specific ticket category. Every section contains the full endpoint reference for that category, including request parameters, response structures, and examples. *** ### API Categories


Experience Ticketing	Concerts, parties, conferences, comedy shows, festivals, and other entertainment events. Covers browsing experiences, fetching ticket categories, holding inventory, and completing purchases.	/pages/1gdKXY1LLDJKoknI0J8g
Cinema Ticketing	Movie showings across cinema chains nationwide. Covers fetching movie listings, showtime structures, multi-location cinemas, and purchasing cinema tickets.	/pages/W5Cnj5F20hEGpenjTp7s
Bus Ticketing	Inter-city and intra-city bus tickets. Covers fetching routes, terminals, schedules, seat availability, and completing bus ticket purchases.	/pages/TFOhimMZLjfKjRHOZefQ
Hospitality	Hotels, resorts, apartments, and short-let accommodations. Covers browsing available properties, checking availability, and completing bookings.	/pages/DBGYmBTUlZA8UYrC6uhk
General Endpoints	Shared endpoints that apply across all ticket categories, including fetching all businesses, transaction requery, and other utility endpoints.	/pages/yDkQXC7I73DXh60566m1

*** ### How Each Section Is Structured Every endpoint page in the API reference follows the same structure so you always know what to expect: * **Endpoint**: The HTTP method and path * **Query or path parameters**: What you can pass and what each field does * **Response fields**: A description of every field returned * **Example requests**: Ready-to-use request examples * **Example responses**: Real response payloads showing all possible field combinations *** ### Before You Start Calling Endpoints {% hint style="info" %} Make sure you have completed the Getting Started steps before making your first API call. You will need your API key attached to every request and a funded Staging wallet to test purchase endpoints. {% endhint %}


Getting Started	Set up your account, get your API keys, and fund your test wallet.	/pages/ZNCIZZctsCFVuzhyQrsD
Authentication	Learn how to attach your API key and transaction medium to every request.	/pages/tYo9evKUQvUzPz26fUEU

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://syticks.gitbook.io/merpi-by-syticks/explore-the-api-reference.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.