Skip to main content
The WotNot API allows you to programmatically manage your WotNot account, knowledge bases, conversations, contacts, bots, and other resources without using the WotNot dashboard. Use the API to integrate WotNot with your existing applications, automate repetitive tasks, or build custom workflows around your AI agents.
The WotNot API uses Bearer token authentication. Keep your API token secure and do not expose it in client-side applications.

What you can do with the API

WotNot APIs cover several areas of the platform.

Knowledge Bases

Create knowledge bases, add data sources, remove sources, and check training status.

Conversations

Create conversations, send messages, update variables, manage assignees, and close conversations.

Contacts

Create new contacts or update existing contacts using API requests.

Bots

Create bots, retrieve bot flows, deploy flows, and fetch the list of bots in an account.

Webhooks

Configure a webhook to receive conversation-related events from WotNot.

Endpoints

Endpoint URL for all API integration with WotNot APIs are:

Knowledge Base

Contact

  • Create contacts: Create new contacts and update existing ones in a single request.

Conversation

Webhook

  • Set webhook URL: Choose where your account receives conversation events, and which events to receive.

Bot

  • Create bot: Create a new bot from an existing bot.
  • Get bot flow: Get a bot’s flow JSON so you can edit it.
  • Deploy bot: Deploy a bot with an updated flow JSON.
  • List bots: List the bots in your account with their status, channels and owner.

Account management

  • Get account roles: List the user roles in your account, what each can access, and who has it.
  • Invite user: Invite a user to your account with a role and get their invitation link.
  • Update user role: Change the role of a user in your account.
  • Remove user: Remove a user from your account.
The API paths currently use both /v1 and /api/v1 prefixes. Use the endpoint path exactly as documented for each operation.

HTTP status codes

Troubleshooting

401 Unauthorized

A 401 response generally indicates that the account token is missing, invalid, or does not have access to the requested resource. Check that:
  • The Authorization header is present.
  • The token is valid.
  • The token is passed using the Bearer <token> format.

400 Bad Request

A 400 response indicates that the request could not be processed. Check that:
  • Required fields are included.
  • Request parameters use the expected format.
  • IDs belong to the correct WotNot account.
  • The request body contains valid JSON when required.

404 Not Found

A 404 response indicates that the requested resource could not be found. Check that the resource ID is correct and that the resource belongs to the account associated with your API token.
Last modified on October 23, 2026