---
title: "Return the account behind an API key"
method: POST
path: "/v1/account/info"
tags: ["Account"]
---

# Return the account behind an API key

`POST /v1/account/info`

## Request

- Base URL: `https://api.relayshield.net`
- URL: `https://api.relayshield.net/v1/account/info`
- Auth: one of:
  - API key in header `X-RS-API-KEY`
  - HTTP bearer

Free and unmetered. Used to confirm a key is live and to label a connected account. This is the endpoint RelayShield's own Zapier, n8n and Make integrations call to test a connection.

**Billing.** Free. This endpoint is not metered.

## Request body

- object: Send an empty JSON object.

## Response `200`

Success. `ok` is true and `data` holds the result.

- object
  - `ok` true, required
  - `data` object, required
    - `plan` string: Plan name on the key, e.g. `personal`.
    - `intel_access` boolean: True when the key carries a Threat Intelligence subscription.
    - `calls_this_month` integer: Metered calls made in the current month.
    - `customer_id` string: Billing customer ID. Empty for AWS Marketplace keys.
    - `email` string: Account email.
    - `active` boolean: False when the key has been deactivated.

## Other responses

- `401`: The API key is missing, invalid or inactive.
- `405`: Wrong HTTP method. Every endpoint is POST.

---

[API](https://skmtc.dev/relayshield/apis/relayshield-api.md) · [All operations](https://skmtc.dev/relayshield/apis/relayshield-api/llms.txt) · [OpenAPI document](https://skmtc.dev/relayshield/apis/relayshield-api/revisions/4d4721b936dd?raw)