SendKuy API
API Reference

Send a failed message again

Creates a fresh delivery for the same recipient and body. The original row keeps its own status; this answers with the new one.

Try it — POST /messages/{id}/resend

Kept for this tab only — it disappears when you close it, and it is never sent anywhere except as the Authorization header on the call below.

Authorization

bearerAuth messages:write
AuthorizationBearer <token>

Authorization: Bearer sk_live_.... Keys in the query string or the request body are refused — a URL is logged by every proxy it passes, and that is how customer keys leak.

A key carries scopes. A call outside them answers 403 with insufficient_scope and names the scope it wanted.

In: header

Scope: messages:write

Path Parameters

id*string

The prefixed id of the object.

Header Parameters

Idempotency-Key?string

Any unique string, one per logical request. Retrying with the same key returns the first answer instead of doing the work twice, and answers with Idempotent-Replay: true.

Lengthlength <= 255

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST https://app.sendkuy.com/api/v1/messages/msg_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3/resend \  -H "Authorization: Bearer sk_live_YOUR_API_KEY"
{  "data": {    "object": "message",    "id": "msg_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3",    "channel": "email",    "status": "queued",    "to": "+6281234567890",    "body": "string",    "subject": "string",    "contact_id": "con_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3",    "campaign_id": "string",    "scheduled_at": "2019-08-24T14:15:22Z",    "sent_at": "2019-08-24T14:15:22Z",    "error": "string",    "created_at": "2019-08-24T14:15:22Z",    "updated_at": "2019-08-24T14:15:22Z"  }}