---
title: "Log a call, a meeting, a note or a follow-up"
method: POST
path: "/api/v1/rest/crm/activities"
tags: ["CRM"]
---

# Log a call, a meeting, a note or a follow-up

`POST /api/v1/rest/crm/activities`

## Request

- Base URL: `https://api.custodo.ai`
- URL: `https://api.custodo.ai/api/v1/rest/crm/activities`
- Auth: HTTP bearer

Records something against a customer or a deal. Two fields decide what it means and they are never merged: `completed_at` is when it HAPPENED (a call you are writing up), `due_at` is when it is PLANNED (a follow-up nobody has done yet). Give one, or both when you are logging a call and booking the next one. A note is completed the moment it is written and takes no due date. A planned activity becomes the deal’s next action, which is what stops it going quiet — so booking one is usually the useful half.

## Headers

- `X-Tenant-Id` string, uuid

## Request body

- object
  - `subject_type` 'party' | 'deal', required: `deal` for a trattativa, `party` for a customer with no deal in play.
  - `subject_id` string, uuid, required: The deal id it hangs off, or the anagrafica id (from anagrafiche_search_parties) for a customer.
  - `kind` 'task' | 'call' | 'meeting' | 'note' | 'email' | 'document', required: `call`, `meeting`, `task`, `note`, `email` or `document`.
  - `title` string, required: One line, in Italian.
  - `body` string: What was said, or what has to be done.
  - `due_at` string, date-time: When it is planned, ISO-8601 with a timezone: 2026-09-03T15:00:00Z.
  - `completed_at` string, date-time: When it actually happened, ISO-8601 with a timezone. Backdating is normal.
  - `direction` 'inbound' | 'outbound': Only for a call or an email: who rang whom.
  - `outcome` string: How it went, in a few words.
  - `duration_minutes` integer

## Response `200`

Done. `data` is the tool’s own answer.

- RestResult
  - `ok` true, required
  - `data` unknown, required

## Other responses

- `400`: The arguments did not validate: `error.message` names the field, what it expects and what arrived.
- `401`: No API key, or one that is malformed, unknown, revoked or expired.
- `403`: The call never ran: the module is off for this organisation, the credential lacks the permission or the module, the tier does not cover it, or the tool is destructive and the key was not minted for that.
- `409`: The record is in a state that does not allow it — under legal hold, already sent, already closed. `error.code` says which.
- `422`: The tool ran and refused, in a sentence of its own (`TOOL_REFUSED`): the message says what to change. Retrying the same call will not help.
- `429`: The API key has spent its minute, or its day. Every request a key makes counts. See `Retry-After`.

---

[API](https://skmtc.dev/custodo/apis/custodo-integrazioni.md) · [All operations](https://skmtc.dev/custodo/apis/custodo-integrazioni/llms.txt) · [OpenAPI document](https://skmtc.dev/custodo/apis/custodo-integrazioni/revisions/16d336d3ec2a?raw)