Create Travel Data Items

Push one or more complete trip records into SQUAKE for emissions calculation, reporting, and carbon accounting.

EndpointCopy Anchor Link

POST /v2/travel-dataCopy Anchor Link

AuthenticationCopy Anchor Link

• Bearer Token or HTTP Basic Auth (API key as username, no password).

Content-TypeCopy Anchor Link

Content-Type: application/json

EnvironmentsCopy Anchor Link

Request envelopeCopy Anchor Link

{
  "trips": [ <Trip>, ... ]
}

You can send multiple trips per request. Each trip must include at least one activity and a start_date_utc.

Submitting on behalf of another clientCopy Anchor Link

If your account is set up to manage multiple clients (contact us to enable it), you can create child clients and push their travel data through your own credentials — no separate API key per child. Add an optional root-level client_id to store the trips under a descendant client:

{
  "client_id": "4fb3ec7a-92cb-471f-b75f-c3fe7c2a34d5",
  "trips": [ <Trip>, ... ]
}

• client_id is a client id (UUID) as returned by the /v2/clients endpoints.
• Omit client_id to ingest for the authenticated client — existing integrations are unaffected.
• Providing client_id requires this to be enabled for your account (contact us). A client_id outside your hierarchy returns 404 with error code client_not_found, and nothing is written.
• All trips in one request are stored under the same target client, using that client's methodologies and configuration. Your authenticated credential remains the recorded actor.

CSV imports (/v2/travel-data/imports) do not support client_id. Sandbox and production hierarchies are separate: a client_id from one environment is never valid in the other. See Create Child Client for creating and listing the clients you can act for.

Trip fieldsCopy Anchor Link

Cost center fieldsCopy Anchor Link

Activity fieldsCopy Anchor Link

All activities share a common base, then add type-specific fields.

Common fieldsCopy Anchor Link

If you omit methodology, SQUAKE uses your account's configured default methodology for that activity type. Pass methodology only when you want to override that default for a specific activity. The fields needed for calculation still depend on the methodology that SQUAKE resolves.

Trip-level and activity-level monetary values can be sent together and do not have to match. Use trip-level values for the overall booking and activity-level values to attribute spend to individual legs. In reporting flows that use activity spend, an activity's amount_in_cents and currency take precedence over the trip-level values. Do not send amount_base_currency; the API neither accepts nor returns that field.

Traveler fieldsCopy Anchor Link

Flight-specific fieldsCopy Anchor Link

Methodology overrides: ADEME, BASE-EMPREINTE, CO2-EMISSIEFACTOREN-NL, DEFRA, GATE4, ICAO, TIM, TU-CHALMERS, US-EPA.

Hotel-specific fieldsCopy Anchor Link

Methodology overrides: DEFRA, HCMI, GREENVIEW.

Car-specific fieldsCopy Anchor Link

Methodology overrides: ACRISS, BASIC, DEFRA, EU-EEA, US-EPA.

Train-specific fieldsCopy Anchor Link

Methodology overrides: ADEME, BASE-EMPREINTE, CO2-EMISSIEFACTOREN-NL, DEFRA, GREEN-TRAVEL-DATA (new name), GREEN-TRAVEL-PLEDGE (old name, still accepted), REM, SQUAKE, US-EPA.

Request exampleCopy Anchor Link

A complete business trip: outbound flight BER → LHR, hotel in London, taxi from Heathrow, and the return flight. The taxi activity omits methodology, so SQUAKE uses the account's configured car default.

{
  "trips": [
    {
      "amount_in_cents": 248500,
      "currency": "EUR",
      "trip_name": "Example business trip to London",
      "trip_purpose": "Customer workshop",
      "trip_reference": "TRIP-EXAMPLE-002",
      "trip_status": "completed",
      "start_date_utc": "2026-03-10",
      "end_date_utc": "2026-03-12",
      "booking_provider": "Example TMC",
      "pnr": "ABC123",
      "activities": [
        {
          "type": "flight",
          "methodology": "TIM",
          "external_reference": "ACTIVITY-FLIGHT-OUTBOUND",
          "amount_in_cents": 65000,
          "currency": "EUR",
          "origin": "BER",
          "destination": "LHR",
          "departure_date": "2026-03-10",
          "booking_class": "economy",
          "number_of_travelers": 1,
          "airline": "LH",
          "flight_number": "LH2472",
          "start_date_utc": "2026-03-10",
          "end_date_utc": "2026-03-10",
          "traveler": {
            "name": "Jane Doe",
            "email": "jane.doe@example.com",
            "traveler_type": "employee"
          }
        },
        {
          "type": "hotel",
          "methodology": "DEFRA",
          "external_reference": "ACTIVITY-HOTEL-001",
          "amount_in_cents": 98500,
          "currency": "EUR",
          "name": "Example City Hotel",
          "number_of_nights": 2,
          "country": "GB",
          "city": "London",
          "start_date_utc": "2026-03-10",
          "end_date_utc": "2026-03-12",
          "number_of_travelers": 1,
          "eco_labels": ["eu_ecolabel", "green_key"],
          "traveler": {
            "name": "Jane Doe",
            "email": "jane.doe@example.com",
            "traveler_type": "employee"
          }
        },
        {
          "type": "car",
          "external_reference": "ACTIVITY-CAR-001",
          "amount_in_cents": 20000,
          "currency": "EUR",
          "origin": "London Heathrow Airport, United Kingdom",
          "destination": "Canary Wharf, London, United Kingdom",
          "fuel_type": "hev",
          "car_type": "average",
          "usage_type": "taxi",
          "provider_company": "Example Ride Provider",
          "number_of_days": 1,
          "start_date_utc": "2026-03-11",
          "end_date_utc": "2026-03-11",
          "traveler": {
            "name": "Jane Doe",
            "email": "jane.doe@example.com",
            "traveler_type": "employee"
          }
        },
        {
          "type": "flight",
          "methodology": "TIM",
          "external_reference": "ACTIVITY-FLIGHT-RETURN",
          "amount_in_cents": 65000,
          "currency": "EUR",
          "origin": "LHR",
          "destination": "BER",
          "departure_date": "2026-03-12",
          "booking_class": "economy",
          "number_of_travelers": 1,
          "airline": "LH",
          "flight_number": "LH2473",
          "start_date_utc": "2026-03-12",
          "end_date_utc": "2026-03-12",
          "traveler": {
            "name": "Jane Doe",
            "email": "jane.doe@example.com",
            "traveler_type": "employee"
          }
        }
      ],
      "cost_center": {
        "name": "Example Cost Center",
        "purpose": "Sales",
        "email": "cost-center@example.com"
      }
    }
  ]
}

ResponseCopy Anchor Link

ExampleCopy Anchor Link

{
  "carbon_quantity": 333.0,
  "carbon_unit": "kilogram",
  "items": [
    {
      "carbon_quantity": 142.6,
      "carbon_unit": "kilogram",
      "external_reference": "ACTIVITY-FLIGHT-OUTBOUND",
      "trip_reference": "TRIP-EXAMPLE-002",
      "type": "flight",
      "distance": 930.0,
      "distance_unit": "kilometer",
      "methodology": {
        "carbon": { "quantity": 142.6, "unit": "kilogram" },
        "distance": { "distance": 930.0, "unit": "kilometer" },
        "emission_factors": { "energy_scope": "ttw" },
        "meta": { "methodology": "TIM" }
      }
    },
    {
      "carbon_quantity": 36.8,
      "carbon_unit": "kilogram",
      "external_reference": "ACTIVITY-HOTEL-001",
      "trip_reference": "TRIP-EXAMPLE-002",
      "type": "hotel",
      "methodology": {
        "carbon": { "quantity": 36.8, "unit": "kilogram" },
        "meta": { "methodology": "DEFRA" }
      }
    },
    {
      "carbon_quantity": 14.2,
      "carbon_unit": "kilogram",
      "external_reference": "ACTIVITY-CAR-001",
      "trip_reference": "TRIP-EXAMPLE-002",
      "type": "car",
      "distance": 32.0,
      "distance_unit": "kilometer",
      "methodology": {
        "carbon": { "quantity": 14.2, "unit": "kilogram" },
        "distance": { "distance": 32.0, "unit": "kilometer" },
        "emission_factors": { "energy_scope": "ttw" },
        "meta": { "methodology": "DEFRA" }
      }
    },
    {
      "carbon_quantity": 139.4,
      "carbon_unit": "kilogram",
      "external_reference": "ACTIVITY-FLIGHT-RETURN",
      "trip_reference": "TRIP-EXAMPLE-002",
      "type": "flight",
      "distance": 930.0,
      "distance_unit": "kilometer",
      "methodology": {
        "carbon": { "quantity": 139.4, "unit": "kilogram" },
        "distance": { "distance": 930.0, "unit": "kilometer" },
        "emission_factors": { "energy_scope": "ttw" },
        "meta": { "methodology": "TIM" }
      }
    }
  ],
  "trips": [
    {
      "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",
      "activity_ids": [
        "2b4d6f81-9c3e-4a57-b0d2-6e1f8a4c7b93",
        "5e1a9c34-7d62-4f08-b3a1-9c4e2d7f6b58",
        "c84f1d27-3e95-4b60-a7d8-2f1b9e6c4a03",
        "a1d3b5c7-2e94-4f68-9b0a-7c5d3e1f8a26"
      ]
    }
  ]
}

Response fieldsCopy Anchor Link

A trips entry reports the trip's identity, not the content you sent: it does not echo trip_name, trip_status, the dates, the amount or the cost center. Reading the trip back returns those five fields plus everything SQUAKE stored — see Trip fields.

Reading the data backCopy Anchor Link

The trips array is your handle on the stored records. With those IDs — or with your own trip_reference — you can retrieve the trip, list its activities with the calculations persisted for each, look up the audit log behind a calculation, or delete the trip again.

Four things are only visible there, never in items or in the trips array:

• Additional methodologies. items reports the primary methodology per activity; if your account is configured with more, each additional calculation is readable through the activity's ID.
• Audit references. The ID of the audit log a calculation produced.
• The trip as stored. A trip read returns its name, purpose, status, dates, booking provider, amount and cost center — useful for checking what SQUAKE actually kept of what you sent.
• The activity as stored. An activity read returns its route (origin/destination), its fuel_type where the type has one, and the traveler it was booked for.

Note that activity_ids lists only what this request wrote. Because re-using a trip_reference appends activities to an existing trip, that trip may hold more than the response shows — read the trip for the full list.

See Retrieve & Delete Travel Data.

ErrorsCopy Anchor Link

cURLCopy Anchor Link

curl --request POST "https://api.sandbox.squake.earth/v2/travel-data" \
  --header "Authorization: Bearer $ACCESS_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{ "trips": [ ... ] }'

Implementation notesCopy Anchor Link

Set external_reference on every activity. Response items are flattened across all trips in the request, so use external_reference to identify each activity and the echoed trip_reference to know which trip it belongs to. Together they let you reconcile every response item back to your input.

Dates use ISO 8601 (YYYY-MM-DD). The _utc suffix means SQUAKE stores and interprets them as UTC. For same-day legs, start_date_utc and end_date_utc may be identical.

trip_reference is your idempotency key for trip identity. Reuse it to incrementally add activities to a trip as segments get ticketed. Omit it to always create a new trip.

Use activity-level monetary values for per-leg spend. You can retain the overall booking cost on the trip and add amount_in_cents and currency to each activity. Activity values take precedence in activity-based reporting. amount_base_currency is not part of the public API.

usage_type determines GHG scope for car activities. Use rental or taxi for Scope 3.6 (third-party vehicles), company for Scope 1 (company fleet), and personal_car for Scope 3.6 (employee reimbursement).

Partial failures don't fail the whole request. An activity with an unrecognised or missing field returns methodology.errors — the HTTP status is still 200. Check each item individually in error-sensitive workflows.