---
title: "Test API key"
method: POST
path: "/auth"
tags: ["Auth"]
---

# Test API key

`POST /auth`

## Request

- Base URL: `https://services.certseal.com/api/v1`
- URL: `https://services.certseal.com/api/v1/auth`
- Auth: HTTP bearer

Verifies the bearer API key and returns a human-readable
`username` for the connected workspace. Intended for use as
Zapier's "Test Auth" / connection-label endpoint — a 2xx
response confirms the key is valid and the returned `username`
is safe to surface in the integration UI.

## Response `200`

API key is valid.

- AuthResult
  - `workspaceId` string: Stable identifier of the workspace the API key is bound to. Suitable as a connection UID for integration platforms (e.g. Make) since it does not change when the owner is renamed.
  - `username` string, required: Display name of the workspace owner. Falls back to the owner's email when no name is set. Safe to show as a Zapier connection label.

## Other responses

- `401`: Missing, malformed, expired, or revoked API key.
- `429`: Too many requests for this API key. Honour the `Retry-After` response header (seconds) or the `detail.retryAfter` field.

---

[API](https://skmtc.dev/certseal/apis/certseal-com-api.md) · [All operations](https://skmtc.dev/certseal/apis/certseal-com-api/llms.txt) · [OpenAPI document](https://skmtc.dev/certseal/apis/certseal-com-api/revisions/9097f49f49f5?raw)