---
title: "Invite a user to the team"
method: POST
path: "/v2/invite_teams"
tags: ["team"]
---

# Invite a user to the team

`POST /v2/invite_teams`

Sends an invitation to a user to join a specified team. It requires parameters such as the team's unique identifier and the email address of the user to be invited. The retailer team, identified by a unique ID, manages access and can also invite suppliers.

## Request body

- V2CreateUserTeamInviteRequest
  - `inviteTeam` V2InviteTeam, required
    - `managerTeamId` string — The unique identifier of the retailer team. The retailer team handles access management and can send invitations to users, including suppliers.
    - `roleIds` Authv2RoleTypes[], required — The team permissions. Users can be assigned either retailer or supplier permissions: - Retailer full: Provides users full access, allowing them to modify administration settings, campaigns, reviews, team manager roles, and team settings. - Retailer report view: Provides users with read only access to dashboards, campaigns, and reporting data. - Supplier full: Provides users full access, allowing them to modify administration settings, campaigns, and team settings. - Supplier report view: Provides users with read only access to dashboards, campaigns, and reporting data.
    - `teamId` string, required — A unique identifier for the team linked to the user who will receive the invitation.
    - `emailToInvite` string, required — The email address of the user who will be invited to join the team.
    - `inviteUrl` string — The base invitation url emailed to the user to respond to their invitation and continue the onboarding process.
    - `languageCode` 'EN_US' | 'CS_CZ' | 'FR_FR' | 'HU_HU' | 'IT_IT' | 'JA_JP' | 'KO_KR' | 'PT_BR' | 'SK_SK' | 'ES_ES' — Language code as per ISO 639-1 format.

## Response `200`

The invite user team

- V2CreateUserTeamInviteResponse
  - `invitationToken` string — The invitation_token of the team.

## Other responses

- `400` — There was a problem with input.
- `401` — Access denied due to insufficient permissions.
- `403` — Login failed or token not valid.
- `default` — An unexpected error response.

---

[API](https://skmtc.net/citrusad/apis/citrus-auth-api.md) · [All operations](https://skmtc.net/citrusad/apis/citrus-auth-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/citrusad/citrus-auth-api/versions/a040003c7378/schema)