---
title: "Change the sign-in address (slug)"
method: PATCH
path: "/accounts/slug"
tags: ["Account Management"]
---

# Change the sign-in address (slug)

`PATCH /accounts/slug`

## Request

- Base URL: `https://api.quiva.ai`
- URL: `https://api.quiva.ai/accounts/slug`
- Auth: one of:
  - HTTP bearer
  - API key in header `x-api-key`
- TypeScript: <https://skmtc.dev/quivaworks/apis/quiva-ai-gateway/docs/accounts/slug/patch.ts> (a function with typed inputs; its response is checked against the schema)

Root user only. Changes the account's sign-in slug, which is also its sign-in subdomain, and publishes its DNS record. The caller confirms with an email code (see `GET /accounts/email-code`), exactly as for rename. The old slug stays as an alias (up to 3). The owner is notified by email. A refused change keeps the code, so it can be resubmitted.

## Request body

- ChangeAccountSlugRequest
  - `slug` string, required: 3-63 lowercase letters, numbers or hyphens. Reserved platform names are refused.
  - `email_code` string, required: Email verification code, see `GET /accounts/email-code`

## Response `200`

Success

- object
  - `data` AccountSlugResponse, required
    - `slug` string
    - `slug_aliases` string[]: Previous slugs, up to 3, that still sign in
    - `slug_published` boolean: False while the sign-in address's DNS record is not yet published

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `409`: The slug is taken, or the account already holds 3 previous slugs

## Changes

- **2026-11-12** `700eb1ace61a`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway/changes/accounts/slug/patch.md)

---

[API](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway.md) - [All operations](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway/llms.txt) - [OpenAPI document](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway/revisions/700eb1ace61a?raw)