---
title: "Invite user to party"
method: POST
path: "/v2/session/invite/{sessionId}"
tags: ["session"]
---

# Invite user to party

`POST /v2/session/invite/{sessionId}`

Sends a party invitation to another Xbox Live user.

## Parameters

- **sessionId** (path) - The service config ID (SCID), typically `7492BACA-C1B4-440D-A391-B7EF364A8D40`
- **xuid** (body) - The Xbox User ID of the person to invite
- **sessionName** (body) - The unique session name from `/session/create`

## How Invitations Work

1. The invited user receives a notification on their Xbox device
2. They can accept to join the party
3. Once accepted, they appear in the session's member list

## Example Request

```json
{
  "xuid": "2533274817903789",
  "sessionName": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}
```

## Requirements

- You must be a member of the session to invite others
- The invited user must have their privacy settings configured to receive invites

## Path parameters

- `sessionId` string, required

## Request body

- object
  - `xuid` string, required
  - `sessionName` string, required

## Response `200`

Invitation sent successfully

- ApiResponse — Standard API response wrapper. All endpoints return responses in this format.
  - `content` unknown, required
  - `code` integer, required — HTTP status code from the upstream API. Common values: 200 (success), 400 (bad request), 401 (unauthorized), 404 (not found), 410 (deprecated/gone), 429 (rate limited), 500 (server error)

## Other responses

- `401` — Invalid or missing API key
- `404` — Resource not found
- `429` — Rate limit exceeded

---

[API](https://skmtc.dev/xbl/apis/openxbl-api.md) · [All operations](https://skmtc.dev/xbl/apis/openxbl-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/xbl/openxbl-api/revisions/e5df7bdca559/schema)