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

# Send an insight card

> Shows a card with your own context, such as a record from your CRM, to the agent on a call in progress. A card has a `title`, an optional `icon` and up to 20 `blocks`: field lists, text, links, chips, metrics and ticket references. The answer says who got the card and how, but holds none of its content.

**Delivered or pending.** When an agent has answered the call, the card is shown to that agent at once: `delivery` is `delivered` and `recipient` names the agent. When nobody has answered yet, the card is kept for 1 hour and shown to the agent who answers: `delivery` is `pending` and `recipient` is `null`. A pending card shows only on Phone versions that fetch cards when a call is answered; older Phone versions do not show it. A call uuid that matches no call, and a call of another company, get the same pending answer, so the answer never tells whether a call exists. A call that has ended returns `409 INSIGHT_CARDS.CALL_ENDED`.

**Which call.** `callUuid` is the call uuid that call webhooks such as [`call.started`](/guides/webhooks/events/calls#call-started) carry as `call_uuid`, in any letter case. The numeric call id is not accepted here.

**The body.** The body is at most 32 KiB. The card's `title` is at most 120 characters and every other text value at most 2,000, counted in Unicode code points. Every URL must be an absolute `https:` URL. Unknown fields are refused at every level. A wrong shape (not JSON, an unknown or missing field, a wrong type) is `400 VALIDATION.INVALID_BODY` and a value out of range (too long, too many, not in its list, not `https:`) is `422 VALIDATION.INVALID_FIELD`, both with the JSON path in `target`, for example `blocks[1].url`.

**Retries.** Send an `Idempotency-Key` to retry safely. A `201` is stored for 24 hours: the same key with the same call and the same body, byte for byte, returns it again with `Idempotent-Replay: true` and sends no second card. The same key with another body, or for another call, is `422 IDEMPOTENCY_KEY_REUSED`. While the first request with a key is still running, a retry gets `409 INSIGHT_CARDS.IDEMPOTENCY_KEY_IN_USE`: retry it shortly. The `422` and the `409` leave the key with the request that holds it. Any other refusal does not use up the key, so a retry with the same key runs again.

**Limits.** Your company can hold a limited number of pending cards at a time. Over that limit you get `429 INSIGHT_CARDS.PENDING_LIMIT_REACHED` with `Retry-After`. Requests also count against the gateway's per-company rate limit, one budget shared with the Call tags operations under `/v1/calls/`.

**Authentication.** Send your API credentials with the first request. The `401` comes from the gateway without a `WWW-Authenticate` challenge, so an HTTP client that waits for a challenge before it sends credentials never sends them.

Moving from the Cue Cards API? [Migrate from Cue Cards](/guides/insight-cards/migrate-from-cue-cards) maps every field.



## API Specification

The full API specification for this endpoint is available in the [documentation index](https://help.cloudtalk.io/llms.txt).


## Related topics

- [Migrate from Cue Cards to insight cards](https://help.cloudtalk.io/guides/insight-cards/migrate-from-cue-cards.md)
- [Cue Cards](https://help.cloudtalk.io/en/articles/11154936-cue-cards.md)
- [Create CueCard](https://help.cloudtalk.io/api-reference/cuecard/create-cuecard.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.