The REST and SignalR APIs documented here are more complex than the client SDKs. Consider using the Lobby C++ SDK or Matchmaking C++ SDK instead, unless those SDKs don’t meet your needs.
Members
entityType string
The type of the
entity
whose subscription changed. Clients may only care about this field if they
added multiple entities to the
same session.
Example: title_player_account
entityId string
The ID of the
entity
whose subscription changed. Clients may only care about this field if they
added multiple entities to the
same session.
Example: 6C6B908A2B5B9A4
topic string
A topic string, matching the topic string returned when subscribing to
resources. This field allows the client to keep
track of which messages are for which resources they subscribed to.
Example: Opaque~Topic~String~6183258
status string
The status of the subscription change.
unsubscribeReason string optional
A reason for unsubscription, that can be optionally provided by the service
handling the unsubscribe request.
Example: ResourceOwningServiceDefinedReason
traceId string
A W3C TraceContext trace-id.
The client should log this field so it can be included if you need to send a bug
report to the PlayFab team.
Example: 4bf92f3577b34da6a3ce929d0e0e4736