> ## 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.27.0 - TSP Exclusion for Invitations

> Adds support for excluding specific telematics service providers when creating fleet invitations.

**Released 21st July 2026**

## TSP Exclusion for Invitations

This release adds the `exclude_tsps` field to the invitations API, giving you finer control over which telematics service providers (TSPs) are available when a fleet accepts an invitation.

<Check>
  **Backward-compatible addition:** All existing invitation workflows continue to work without modification. The `exclude_tsps` field is optional.
</Check>

### New fields

<AccordionGroup>
  <Accordion title="exclude_tsps — Invitation TSP exclusion list" icon="filter">
    A new `exclude_tsps` field is now available on invitation create requests and is returned in all invitation read responses.

    Use `exclude_tsps` to block specific TSPs from being shown to a fleet when they accept an invitation. This is the complement to the existing `limit_tsps` field:

    | Field | Behaviour |
    | - | - |
    | `limit_tsps` | Allow **only** the listed TSPs. Cannot be combined with `exclude_tsps`. |
    | `exclude_tsps` | Allow all TSPs **except** the listed ones. Cannot be combined with `limit_tsps`. |

    **Affected endpoints:**

    * `POST /v2/orgs/invitations` — new optional request body field
    * `GET /v2/orgs/invitations` — new field in each item of the response list
    * `GET /v2/orgs/invitations/{invitation_id}` — new field in the response
    * `POST /v2/orgs/invitations/{invitation_id}/accept` — new field in the response
    * `POST /v2/orgs/invitations/{invitation_id}/decline` — new field in the response

    **Create an invitation with excluded TSPs:**

    ```bash theme={null}
    curl -X POST 'https://api.catenatelematics.com/v2/orgs/invitations' \
      -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
      -H 'Content-Type: application/json' \
      -d '{
        "fleet_id": "019ddd87-eedd-710f-967c-1c6cc72ac985",
        "exclude_tsps": ["provider_slug_1", "provider_slug_2"]
      }'
    ```

    **Example response (invitation object):**

    ```json theme={null}
    {
      "id": "01234567-89ab-cdef-0123-456789abcdef",
      "fleet_id": "019ddd87-eedd-710f-967c-1c6cc72ac985",
      "limit_tsps": null,
      "exclude_tsps": ["provider_slug_1", "provider_slug_2"],
      "status": "pending"
    }
    ```
  </Accordion>
</AccordionGroup>

***

## Need help?

<CardGroup cols={2}>
  <Card title="Organizations API reference" icon="building" href="/api-reference/organizations-api">
    View complete endpoint documentation for invitations and fleet management.
  </Card>

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


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