Tealium · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Tealium Moments Personalization API

3 actions 3 updates phrasing extends openapi/tealium-personalization-api-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for Tealium's API. It is a proposal applied on top of the contract, not a document Tealium publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info

$.paths['/personalization/accounts/{account}/profiles/{profile}/engines/{engineId}/visitors/{visitorId}'].get

$.paths['/personalization/accounts/{account}/profiles/{profile}/engines/{engineId}'].get

OpenAPI Overlay

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Tealium Moments Personalization API
  version: 1.0.0
extends: openapi/tealium-personalization-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/personalization/accounts/{account}/profiles/{profile}/engines/{engineId}/visitors/{visitorId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get personalization moments for an anonymous visitor
      effect: read
      questions:
      - How do I fetch a Moments engine's live context for an anonymous visitor GUID?
      - Can I get an empty 200 instead of a 404 when an anonymous visitor isn't found?
      instructions:
      - text: Get Moments engine {engineId} data for anonymous visitor {visitorId} in {account}/{profile}.
        slots:
          engineId: path.engineId
          visitorId: path.visitorId
          account: path.account
          profile: path.profile
      - text: Fetch audiences and badges from engine {engineId} for visitor GUID {visitorId} on {account}/{profile}, returning empty if not found.
        slots:
          engineId: path.engineId
          visitorId: path.visitorId
          account: path.account
          profile: path.profile
      method: generated
      generated: '2026-10-01'
- target: $.paths['/personalization/accounts/{account}/profiles/{profile}/engines/{engineId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get personalization moments by a known identifier
      effect: read
      questions:
      - Can I look up a visitor's personalization moments server-side using their email or customer ID?
      - Which Moments lookup works with a known identifier instead of the anonymous visitor ID?
      instructions:
      - text: Get Moments engine {engineId} context in {account}/{profile} for the visitor whose attribute {attributeId} is {attributeValue}.
        slots:
          engineId: path.engineId
          account: path.account
          profile: path.profile
          attributeId: query.attributeId
          attributeValue: query.attributeValue
      - text: Personalize for known customer {attributeValue} via attribute {attributeId} using engine {engineId} on {account}/{profile}.
        slots:
          attributeValue: query.attributeValue
          attributeId: query.attributeId
          engineId: path.engineId
          account: path.account
          profile: path.profile
      method: generated
      generated: '2026-10-01'