Keep the group together as they play.

Represent a group of players who want to play together. Connect that group to the supported invitation and matchmaking workflows in your game.
Formation and membership
Party leadership
Queue integration
Contextual draft · Release status, supported versions, and limits await owner review.

Plan the integration

Formation and membership

Define invitations and membership for a group that wants to enter play together.

Party leadership

Decide who owns group actions and what should happen when that player disconnects.

Queue integration

Pass group membership into the supported queue workflow; test partial failure and cancellation.
ILLUSTRATIVE GAME WORKFLOW

let a group request a match together.

This example describes a game-team workflow. Service connections and game rules require explicit integration; it does not imply automatic bindings.

Scope and responsibilities

A party groups players. Invitations, reconnects, leadership, and group queueing need explicit lifecycle rules; persistence between matches is not implied.

Related services

Explore complementary services for your game, with integration details for each building block.
SERVICE 1

Friends

Help players stay connected. Explore Friends
SERVICE 2

Presence

Show when friends are ready to play. Explore Presence
SERVICE 3

Matchmaking

Connect players to their next match. Explore Matchmaking

Setup prerequisites

A test workspace with access to Parties.
Step 1: pending
A confirmed API version and documented permissions for the workflow.
Step 2: pending
Client and backend tests for successful, invalid, repeated, and interrupted requests.
Step 3: pending
Review integration availability →
YOUR NEXT CHAPTER STARTS HERE

Build the backend for your next game.

Explore the services and plan your first player experience.