> ## Documentation Index > Fetch the complete documentation index at: https://docs.gojinko.com/llms.txt > Use this file to discover all available pages before exploring further. # audience trend > Demand time series per traveler-type segment Returns a series for each traveler-type segment (excluding Unknown) for the given destination. Requires `destination`. ## OpenAPI ````yaml api-reference/public-api.yaml GET /v1/audience/trend openapi: 3.0.0 info: title: Jinko Public API version: 0.1.0 description: >- Curated public REST surface for Jinko. Authenticated with jnk_ API keys. See https://docs.gojinko.com for guides. ### Per-end-user attribution On booking calls you may send an optional `X-End-User-Id` request header to attribute the booking to one of your own end users (for per-end-user attribution and rate-limiting). The value is an **opaque, tenant-scoped** identifier that you choose — not a Jinko account id. Omit it to book as the tenant. WorkOS-shaped values (prefixed `user_` or `org_`) are rejected. servers: [] security: [] paths: /v1/audience/trend: get: tags: - Demand summary: Demand time series per traveler-type segment description: >- Returns a series for each traveler-type segment (excluding Unknown) for the given destination. Requires `destination`. parameters: - schema: type: string description: >- Origin selector `:` (e.g. `Country:US`), or `global` for all origins. example: Country:US required: false name: origin in: query - schema: type: string minLength: 1 description: Destination selector `:`. Required for this endpoint. example: City:PAR required: true name: destination in: query - schema: type: string pattern: ^\d{4}-\d{2}-\d{2}$ description: >- Start of the departure window (YYYY-MM-DD). Supply together with departure_date_to; omit both (recommended) for no departure-date filter — each bucket then counts searches for all departure dates. A window anchored at the query date counts only long-advance-purchase searches in old buckets and near-departure searches in recent ones, ramping the curve artificially. example: '2026-07-01' required: false name: departure_date_from in: query - schema: type: string pattern: ^\d{4}-\d{2}-\d{2}$ description: >- End of the departure window (YYYY-MM-DD). Supply together with departure_date_from; omit both for no departure-date filter. example: '2026-07-31' required: false name: departure_date_to in: query - schema: type: string enum: - Solo - Couple - Group - Family example: Couple required: false name: traveler_type in: query - schema: type: string enum: - One-Way - Round-Trip example: Round-Trip required: false name: trip_type in: query - schema: type: integer nullable: true minimum: 0 example: 5 required: false name: trip_duration_min in: query - schema: type: integer nullable: true minimum: 0 example: 9 required: false name: trip_duration_max in: query - schema: type: integer nullable: true minimum: 0 example: 7 required: false name: search_window_min in: query - schema: type: integer nullable: true minimum: 0 example: 30 required: false name: search_window_max in: query - schema: type: integer minimum: 2 description: >- Number of buckets N, in the chosen granularity unit (min 2; max depends on granularity: day <= 60, week <= 52, month <= 12; default 12). The series spans the last N complete buckets, excluding the in-progress one (day: last N days ending yesterday; week: last N full Monday-Sunday weeks; month: last N full calendar months). example: 12 required: false name: trend_window in: query - schema: type: string enum: - day - week - month description: >- Bucket size for the returned series: week (default), day, or month. example: week required: false name: granularity in: query - schema: type: integer minimum: 1 maximum: 50 default: 10 description: Maximum number of series (top-N keys). Default 10, max 50. example: 10 required: false name: limit in: query responses: '200': description: Per-segment time series content: application/json: schema: $ref: '#/components/schemas/TrendResponse' '400': description: Bad request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: BAD_REQUEST message: Malformed JSON in request body. doc_url: https://docs.gojinko.com/concepts/errors '401': description: Authentication required content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: AUTH_REQUIRED message: Invalid or expired API key. doc_url: https://docs.gojinko.com/api-reference/authentication '422': description: Validation error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: BAD_REQUEST message: >- origins: origins is required; trip_type: trip_type is required doc_url: https://docs.gojinko.com/concepts/errors '429': description: Rate limit or quota exceeded content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: RATE_LIMITED message: Rate limit or quota exceeded. doc_url: https://docs.gojinko.com/concepts/errors '502': description: Upstream service error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: UPSTREAM_ERROR message: Upstream travel provider returned an error. Please retry. doc_url: https://docs.gojinko.com/concepts/errors security: - ApiKeyAuth: [] - BearerAuth: [] components: schemas: TrendResponse: type: object properties: granularity: type: string example: week from: type: string example: '2026-06-19' to: type: string example: '2026-06-25' series: type: array items: $ref: '#/components/schemas/TrendSeries' required: - granularity - from - to - series ErrorResponse: type: object properties: error: type: object properties: code: type: string message: type: string doc_url: type: string required: - code - message required: - error TrendSeries: type: object properties: label: type: string description: Dimension value for ranked endpoints. example: FR origin: type: string example: Country:US destination: type: string example: Country:FR series: type: array items: type: object properties: date: type: string example: '2026-06-20' value: type: number example: 1234 required: - date - value summary: type: object properties: total: type: number example: 34567 avg_per_day: type: number example: 1191 growth_pct: type: number nullable: true example: 12.3 peak_date: type: string example: '2026-06-14' peak_value: type: number example: 1890 required: - series securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key BearerAuth: type: http scheme: bearer ````