openapi: 3.0.3 info: title: Talon.One Account Audiences API description: 'Talon.One is an enterprise promotion, loyalty, and incentives engine. This OpenAPI description models the two primary REST surfaces Talon.One exposes. The Integration API (paths under /v1 and /v2 for customer_sessions, customer_profiles, events, coupon_reservations, referrals, loyalty_programs, audiences) pushes real-time customer data into the rules engine and returns the effects to apply. The Management API (paths under /v1 for applications, campaigns, coupons, loyalty_programs, audiences, attributes, collections, accounts, users, exports) administers the resources that back the Campaign Manager. Talon.One runs as a managed, per-customer deployment: replace the server base URL with your own deployment domain. Authenticate with the Authorization header - Integration keys use the ApiKey-v1 prefix and Management keys use the ManagementKey-v1 prefix. Endpoints and paths here are grounded in Talon.One''s public documentation and SDKs; request and response schemas are honestly simplified.' version: '1.0' contact: name: Talon.One url: https://docs.talon.one servers: - url: https://yourbaseurl.talon.one description: Per-customer Talon.One deployment (replace yourbaseurl with your deployment domain) security: - integrationKey: [] - managementKey: [] tags: - name: Audiences description: Manage audiences and their memberships. paths: /v1/audiences: get: operationId: listAudiences tags: - Audiences summary: List audiences description: List the audiences in the account. security: - managementKey: [] responses: '200': description: A list of audiences. content: application/json: schema: type: object /v2/audiences: post: operationId: createAudienceV2 tags: - Audiences summary: Create audience description: Create an audience via the Integration API. security: - integrationKey: [] requestBody: required: true content: application/json: schema: type: object responses: '200': description: The created audience. content: application/json: schema: type: object components: securitySchemes: integrationKey: type: apiKey in: header name: Authorization description: 'Integration API key with the ApiKey-v1 prefix, e.g. header "Authorization: ApiKey-v1 ".' managementKey: type: apiKey in: header name: Authorization description: 'Management API key with the ManagementKey-v1 prefix, e.g. header "Authorization: ManagementKey-v1 ".'