Create the Conversations API chatbot

The Conversations API is in Controlled Availability. Endpoints, behaviors, and configuration surfaces may change during CA. Contact your Moveworks account team to participate.

Every Conversations API request carries an Assistant-Name header naming the chatbot it is addressed to. You create that chatbot once, in Moveworks Setup, before configuring authentication.

Do this first. The Bot Name it produces is an input to whichever authentication guide you follow next.

Prerequisites

Your account team has enabled the Conversations API for your org. Until they have, Conversations API requests return 404 regardless of what you configure here.
Edit access to Moveworks Setup for your org.

Create the chatbot

In Moveworks Setup, go to Chat Platforms > Manage Chatbots > Chatbots, then create a new entry:

Field	Value
Channel	`conversationsrestapi`
Select Connector	`conversations_rest_api`
Bot ID	Any UUID you generate
Bot Name	Your choice. Include `-capi` so it is recognizable alongside your other chatbots, for example `acme-capi`. This is the value you send in `Assistant-Name`.
Bot Friendly Name	Match the Bot Name

Save the entry, then record the Bot Name.

The Assistant-Name header must match the Bot Name exactly. A mismatch is rejected at the API rather than falling back to a default chatbot.

Next steps

Continue with the authentication guide that matches how your integration will identify users:

Set up authentication with Okta, for users signing in through your Okta tenant.
Set up authentication with Azure AD (Entra ID), for users signing in through your Entra tenant.
Set up service-to-service authentication, for a backend acting on behalf of known users.