Skip to main content
Customers with AI Services implementations use ASAPP’s Metadata Ingestion API to send key attributes about conversations, customers, and agents. Developers can join metadata with AI Service output data to sort and filter reports and analyses using attributes important to your business.
Metadata Ingestion API is not accessible by default. Reach out to your ASAPP account contact to ensure it is enabled for your implementation.

Before You Begin

To use ASAPP’s APIs, you need API credentials for each app. Get in touch with your ASAPP team to receive your unique API keys.

Endpoints

The Metadata Ingestion endpoints are used to send information about agents, conversations, and customers. Metadata can be sent for a single entity (e.g., one agent) or for multiple entities at once (e.g., several hundred agents) in a batch format.

Agent

The OpenAPI specification for each agent endpoint shows the types of metadata the API accepts. Examples include information about lines of business, groups, locations, supervisors, languages spoken, vendor, job role, and email. The endpoints also accept custom-defined attributes in key-value pairs if no existing field in the schema suits the type of metadata you wish to upload.

Conversation

The OpenAPI specification for each conversation endpoint shows the types of metadata the API accepts. Examples include unique identifiers, lines of business, group and subdivision identifiers, routing codes, associated campaigns and business rules, browser and device information. The endpoints also accept custom-defined attributes in key-value pairs if no existing field in the schema suits the type of metadata you wish to upload.

Customer

The OpenAPI specification for each customer endpoint shows the types of metadata the API accepts. Examples include unique identifiers, statuses, contact details, and location information. The endpoints also accept custom-defined attributes in key-value pairs if no existing field in the schema suits the type of metadata you wish to upload.