Retrieve a trip

Read one stored trip by its SQUAKE ID or by your own trip_reference.

Returns one stored trip: the identity fields a submission echoes back, plus the trip's name, purpose, status, dates, booking provider, amount and cost center as SQUAKE stored them. The trip lists its activities by ID in activity_ids. To read the activities, see List the activities of a trip.

Request

GET /v2/travel-data/trips/{id}

idstringrequired

The trip's SQUAKE id (a UUID) or your own trip_reference.

See every field of GET /v2/travel-data/trips/{id} in the API reference

Both requests below read the same trip, because TRIP-EXAMPLE-002 is that trip's trip_reference:

curl "https://api.sandbox.squake.earth/v2/travel-data/trips/7c9e6f2a-4b81-4d3e-9a52-1f0c8b3d5e47" \
  --header "Authorization: Bearer $SQUAKE_API_KEY"

curl "https://api.sandbox.squake.earth/v2/travel-data/trips/TRIP-EXAMPLE-002" \
  --header "Authorization: Bearer $SQUAKE_API_KEY"

If you set trip_reference when you submit trips, you don't need to store SQUAKE's trip IDs.

Response

200 OKapplication/json
{
  "id": "7c9e6f2a-4b81-4d3e-9a52-1f0c8b3d5e47",
  "trip_reference": "TRIP-EXAMPLE-002",
  "client_id": "4fb3ec7a-92cb-471f-b75f-c3fe7c2a34d5",
  "submitted_by_client_id": "4fb3ec7a-92cb-471f-b75f-c3fe7c2a34d5",
  "trip_name": "Example business trip to London",
  "trip_purpose": "Customer workshop",
  "trip_status": "completed",
  "booking_provider": "Example TMC",
  "start_date_utc": "2026-03-10T00:00:00Z",
  "end_date_utc": "2026-03-12T00:00:00Z",
  "amount_in_cents": 248500,
  "currency": "EUR",
  "cost_center": {
    "name": "Example Cost Center",
    "purpose": "Sales",
    "email": "cost-center@example.com"
  },
  "activity_ids": [
    "2b4d6f81-9c3e-4a57-b0d2-6e1f8a4c7b93",
    "5e1a9c34-7d62-4f08-b3a1-9c4e2d7f6b58",
    "c84f1d27-3e95-4b60-a7d8-2f1b9e6c4a03",
    "a1d3b5c7-2e94-4f68-9b0a-7c5d3e1f8a26"
  ]
}

activity_ids lists every activity of the trip in ingestion order, including activities that later submissions with the same trip_reference appended. Legs of a flight submitted with routing aren't listed: the routed activity carries the itinerary.

Dates come back as UTC date-times, such as 2026-03-10T00:00:00Z, even though ingestion takes plain dates. trip_status is one of planned, confirmed, in_progress, completed, canceled or null. See Trip status for how SQUAKE maps the status you sent.

Errors

StatusCodeMeaning
401The API key is missing or invalid.
404travel_data_not_foundNo trip has this ID or reference, or the trip belongs to a client you can't access.
404 application/json
{
  "errors": [
    {
      "code": "travel_data_not_found",
      "detail": "The requested travel data does not exist or is not accessible."
    }
  ]
}

A trip you can't access returns the same response as one that doesn't exist.

On this page

GET/v2/travel-data/trips/{id}

Run this request against the sandbox with your test key.

Open in API reference