New required field `tokenId` added to a response object
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
A new field tokenId (type string) has been added to a response object's properties and simultaneously added to its required array alongside the existing token, connector, and expiresAt fields. Because tokenId is marked required in the schema, any client that validates responses against this spec will now fail if the server doesn't return it — and any server implementation that doesn't yet emit it will produce invalid responses. This is a breaking schema change for strict consumers.