Build on Nonverbia with the REST API, OAuth and webhooks.
API authentication: tokens and OAuth
Webhooks: events and signatures
<aside> 💡
New here? Start with the Developer quickstart. It takes about ten minutes to create a token, make your first call and receive your first webhook.
</aside>
| Page | Read it when you want to… |
|---|---|
| API quickstart | Set up your first integration, step by step |
| API authentication: tokens and OAuth | Choose between API tokens and OAuth, pick scopes, or build an app other users connect to |
| REST API reference | Look up an endpoint, its parameters and its responses |
| Webhooks: events and signatures | Receive meetings as they finish, verify signatures and read the payload reference |
| API errors and rate limits | Handle failures and stay within the limits |
https://api.nonverbia.com/api/v1Authorization: Bearer with a personal access token (nvb_pat_…) or an OAuth 2.0 access tokencapture.processed, signed with HMAC-SHA256project in the API, and a meeting is a captureThe MCP server at https://api.nonverbia.com/mcp lets AI assistants such as Claude and ChatGPT read your meetings. It uses the same tokens and scopes. Set it up in the app under Integrations → MCP server.