# Destino Tour API Onboarding Checklist

## Before starting

- confirm production base URL
- confirm partner technical contact
- confirm API key delivery channel
- confirm whether allowIps will be used for this partner

## Technical setup

- validate `GET /api/v1/health`
- import the Postman collection
- fill `baseUrl` and `apiKey`
- test `GET /api/v1/circuits`
- test `GET /api/v1/departures`

## Reservation flow

- choose a valid `departureId`
- send `POST /api/v1/reservations`
- include `Idempotency-Key`
- store `requestId`
- store `reference`
- store `externalReference`
- validate `GET /api/v1/reservations/{reference}`
- validate `GET /api/v1/reservations?externalReference=<value>`
- validate `PATCH /api/v1/reservations/{reference}` for metadata updates
- validate `POST /api/v1/reservations/{reference}/cancel` only when cancellation is part of the test

## Error handling

- handle `400` invalid payload or missing `Idempotency-Key`
- handle `401` invalid API key
- handle `403` unauthorized IP or reservation from another integrator
- handle `409` no availability
- handle `429` rate limit exceeded

## Go-live checks

- confirm expected traffic volume
- confirm support escalation path
- confirm retry policy based on idempotency
- confirm monitoring uses `x-request-id`