---
title: "Check status page slug availability"
method: GET
path: "/me/status-pages/slug-check"
---

# Check status page slug availability

`GET /me/status-pages/slug-check`

## Request

- Base URL: `https://app.yoping.me/api/v1`
- URL: `https://app.yoping.me/api/v1/me/status-pages/slug-check`
- Auth: API key in cookie `yp_session`

Reports whether a slug is free to claim. Malformed and reserved slugs are simply `available: false`, never an error.

## Query parameters

- `slug` string, required

## Response `200`

Availability of the slug.

- object: Uniform success envelope: the payload is always under `data`.
  - `data` StatusPageSlugCheck, required
    - `available` boolean, required

## Other responses

- `401`: Not authenticated (code `unauthorized`): missing, invalid, or expired session; invalid login credentials; or a Bearer token, which this surface rejects.
- `403`: Forbidden. Code `forbidden` for a cross-origin (CSRF) request blocked by origin validation or for API-key management attempted without a browser session; `account_suspended` when a suspended account attempts a mutation; `account_deleted` when an account in its deletion grace window calls a non-exempt route.
- `429`: Too many requests (code `rate_limited`). A global per-IP budget of 300 requests/minute (burst 60) applies to every endpoint; login, signup, and test alerts have tighter dedicated limits.

---

[API](https://skmtc.dev/yoping/apis/yopingme-api.md) · [All operations](https://skmtc.dev/yoping/apis/yopingme-api/llms.txt) · [OpenAPI document](https://skmtc.dev/yoping/apis/yopingme-api/revisions/76d8deb40173?raw)