---
title: "Create a team"
method: POST
path: "/v1/teams"
tags: ["Teams"]
---

# Create a team

`POST /v1/teams`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/teams`
- Auth: HTTP bearer

```bash
curl -X POST https://api.subscriby.net/v1/teams \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"name": "Research Collective"}'
```

The caller becomes the team **owner**. Ownership is not a membership row: the owner cannot be removed from the team, cannot be re-roled, and is the only account permitted to rename or delete it.

A new team starts empty. Add people with [Team Members](https://docs.subscriby.net/api/v1/reference/team-members), and give them something to hold with [Roles](https://docs.subscriby.net/api/v1/reference/roles). Answers `201` with the team and emits `team.created`.

## Headers

- `Idempotency-Key` string, uuid, required

## Request body

- StoreTeamRequest: A team's name: required on create, optional on update. Ownership does not transfer through this body, and membership moves through its own routes.
  - `name` string, required: The team's name, up to 255 characters; the only mutable field.

## Response `201`

The new team.

- object
  - `data` TeamResource, required: A team: the tenant every project, role and group hangs off. Every creator owns a personal team; further teams are a Growth capability.
    - `id` string, required: The team's id, the value a token's team scope names.
    - `name` string, required: The team's name.
    - `owner_user_id` string, required: The user who owns the team; deleting it is theirs alone.
    - `personal` boolean, required: Whether this is the creator's personal team, the one created with the account, which cannot be deleted.
    - `created_at` string, nullable, required: When the team was created, ISO 8601.

## Other responses

- `400`: `IDEMPOTENCY_KEY_MISSING`: every write needs an `Idempotency-Key` header. Send a fresh UUID per distinct operation.
- `401`: `AUTHENTICATION_REQUIRED`: the request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an `sbt_test_` token on production).
- `403`: `TOKEN_MISSING_ABILITY`: the token is valid but does not carry the ability this endpoint requires; `error.context.required_ability` names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers `FORBIDDEN`, `TEAM_TIER_REQUIRED` or `CONNECTOR_TIER_REQUIRED` with the same status, and says so in its own description. On this endpoint: `TEAM_TIER_REQUIRED`: below the Growth tier; nothing changes.
- `409`: `IDEMPOTENCY_KEY_REUSED`: the key was already used in the last 24 hours with a different request body.
- `422`: `VALIDATION_FAILED`: the payload broke a rule, and `error.fields` maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with `error.message` saying why and no `fields`.
- `425`: `IDEMPOTENCY_REPLAY_IN_PROGRESS`: the first request with this key is still running; retry in a few seconds and the original response is replayed.
- `429`: `RATE_LIMITED`: the token has spent its 300 requests a minute or 10,000 an hour; `Retry-After` says when the next one is accepted.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)