Create a partner invite.

Reimbursement coverage of specific RFIDs and vehicles (allow) can be declared here only when the invited email address resolves to an existing user of the partner's operator, since the listed entities are validated against that user — listed RFIDs must belong to the invite's partner and must either belong to that user or have no owner, and listed vehicles must belong to the invite's partner. When no such user exists yet, coverage of specific entities is rejected with a validation error; create the invite without it and declare the covered set via the update endpoint once the invite is accepted.

Declaring coverage of specific entities also assigns them to the invited user: listed RFIDs with no owner get that user as their owner, and that user is added to the users of listed vehicles they are not yet a user of. This happens when the invite is accepted if it is still pending, or as part of the write itself when the invite is already accepted — including on the update endpoint.

Experimental endpoint — not yet a stable contract. partner-invites/v2.0 ships as experimental / beta. While experimental, its schema and behaviour may change without a version bump — including breaking changes within v2.0 itself. Anyone consuming it does so for evaluation only, or by coordinating adoption with their account manager so changes can be sequenced with them. It graduates to a stable, version-locked contract (where the normal breaking-change rules apply) only when this experimental notice is removed.