Read one gateway

Try it — GET /gateways/{id}

Your API key

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.

Your SendKuy origin

Authorization

bearerAuth gateways:read

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: gateways:read

Path Parameters

id*string

The prefixed id of the object.

Response Body

`application/json`

curl -X GET https://app.sendkuy.com/api/v1/gateways/gw_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3 \  -H "Authorization: Bearer sk_live_YOUR_API_KEY"

{  "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"  }}

Authorization

Path Parameters

Response Body

200application/json

401application/json

403application/json

404application/json

429application/json

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`