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

# Quickstart

> Choose the shortest path to a working Chert integration.

Most teams start in one of four places. Pick the path that matches where your users already work.

\| Goal | Start here | Time |
\|---|---|
\| Send iMessage from your own backend | [Messaging API quickstart](/api/quickstart) | 5 minutes |
\| Add Chert to Salesforce records | [Salesforce overview](/salesforce/overview) | 30 minutes |
\| Send from HubSpot contacts and workflows | [HubSpot overview](/hubspot/overview) | 15 minutes |
\| Triage replies in Slack | [Slack overview](/slack/overview) | 10 minutes |

## API path in one command

If you already have a signing secret, this is the shortest possible API check:

```bash theme={null}
curl https://console.trychert.com/api/v1/send \
  -H "Authorization: Bearer $CHERT_SIGNING_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"phone":"+14155551234","body":"Hi Sam - testing Chert."}'
```

Use the full [Messaging API quickstart](/api/quickstart) when you need credentials, reply streaming, webhooks, or HMAC signing.

## What to read next

* [Usage examples](/api/usage-examples) — send, follow up, attach media, stream replies.
* [Authentication](/api/authentication) — bearer auth for scripts, HMAC for production.
* [Receiving replies](/api/receiving-replies) — webhooks, retries, and event signatures.

## See also

* [Introduction](/introduction)
* [Messaging API overview](/api/overview)