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.1 - Fleet Name Validation Documentation
10th February 2026
This patch release clarifies the validation constraints for fleet name fields in the API documentation. 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:
  • FleetUpdate.fleet_name - Added validation constraint documentation
  • OnboardingInvitation.partner_provided_fleet_name - Added validation constraint documentation
Validation Rule: Fleet name fields now explicitly document that only letters, numbers, and spaces are allowed. This constraint was always enforced by the API but is now clearly documented in the OpenAPI specification.Before:
fleet_name:
  description: "The fleet's preferred name for their organization"
After:
fleet_name:
  description: "The fleet's preferred name for their organization. Only letters, numbers, and spaces are allowed."
Impact:
  • No changes to API behavior
  • Existing integrations are unaffected
  • Validation rules remain the same as previous versions

​
Integration Notes

1

Review Fleet Name Inputs

If you’re creating or updating fleets, ensure your fleet name inputs comply with the documented validation:
# Valid fleet names
"ABC Logistics"
"Fleet 123"
"North America Operations"

# Invalid fleet names (will be rejected)
"ABC-Logistics"  # Contains hyphen
"Fleet_123"      # Contains underscore
"ABC@Logistics"  # Contains special character
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