> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catenatelematics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# v2.41.0 - TMS Invitation Pre-Registration Tokens

> TMS invitation responses now include pre-registration access and refresh tokens.

**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.

<Check>
  **Backward-compatible addition:** Existing integrations continue to work. The new fields are additive — update your response handling to take advantage of pre-registration tokens.
</Check>

### New response fields

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

| Field | Type | Description |
| - | - | - |
| `pre_registration_access_token` | string | Short-lived access token for the invited TMS prior to completing registration. |
| `pre_registration_refresh_token` | string | Refresh token for the invited TMS prior to completing registration. |

### Affected endpoints

<AccordionGroup>
  <Accordion title="TMS Invitations" icon="envelope">
    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):**

    ```json theme={null}
    {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "status": "pending",
      "pre_registration_access_token": "<access_token>",
      "pre_registration_refresh_token": "<refresh_token>"
    }
    ```
  </Accordion>
</AccordionGroup>

### What to update

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

***

## Need help?

<CardGroup cols={2}>
  <Card title="Organizations API reference" icon="building" href="/api-reference/organizations-api">
    View complete TMS invitation endpoint documentation.
  </Card>

  <Card title="Contact support" icon="life-ring" href="mailto:support@catenaclearing.io">
    Questions about updating your integration? Our team is here to help.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.