Qloo Audiences API

Segment and filter by audience groupings

Operations 2

GET /v2/audiences Get Audiences #
GET /v2/audiences/types Get Audience Types #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/qloo-com:qloo-com-audiences-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

qloo-com-audiences-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Qloo Audiences API
  version: '2.0'
  description: Qloo's API
  contact:
    name: Support
    email: support@qloo.com
servers:
- url: https://api.qloo.com
  description: Production Qloo API server
security:
- ApiKey: []
tags:
- name: Audiences
  description: Segment and filter by audience groupings
paths:
  /v2/audiences:
    get:
      deprecated: true
      summary: Get Audiences
      x-readme-title: Get Audiences
      operationId: get-audiences
      description: The Find Audiences API retrieves a list of audience IDs that can be used for filtering results and refining targeting in recommendations. You can use the returned audience IDs as values for `signal.demographics.audiences` to filter Insights API query results by specific audiences.
      tags:
      - Audiences
      parameters:
      - name: filter.parents.types
        in: query
        description: Filter by a comma-separated list of parental entity types.
        required: false
        style: form
        explode: false
        schema:
          type: string
          enum:
          - urn:audience:communities
          - urn:audience:global_issues
          - urn:audience:hobbies_and_interests
          - urn:audience:investing_interests
          - urn:audience:leisure
          - urn:audience:life_stage
          - urn:audience:lifestyle_preferences_beliefs
          - urn:audience:political_preferences
          - urn:audience:professional_area
          - urn:audience:spending_habits
          examples:
          - urn:audience:communities
          - urn:audience:global_issues
      - name: filter.results.audiences
        in: query
        description: Filter by a comma-separated list of audience IDs.
        required: false
        style: form
        explode: false
        schema:
          type: array
          items:
            type: string
          examples:
          - urn:audience:communities
          - urn:audience:spending_habits
      - name: filter.audience.types
        in: query
        description: Filter by a list of audience types.
        required: false
        style: form
        explode: false
        schema:
          type: array
          items:
            type: string
          examples:
          - urn:audience:communities
          - urn:audience:spending_habits
      - name: filter.query
        in: query
        description: A partial string search on the audience or tag name.
        required: false
        schema:
          type: string
          examples:
          - vegan
      - name: filter.popularity.min
        in: query
        description: Filter by the minimum popularity percentile required for a Point of Interest (float, between 0 and 1; closer to 1 indicates higher popularity, e.g., 0.98 for the 98th percentile).
        required: false
        schema:
          type: number
          minimum: 0
          maximum: 1
          examples:
          - 0.5
      - name: filter.popularity.max
        in: query
        description: Filter by the maximum popularity percentile a Point of Interest must have (float, between 0 and 1; closer to 1 indicates higher popularity, e.g., 0.98 for the 98th percentile).
        required: false
        schema:
          type: number
          minimum: 0
          maximum: 1
          examples:
          - 0.98
      - name: page
        in: query
        description: The page number
        schema:
          type: integer
          format: int32
          minimum: 1
          maximum: 100
          default: 1
        examples:
          default:
            value: 1
      - name: take
        in: query
        required: false
        description: 'The number of results to return. Default is `20`. The maximum allowed is `50`.

          To retrieve additional results, use the `page` parameter to access the next page of results. This is the recommended approach for pagination.

          For specific cases, the `offset` parameter can be used with `take` to skip a set number of results.

          '
        schema:
          type: integer
          default: 20
          minimum: 1
          maximum: 50
          examples:
          - 10
      responses:
        '200':
          description: Successful Operation
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  results:
                    type: object
                    properties:
                      entities:
                        type: array
                        items: {}
                      duration:
                        type: number
        '400':
          description: Bad Request
        '500':
          description: Internal Server Error
  /v2/audiences/types:
    get:
      deprecated: true
      summary: Get Audience Types
      x-readme-title: Get Audience Types
      operationId: get-audience-types
      description: The Get Audience Types API returns all available audience type IDs, representing different audience categories. You can use this API to explore audience classifications and refine searches in the Find Audiences API. Including `filter.parents.types` allows you to narrow results by relevant entity types.
      tags:
      - Audiences
      parameters:
      - name: filter.parents.types
        in: query
        description: Filter by a comma-separated list of parental entity types.
        required: false
        style: form
        explode: false
        schema:
          type: string
          enum:
          - urn:audience:communities
          - urn:audience:global_issues
          - urn:audience:hobbies_and_interests
          - urn:audience:investing_interests
          - urn:audience:leisure
          - urn:audience:life_stage
          - urn:audience:lifestyle_preferences_beliefs
          - urn:audience:political_preferences
          - urn:audience:professional_area
          - urn:audience:spending_habits
          examples:
          - urn:audience:communities
          - urn:audience:global_issues
      - name: page
        in: query
        description: The page number
        schema:
          type: integer
          format: int32
          minimum: 1
          maximum: 100
          default: 1
        examples:
          default:
            value: 1
      - name: take
        in: query
        required: false
        description: 'The number of results to return. Default is `20`. The maximum allowed is `50`.

          To retrieve additional results, use the `page` parameter to access the next page of results. This is the recommended approach for pagination.

          For specific cases, the `offset` parameter can be used with `take` to skip a set number of results.

          '
        schema:
          type: integer
          default: 20
          minimum: 1
          maximum: 50
          examples:
          - 10
      responses:
        '200':
          description: Successful Operation
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  results:
                    type: object
                    properties:
                      entities:
                        type: array
                        items: {}
                      duration:
                        type: number
        '400':
          description: Bad Request
        '500':
          description: Internal Server Error
components:
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: X-Api-Key
x-provenance:
  method: searched
  source: https://docs.qloo.com/reference
  harvested: '2026-10-21'
  tool: harvest-readme-openapi.py
  note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
  assembled_from:
  - https://docs.qloo.com/reference/analysis-compare.md
  - https://docs.qloo.com/reference/api-information.md
  - https://docs.qloo.com/reference/get-audience-types.md
  - https://docs.qloo.com/reference/get-audiences.md
  - https://docs.qloo.com/reference/get-entities.md
  - https://docs.qloo.com/reference/get-search.md
  - https://docs.qloo.com/reference/get-tag-types.md
  - https://docs.qloo.com/reference/get-trending.md
  - https://docs.qloo.com/reference/insights-api-deep-dive.md
  - https://docs.qloo.com/reference/search-tags.md
  merge:
    pages: 10
    deduped: 9
    conflicts_kept_first: 0