---
title: "Set the status"
method: POST
path: "/api/v1/inbox/{event_id}/classify"
tags: ["Inbox"]
---

# Set the status

`POST /api/v1/inbox/{event_id}/classify`

## Request

- Base URL: `https://app.argorant.com`
- URL: `https://app.argorant.com/api/v1/inbox/{event_id}/classify`
- Auth: HTTP bearer

Stores a status on the conversation: any key from GET /api/v1/reply-statuses, built in or one of your own stages. The built-in interested status has the key `positive`; `interested` is accepted as the same thing.

| Cost | What it does | Key scopes |
| --- | --- | --- |
| Free | Writes | `argorant:manage_lists` |

## Path parameters

- `event_id` string, required

## Headers

- `Idempotency-Key` string
- `X-Request-Id` string

## Request body

- object
  - `classification` string, required: A status key, for example positive, meeting_booked or proposal_sent.

## Response `200`

OK

- object
  - `ok` boolean
  - `id` string
  - `classification` string

## Other responses

- `401`: 401 Unauthorized. `unauthorized` when the API key is missing, wrong or revoked.
- `403`: 403 Forbidden. `scope_missing` when the key lacks argorant:manage_lists.
- `404`: 404 Not found. `not_found` when the item does not exist in your workspace.
- `409`: 409 Conflict. `idempotency_conflict` when the Idempotency-Key was used with another body.
- `422`: 422 Validation error. `validation_error` when a field has the wrong type or is missing.
- `429`: 429 Too many requests. `rate_limited` when too many requests this minute.

---

[API](https://skmtc.dev/argorant/apis/argorant-api.md) · [All operations](https://skmtc.dev/argorant/apis/argorant-api/llms.txt) · [OpenAPI document](https://skmtc.dev/argorant/apis/argorant-api/revisions/4bc28c0085b6?raw)