> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senderz.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Validate connection

> Confirm your credentials and read workspace metadata.

A cheap endpoint that 200s with your workspace metadata. Use it to validate an API key and workspace ID before doing real work — it's also what Make uses to render the connection chip.

## Get current workspace

```http theme={null}
GET /api/v1/public/me
```

Authenticated with the [`X-Sender-Tenant` + `X-API-Key`](/en/api-reference/authentication) headers. No parameters.

### Response

<ResponseField name="tenant" type="object">
  <Expandable title="tenant">
    <ResponseField name="id" type="string">Workspace UUID.</ResponseField>
    <ResponseField name="slug" type="string">Workspace slug (your public Workspace ID).</ResponseField>
    <ResponseField name="name" type="string">Workspace display name.</ResponseField>
    <ResponseField name="plan" type="string">Current plan.</ResponseField>
    <ResponseField name="status" type="string">Workspace status.</ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="apiVersion" type="string">
  The API version, e.g. `2026-01`.
</ResponseField>

<CodeGroup>
  ```bash cURL theme={null}
  curl https://api.senderz.app/api/v1/public/me \
    -H "X-Sender-Tenant: your-workspace-slug" \
    -H "X-API-Key: your-api-key"
  ```

  ```json Response theme={null}
  {
    "success": true,
    "data": {
      "tenant": {
        "id": "0f1e2d3c-…",
        "slug": "your-workspace-slug",
        "name": "Your Store",
        "plan": "c5000",
        "status": "active"
      },
      "apiVersion": "2026-01"
    }
  }
  ```
</CodeGroup>

<Note>
  A `404 Workspace not found` means the tenant reference doesn't resolve; a
  `401` means the key is missing or wrong.
</Note>