---
title: "Create Account Correspondence"
method: POST
path: "/accounts/{account_id}/correspondence"
tags: ["Documents"]
---

# Create Account Correspondence

`POST /accounts/{account_id}/correspondence`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/accounts/{account_id}/correspondence`
- Auth: HTTP bearer

Record ONE message, call or note against an account.

`correspondence_date` is when it HAPPENED, not when it was recorded - the
generated documents read it as the relationship's timeline, so a wrong
date is worse than a missing record.

## Path parameters

- `account_id` string, required: The account.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- CorrespondenceCreateRequest: One piece of correspondence with an account. Mirrors `campaign_builder.routers.correspondence.CorrespondenceCreate`. `channel` and `direction` are NOT closed here, because the app does not close them either: it stores whatever it is given. The values it reads elsewhere are `email` / `linkedin` / `call_notes` and `inbound` / `outbound`, and a value outside those is accepted and simply never matched by a filter.
  - `channel` string, required: `email`, `linkedin` or `call_notes`.
  - `direction` string, required: `inbound` or `outbound`.
  - `subject` string, nullable
  - `content` string, required: The body. Indexed for retrieval.
  - `correspondence_date` string, date-time, required: When it happened - NOT when it was recorded. Required.
  - `stakeholder_id` string, nullable: The person at the account, when known.
  - `external_id` string, nullable: Your id for this message. The app uses it to skip duplicates on `/correspondence/import`, so send it to make an import re-runnable.

## Response `201`

Successful Response

- ApiResponseDocumentPayload
  - `data` DocumentPayload, required: An open envelope for one document, folder or questionnaire. Open on purpose: a Library document carries extraction metadata, a questionnaire carries per-provider processing detail, and a generated deal document carries `structured_data` and `highlights` whose shape is the generator's rather than this contract's. Pinning those would silently drop whatever the app learned to return that this file had not caught up on.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)