> ## Documentation Index
> Fetch the complete documentation index at: https://docs.humanly.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Writes (coming soon)

> Standard Connect write conventions — idempotency and validation

<Warning>
  **Not yet implemented.** This page describes the **planned MS7 (PLAT-42)** conventions.
</Warning>

Connect write routes (push data **to** a vendor) will require:

## Idempotency

Send a unique idempotency key **per logical write operation**, and **reuse the same key** for any retries of that operation:

```
X-Idempotency-Key: <partner-generated-uuid>
```

Safe retries with the same key return the same outcome without duplicate side effects. Generate a **new** key only when starting a **new** operation — not on every HTTP retry. Keys will be stored in a shared `connect_idempotency_keys` table (qualifi-api via internal-router).

## Validation errors

Failed validation returns **400** with code `VALIDATION_ERROR` and field-level `details` — same envelope as other Connect routes. See [Error envelope](/platform/error-envelope).

## Sync vs async

* **Sync writes** — complete in the HTTP response.
* **Async writes** — return **202 Accepted** with a job ID; poll [Async jobs](/connect/async-jobs).

Vendor-specific routes choose sync or async based on vendor API behavior.

## Related

* [Reads](/connect/reads) — pagination (planned)
* [Getting started](/connect/getting-started) — stub order (available today)