List the gateways your messages can leave through
Only the gateways you connected yourself. If your plan lends SendKuy's senders, messages can also leave through a shared gateway that is not in this list — leave gateway_id out when sending and we pick one.
Try it — GET /gateways
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 gateways:readAuthorization: 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: gateways:read
Query Parameters
The meta.next_cursor from the previous page.
Rows per page. Defaults to 20, capped at 100.
1 <= value <= 100Response Body
application/json
application/json
application/json
application/json
curl -X GET https://app.sendkuy.com/api/v1/gateways \ -H "Authorization: Bearer sk_live_YOUR_API_KEY"{ "meta": { "has_more": true, "next_cursor": "string" }, "data": [ { "object": "gateway", "id": "gw_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3", "channel": "email", "type": "string", "name": "string", "address": "string", "status": "active", "is_default": true, "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" } ]}