MustSeen API Documentation
Welcome to the MustSeen API documentation. Here you will find everything you need to integrate our travel intelligence into your application.
Our API is built around REST principles and returns predictable JSON-formatted responses, using standard HTTP response codes and authentication.
Authentication
The MustSeen API uses API keys to authenticate requests. You can view and manage your API keys in your Developer Dashboard. All API requests must be made over HTTPS and include your key in the Authorization header as a Bearer token.
Authorization: Bearer YOUR_API_KEY Requests made without authentication will fail with a 401 status code.
Create a Travel Plan
This is the core endpoint of the MustSeen platform. It takes a user's intent and constraints and returns a ranked list of optimized, bookable travel package options.
POST /v1/plan
Request Body
| Parameter | Type | Description |
|---|---|---|
| intent | string | A natural language description of the desired trip. The more detailed, the better the result. |
| constraints | object | An object containing hard constraints for the trip. |
| constraints.budget_eur | integer | The maximum total budget for the trip in EUR. |
Errors
MustSeen uses conventional HTTP response codes to indicate the success or failure of an API request.
| Status Code | Meaning |
|---|---|
| 400 Bad Request | Your request has missing or invalid parameters. |
| 401 Unauthorized | Your API key is wrong or missing. |
| 429 Too Many Requests | You have hit a rate limit. Please slow down your requests. |
| 500 Internal Server Error | Something is wrong on our end. Please contact support. |