Fuel Card Resource Support
This release extends theResourceEnum across the Integrations API to include fuel_card as a supported resource type. All endpoints that accept or return a resource field now support fuel card data synchronization.
Backward-compatible addition: Existing integrations are unaffected. The
fuel_card value is purely additive to the existing resource enum.New resource type
fuel_card added to ResourceEnum
fuel_card added to ResourceEnum
The Example — filter resource operations by fuel card:Example — check data freshness for fuel card:The response will now include entries where
fuel_card value is now a valid option for the resource field across all Integrations API endpoints. This enables scheduling, monitoring, and backfilling of fuel card data from connected TSP providers.Affected endpoints:Example — create a fuel card sync schedule:
resource is "fuel_card".Fuel Card Webhook Support
This release extends webhook event support to include fuel card as a resource type, enabling real-time notifications for fuel card operations across your fleet.Backward-Compatible: All existing webhook subscriptions and integrations continue to work without any changes.
New Resource Type
Fuel card added to ResourceEnum
Fuel card added to ResourceEnum
The Example — fuel card resource operation event payload:
fuel_card value has been added to the ResourceEnum schema and is now supported across all webhook event types. You can subscribe to fuel card events using the same event patterns as other resource types.Affected event schemas:BaseExecutionEventBaseResourceOperationEventBaseScheduleEventExecutionFailedExecutionStaledResourceOperationCreatedResourceOperationFailedResourceOperationSucceededScheduleDeactivated
Need help?
API reference
View complete endpoint documentation for the Integrations API
Contact support
Questions about integrating fuel card data? Our team is here to help