API keys
The Pivra API is coming soon. No endpoint accepts API keys yet, so keys cannot be created today.
Updated 8 Oct 2026
The Pivra API is coming soon. No Pivra endpoint accepts an API key yet, so the API Keys section in Settings โ Security no longer creates keys. We would rather say so than issue a key that does nothing.
When the API launches, this article will list the endpoints, how to authenticate, and the plans that include it.
What works today
- The chat widget uses its own public embed key, shown in Install โ Embed code. It is safe to put in website code and is unrelated to API keys.
- Integrations (HubSpot, Mailchimp, Zapier, Make, ServiceM8 and others) send your leads to other tools without any coding. See Integrations in the dashboard.
- Actions send webhooks to your own systems when a lead is captured, a conversation starts or a visitor asks for a person.
- CSV export of your leads, from the dashboard.
Keys created before the API was marked coming soon
If you created an API key earlier, it does not grant access to anything. You can revoke it in Settings โ Security โ API Keys; nothing that uses it will break.
Frequently asked questions
Is the API key the same as the embed key? No. The embed key (shown in Install โ Embed code) is a public key for the chat widget. API keys were meant for server-to-server access and are not accepted anywhere yet.
Can I send messages to my chatbot programmatically? Not yet. The chat endpoint is designed for the website widget. Programmatic access is part of the API that is coming soon.
I need an integration that isn't listed. Email support@pivra.ai and tell us what you want to connect. Actions (webhooks) cover many cases today.
Was this helpful?
If you have questions or suggestions, email us at support@pivra.ai .