# Create a Vigil conversation message

> POST /api/vigil/conversations/{conversationId}/messages on the Vigilbase One API.

Source: https://docs.vigilbase.com/one/api/reference/vigil/post-vigil-conversations-conversation-id-messages

`POST https://one.vigilbase.com/api/vigil/conversations/{conversationId}/messages`

## Authorizations

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`. Organisation API keys can't call this endpoint: it acts for a signed-in person or changes how people sign in.

## Path parameters

- `conversationId` (string, required)

## Body (application/json)

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`. API keys can't call this.
curl --request POST \
  --url 'https://one.vigilbase.com/api/vigil/conversations/{conversationId}/messages' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{}'
```