REST API: contacts
Create, inspect, export, and maintain contact records.
Contacts are organization records that can be created, listed, inspected, exported, and deleted through the REST API. Use a stable external identifier in your own system and treat a returned AgentStack contact identifier as the key for later reads or removal. A contact export should be an explicit operator job with a defined retention destination, not an automatic by-product of every conversation.
The agent-specific verification and resume settings govern how an embedded conversation may connect to a verified contact. Enabling or regenerating verification returns secret material; store it only in a protected server-side secret manager, rotate integrations after regeneration, and never return it to a browser. The runtime configuration includes guest-use behavior, but clients should not rely on undocumented response fields.
Deleting a contact is a consequential data action. Verify the contact identity, record the reason in your system, and follow the response envelope. For widget JWT details and visitor experience, read Identity verification; for contact-policy changes, apply the exact request shapes from the API reference.