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.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Body
API model for creating a fleet invitation
Your internal fleet identifier. Use this to map Catena fleets back to your system. This value will be returned in webhooks and redirect URLs.
Pre-populate the fleet name during onboarding. The fleet can modify this during acceptance. Only letters, numbers, and spaces are allowed.
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
1 - 2083Pre-populate the country code of the fleet
^\w{3}$The URL to redirect the user to after onboarding successfully on Catena Connect. Available query parameters: invitation_id, fleet_ref.
1 - 2083The 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.
1 - 2083Your webhook endpoint to receive real-time notifications for invitation acceptance, share agreement creation, and connection status updates. Must be HTTPS.
1 - 2083Restrict which telematics providers the fleet can connect to. Useful if you only need data from specific TSPs. If omitted, all available TSPs are shown.
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.
1 <= x <= 672Deprecated: 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.
1 - 2083Deprecated: Use fleet_country_code instead. Pre-populate the country code of the fleet.
^\w{3}$Response
Existing invitation refreshed (already exists for this fleet_ref)
API model for reading a fleet invitation
Contains the complete invitation state including acceptance/decline status. Use this to track invitation lifecycle and retrieve tokens for accepted invitations.
Unique invitation identifier
When the invitation was created
The magic link that is used to open Catena Connect and accept the invitation. Share this URL with the fleet to begin onboarding.
The expiration date and time of the invitation
The number of hours the invitation is valid for.
The current status of the invitation (active, accepted, declined, or expired)
active, accepted, declined, expired, deleted Pre-populate the fleet name during onboarding. The fleet can modify this during acceptance.
The date and time the invitation was accepted. Null if not accepted.
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.
1 - 2083The URL to redirect the user to after onboarding successfully on Catena Connect. Available query parameters: invitation_id, fleet_ref.
1 - 2083The 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.
1 - 2083Restrict which telematics providers the fleet can connect to. Useful if you only need data from specific TSPs. If omitted, all available TSPs are shown.
The slug of your organization
Your organization ID requesting access to fleet data
The reason provided by the fleet for declining the invitation. Null if invitation was not declined.
The date the invitation was declined by the fleet. Null if invitation was not declined.
Your internal fleet identifier. Use this to map Catena fleets back to your system. This value will be returned in webhooks and redirect URLs.
Defines which resources (vehicle, locations, users, etc.) the fleet must grant access to and the permission level (read, write) for each.
The contact email for the fleet.
The fleet's regulatory identifier (e.g., DOT number).
The type of regulatory ID (e.g., 'DOT', 'MC').
The phone number for the fleet.
The website URL for the fleet.
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.
The Catena fleet ID created after accepting the invitation. Null if invitation has not been accepted.