> For the complete documentation index, see [llms.txt](https://attnapidoc.mytravellerschoice.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://attnapidoc.mytravellerschoice.com/getting-started-with-attraction-api.md). # Getting Started with Attraction API Welcome to Traveller's Choice Attraction API. There are two simple steps to follow before starting the development process. Register as an API consumer with Traveller's choice and get your API Key. ## Registration process To access TCTT APIs, you are required to register as an API consumer with Traveller's Choice. ## Get your API keys Your API requests are authenticated using Access Token. Any request that doesn't include an Access Token will return an error. To generate Access Token, you need to make an API request with your API key, which will be provided when you register as an API consumer. You can see and copy your API Key anytime from your dashboard. --- # 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, and the optional `goal` query parameter: ``` GET https://attnapidoc.mytravellerschoice.com/getting-started-with-attraction-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.