> 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 TicketingConcerts, parties, conferences, comedy shows, festivals, and other entertainment events. Covers browsing experiences, fetching ticket categories, holding inventory, and completing purchases.Experience Ticketing(Events -Parties, Conference, Comedy and more)
Cinema TicketingMovie showings across cinema chains nationwide. Covers fetching movie listings, showtime structures, multi-location cinemas, and purchasing cinema tickets.Cinema Ticketing(Cinema Movies, Available Days, Purchase, etc)
Bus TicketingInter-city and intra-city bus tickets. Covers fetching routes, terminals, schedules, seat availability, and completing bus ticket purchases.Get All States Endpoint
HospitalityHotels, resorts, apartments, and short-let accommodations. Covers browsing available properties, checking availability, and completing bookings.Hospitality Ticketing(Hotels, Resorts, Apartments)
General EndpointsShared endpoints that apply across all ticket categories, including fetching all businesses, transaction requery, and other utility endpoints.General Endpoints(Get All Businesses, Transaction Requery, etc)
*** ### 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 StartedSet up your account, get your API keys, and fund your test wallet.Getting Started
AuthenticationLearn how to attach your API key and transaction medium to every request. API Keys and Authentication