Create Invitation
Create an invitation with a magic link to onboard a fleet.
Returns an invitation object with a unique ID that serves as the magic link token. Share this link with the fleet to begin the onboarding process. Once accepted, a share agreement is automatically created to enable data sharing.
Note: If an active, accepted, or declined invitation already exists for the same fleet_ref,
the invitation is refreshed (expiration extended, tokens regenerated if accepted,
reactivated if declined) and returned with status code 200 instead of 201.
Note: On refresh, limit_tsps and exclude_tsps are only updated when explicitly provided.
Omitting them (or sending null) leaves the existing restriction on the invitation unchanged —
it does not clear a previously set filter. To remove a limit_tsps/exclude_tsps restriction
on refresh, you must explicitly pass an empty list, e.g. "limit_tsps": [].
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
Pre-populate the fleet name during onboarding. The fleet can modify this during acceptance.
Pre-populate the fleet contact email. Optional but recommended for faster onboarding.
Pre-populate the fleet’s regulatory identifier (e.g., DOT number, EASA ID). Helps with fleet verification.
Pre-populate the type of regulatory ID provided (e.g., DOT, EASA, MC). Required if regulatory_id is set.
Pre-populate the phone number of the fleet
Pre-populate the website of the fleet
Pre-populate the country code of the fleet
The URL to redirect the user to after onboarding successfully on Catena Connect. Available query parameters: invitation_id, fleet_ref.
The URL to redirect the user to after failing to onboard on Catena Connect (i.e. declining an invitation, opening an expired invitation, etc). Available query parameters: invitation_id, fleet_ref.
Your webhook endpoint to receive real-time notifications for invitation acceptance, share agreement creation, and connection status updates. Must be HTTPS.
Restrict which telematics providers the fleet can connect to. Useful if you only need data from specific TSPs. If omitted, all available TSPs are shown. On refresh, this field is only updated when explicitly provided — omitting it leaves any existing restriction unchanged; pass an empty list ([]) to clear it. Cannot be combined with exclude_tsps.
Exclude specific telematics providers from the ones shown to the fleet. Useful if you want the fleet to have access to every TSP except a few. On refresh, this field is only updated when explicitly provided — omitting it leaves any existing restriction unchanged; pass an empty list ([]) to clear it. Cannot be combined with limit_tsps.
Defines which resources (vehicle, locations, users, etc.) the fleet must grant access to and the permission level (read, write) for each. If omitted, we will require READ permissions for all resources.
How long the invitation link remains valid (1-672 hours). Default is 24 hours. Consider longer durations for email campaigns.
Resources to request READ_WRITE access for, on top of the READ default for every other resource. Use this to bump a single resource (e.g. fuel_transaction) to read-write without having to enumerate every other resource. Cannot be combined with permissions — use permissions instead if you need an exact, narrower set of resources.
Deprecated: Use fleet_name instead. Pre-populate the fleet name during onboarding.
Deprecated: Use fleet_email instead. Pre-populate the fleet contact email.
Deprecated: Use fleet_regulatory_id instead. Pre-populate the fleet’s regulatory identifier.
Deprecated: Use fleet_regulatory_id_type instead. Pre-populate the type of regulatory ID.
Deprecated: Use fleet_phone instead. Pre-populate the phone number of the fleet.
Deprecated: Use fleet_website instead. Pre-populate the website of the fleet.
Deprecated: Use fleet_country_code instead. Pre-populate the country code of the fleet.
Response
Existing invitation refreshed (already exists for this fleet_ref)
The current status of the invitation (active, accepted, declined, or expired)
Pre-populate the fleet name during onboarding. The fleet can modify this during acceptance.
The JWT token used to pre-register the fleet. It allows the fleet to create connections after accepting the invitation even without registering a user. Value is set after the invitation is accepted.
The refresh token used to pre-register the fleet. It allows the fleet to create connections after accepting the invitation even without registering a user. Value is set after the invitation is accepted.
Your webhook endpoint to receive real-time notifications for invitation acceptance, share agreement creation, and connection status updates. Must be HTTPS.
The URL to redirect the user to after onboarding successfully on Catena Connect. Available query parameters: invitation_id, fleet_ref.
The URL to redirect the user to after failing to onboard on Catena Connect (i.e. declining an invitation, opening an expired invitation, etc). Available query parameters: invitation_id, fleet_ref.
Defines which resources (vehicle, locations, users, etc.) the fleet must grant access to and the permission level (read, write) for each.
The fleet’s regulatory identifier (e.g., DOT number).
The type of regulatory ID (e.g., ‘DOT’, ‘MC’).
The ISO 3166-1 alpha-3 country code for the fleet.
Deprecated: Use fleet_name instead.
Deprecated: Use fleet_email instead.
Deprecated: Use fleet_regulatory_id instead.
Deprecated: Use fleet_regulatory_id_type instead.
Deprecated: Use fleet_phone instead.
Deprecated: Use fleet_website instead.
Deprecated: Use fleet_country_code instead.