---
title: "Delete a profile"
method: DELETE
path: "/profiles/{id}"
tags: ["Profiles"]
---

# Delete a profile

`DELETE /profiles/{id}`

## Request

- Base URL: `https://api.rizamo.com/v1`
- URL: `https://api.rizamo.com/v1/profiles/{id}`
- Auth: HTTP bearer

For good: what is in it cannot be restored. Its posts go, deleted ones included, with their history and preview links (posts already published stay on the networks), and so do its posting times, its upload requests and connect links, its other events, and its media that no post of another profile uses. Its short links stay and keep working, with no profile. People and invitations limited to some profiles, API keys, agents and webhook endpoints lose it from their profiles: a key or agent that reached only this profile is revoked, and an endpoint that took only its events is disabled (`disabledReason` `profile_deleted`). Refused (409) while it has accounts (move each to another profile, or remove it, first), when it is the team's only profile, while one of its posts is going out, and while a person or an open invitation reaches no other profile, naming them. Only an owner deletes a profile, signed in as themselves within the last 15 minutes (with their session, as the web app does), or an API key an owner let remove accounts and delete profiles when making it (Developers in the web app). Other API keys and agents are refused (403), and a key reaches only its own profiles.

## Path parameters

- `id` string, required: The profile's id (`prof_`).

## Response `200`

OK

- object
  - `id` string, required

## Other responses

- `400`: `invalid_request`: A field is missing or wrong, or the request cannot be done as asked: the message names the field or says what to change.
- `401`: `unauthorized`: No API key or sign-in, or the key does not work: it was deleted, or it expired.
- `403`: `forbidden`: The caller may not do this: the key or agent lacks the scope (the message names it), or the action needs another role or a fresh sign-in.
- `404`: `not_found`: No such object, or it is outside your team or the profiles your key reaches.
- `409`: `conflict`: The object's state does not allow it now, such as an account that needs a new login. `queue_empty`: A post with `queue: true` whose profile has no posting times: set them, or give a `scheduledAt`. `queue_full`: No posting time free for the post's accounts in the next 90 days: add times, or give a `scheduledAt`. `idempotency_key_in_use`: A request with this `Idempotency-Key` is still running: try again in a moment.
- `413`: `payload_too_large`: The body is over 1 MB: files go up through the upload links of `POST /v1/media`.
- `415`: `unsupported_media_type`: The body is not JSON: send it with `Content-Type: application/json`.
- `429`: `rate_limited`: Over one of Rizamo's limits, or a network asked Rizamo to slow down: wait for `Retry-After` seconds, or as long as the message says.
- `500`: `internal`: Our side failed: retry, and send the `requestId` if it keeps failing.
- `503`: `timeout`: The request took too long to work out, most often a report: try again in a moment, or ask a report for a shorter period or one profile.

---

[API](https://skmtc.dev/rizamo/apis/rizamo-api.md) - [All operations](https://skmtc.dev/rizamo/apis/rizamo-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rizamo/apis/rizamo-api/revisions/31b0c1b1ffb5?raw)
