databases
GET /v1/databases/my-address
The address this request came from, to suggest for a database allow-list.
Authentication
Send an API key as a bearer token. The key must carry the databases.view permission; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/databases/my-address \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Gated on databases.view. A database hostname publishes both an A and an AAAA record, so a client that prefers IPv6 connects from its IPv6 address and is refused if only its IPv4 address is listed. The dashboard offers this address (and the one its own origin sees, which may be the other family) so the customer can add both. Read from the forwarding header our own ingress writes, never from a value the caller supplies; address is null when it cannot be resolved.
Response
| Name | Type | Required | What it is |
|---|---|---|---|
address | object | Yes | The caller's public IP address, or null when it cannot be resolved. |
family | object | Yes | — |
Errors this endpoint can return
401 · 403