Skip to main content
Released 18th August 2026

​
TMS Invitation Pre-Registration Tokens

This release adds pre-registration token fields to TMS invitation responses, enabling downstream systems to authenticate on behalf of a newly invited TMS before full registration is complete.
Backward-compatible addition: Existing integrations continue to work. The new fields are additive — update your response handling to take advantage of pre-registration tokens.

​
New response fields

All TMS invitation endpoints now return two additional required fields in the TmsInvitationRead schema:

​
Affected endpoints

The following endpoints now include pre_registration_access_token and pre_registration_refresh_token in their responses:
  • GET /v2/orgs/tms-invitations — list response items
  • POST /v2/orgs/tms-invitations — 200 and 201 responses
  • GET /v2/orgs/tms-invitations/{tms_invitation_id} — 200 response
  • PATCH /v2/orgs/tms-invitations/{tms_invitation_id} — 200 response
  • POST /v2/orgs/tms-invitations/{tms_invitation_id}/accept — 200 response
  • POST /v2/orgs/tms-invitations/{tms_invitation_id}/decline — 200 response
Example response (partial):

​
What to update

1

Handle the new token fields

Update your response parsing to read pre_registration_access_token and pre_registration_refresh_token from TMS invitation responses. These tokens can be used to authenticate API calls on behalf of the invited TMS before they complete registration.
2

Store tokens securely

Treat these tokens with the same care as regular access and refresh tokens — store them securely and do not log or expose them.

​
Need help?

Organizations API reference

View complete TMS invitation endpoint documentation.

Contact support

Questions about updating your integration? Our team is here to help.