economy

Get travel spending by country and category

Returns annual spending by a country's residents on tourism trips of one night or more, broken down by what the money went on, from Eurostat, the statistical office of the European Union. Categories are total (excluding durables), transport, restaurants, accommodation, package (package arrangements), other and durables. Filter by purpose (personal or business), by destination (domestic, foreign or world), and choose whether to read the total spend or the average per_trip or per_night. Values are in euro (not millions). Results come back as data.series[], one per country and category, each with points[] of { year, value }. A year Eurostat has not published for a country is null, never 0. The response echoes the purpose, destination and measure that were applied, plus dataset, unit and a source_note. This is spending by residents of the reporting country (the demand side), not spending received by a destination.

get/economy/tourism-spend

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/economy/tourism-spend
  • Auth: API key in header x-api-key

Query parameters

country_codestring required

One or more ISO 3166-1 alpha-2 country codes of the travellers' home country, comma-separated (up to 10), e.g. DE,FR. EU27 returns the European Union total.

categorystring

Spending categories, comma-separated. Any of total, transport, restaurants, accommodation, package, other, durables. Defaults to all seven.

purpose'total' | 'personal' | 'business'

Trip purpose: total (default), personal or business.

destination'world' | 'domestic' | 'foreign'

Where the trip went: world (default, all trips), domestic or foreign.

measure'total' | 'per_trip' | 'per_night'

total spend (default), the average per_trip or the average per_night.

from_yearinteger

First year to return. Defaults to five years before the current year.

to_yearinteger

Last year to return. Defaults to the latest year Eurostat has.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "economy",
  "endpoint": "/v1/economy/tourism-spend",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.