# acceptEditedContactSuggestion

Accept a text or email reply card with the person's own words (`text`) in place of the draft; it SENDS. Only when the person asks for THIS card by name, by its suggestionId; when their trust for the card's kind asks first, the write says how to ask. Leave `senderUserId` out: it names a customer reply's sender and is refused on any other card; Ask Goliath sends only as the person. In Ask Goliath `acceptPairedActions` is refused (accept each paired card on its own); over HTTP it also accepts them, and `replyInThread` answers in the email thread.

- Call: `POST https://server.goliathdata.com/api/v1/call` with `{ "operationId": "acceptEditedContactSuggestion", "variables": {...} }`
- Scope: `WRITE`
- Type: mutation
- Idempotency: honors `Idempotency-Key` (24 h)
- Rate-limited: no

## Variables

- `suggestionId`: `ID!` (required)
- `text`: `String!` (required)
- `senderUserId`: `ID`
- `replyInThread`: `Boolean`
- `acceptPairedActions`: `Boolean`

## Response (data, an example)

```json
{
  "contactSuggestionMutation": {
    "acceptEditedContactSuggestion": {
      "id": "<ID>",
      "contactId": "<ID>",
      "status": "PENDING"
    }
  }
}
```

## Example

```bash
curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "operationId": "acceptEditedContactSuggestion",
    "variables": {
      "suggestionId": "<suggestionId>",
      "text": "<String>"
    }
  }'
```