{"files":{"SKILL.md":"---\nname: trip-purpose-prediction\ndescription: \"Trip Purpose Prediction API skill. Use when working with Trip Purpose Prediction for travel. Covers 1 endpoint.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# Trip Purpose Prediction\nAPI version: 1.1.4\n\n## Auth\nNo authentication required.\n\n## Base URL\nhttps://test.api.amadeus.com/v1\n\n## Setup\n1. No auth setup needed\n2. GET /travel/predictions/trip-purpose -- returns the forecast purpose of a trip\n3. Explore available endpoints below\n\n## Endpoints\n1 endpoint across 1 group. See references/api-spec.lap for full details.\n\n### Travel\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /travel/predictions/trip-purpose | Returns the forecast purpose of a trip |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"List all trip-purpose?\" -> GET /travel/predictions/trip-purpose\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n- Error responses include status codes and descriptions in the spec\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api Trip Purpose Prediction\n@base https://test.api.amadeus.com/v1\n@version 1.1.4\n@endpoints 1\n@toc travel(1)\n\n@endpoint GET /travel/predictions/trip-purpose\n@desc Returns the forecast purpose of a trip\n@required {originLocationCode: any # city/airport [IATA code](http://www.iata.org/publications/Pages/code-search.aspx) from which the traveler will depart, e.g. BOS for Boston, destinationLocationCode: any # city/airport [IATA code](http://www.iata.org/publications/Pages/code-search.aspx) to which the traveler is going, e.g. PAR for Paris, departureDate: any # the date on which the traveler will depart from the origin to go to the destination. Dates are specified in the [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) YYYY-MM-DD format, e.g. 2017-12-25, returnDate: any # the date on which the traveler will depart from the destination to return to the origin. Dates are specified in the [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) YYYY-MM-DD format, e.g. 2018-02-28}\n@optional {searchDate: any # the date on which the traveler is performing the search. If this parameter is not specified, current date will be used. Dates are specified in the [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) YYYY-MM-DD format, e.g. 2018-02-28}\n@returns(200) Success\n@errors {400: code    | title                                  ------- | -------------------------------------  477     | INVALID FORMAT 572     | INVALID OPTION 4926    | INVALID DATA RECEIVED                32171   | MANDATORY DATA MISSING}\n\n@end\n"}}