Skip to main content

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.6.2 - Fleet Reference Validation Documentation
10th February 2026
This patch release clarifies the validation constraints for fleet reference fields in the API documentation and improves example values. No functional API behavior has changed.
Patch Release: Documentation-only changes that clarify existing validation rules. No breaking changes or functional modifications.

​
Documentation Updates

Updated:
  • FleetCreate.fleet_ref - Added validation constraint documentation
  • OnboardingInvitation.fleet_ref - Added validation constraint documentation
  • ShareAgreement.fleet_ref - Added validation constraint documentation and improved example value
Validation Rule: Fleet reference fields now explicitly document that only letters, numbers, spaces, dashes, and underscores are allowed. This constraint was always enforced by the API but is now clearly documented in the OpenAPI specification.Before:
fleet_ref:
  description: "Your internal fleet identifier. Use this to map Catena fleets back to your system. This value will be returned in webhooks and redirect URLs."
After:
fleet_ref:
  description: "Your internal fleet identifier. Use this to map Catena fleets back to your system. This value will be returned in webhooks and redirect URLs. Only letters, numbers, spaces, dashes, and underscores are allowed."
Example Value Improvement: The ShareAgreement.fleet_ref example was updated from an empty string to a realistic value (FLEET-12345) to better demonstrate proper usage.Impact:
  • No changes to API behavior
  • Existing integrations are unaffected
  • Validation rules remain the same as previous versions

​
Integration Notes

1

Review Fleet Reference Inputs

If you’re creating or updating fleets, ensure your fleet reference inputs comply with the documented validation:
# Valid fleet references
"FLEET-12345"
"Fleet_ABC"
"North America 001"
"customer-fleet-123"

# Invalid fleet references (will be rejected)
"fleet@123"       # Contains @ symbol
"fleet#abc"       # Contains # symbol
"fleet.123"       # Contains period
2

No Action Required

This is a documentation-only update. If your integration is currently working, no changes are needed.

​
Need Help?

API Reference

View complete endpoint documentation with current API structure

Contact Support

Questions about migrating your integration? Our team is here to help