Skip to main content

Fleetio Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Fleetio location.
fleetio_api.png

Fleetio

Create a Fleetio Destination​

  1. Click the + icon on the Nexset that will be sent to the Fleetio destination, and select the Send to Destination option from the menu.

  2. Select the Fleetio connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Fleetio account, and click Next; or, create a new Fleetio credential for use in this flow.

  3. In Nexla, Fleetio destinations can be created using pre-built endpoint templates, which expedite destination setup for common Fleetio endpoints. Each template is designed specifically for the corresponding Fleetio endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Fleetio destinations can also be configured manually, allowing you to send data to Fleetio endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Fleetio endpoints. Each template is designed specifically for the corresponding Fleetio endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Acquisition

    Creates a new vehicle acquisition record in Fleetio with financing details such as lease, loan, or purchase information. Use this endpoint to automatically populate Fleetio with vehicle acquisition data sourced from dealership systems, financial platforms, or procurement tools.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v1/acquisitions. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data is mapped to the correct Fleetio acquisition fields before activating the destination.

    For details about the required and optional fields for acquisition records, refer to the Fleetio Acquisitions API documentation.

    Update Acquisition

    Updates an existing vehicle acquisition record in Fleetio with new financing details or corrected information. Use this endpoint when acquisition data has changed in an external system and you need to keep Fleetio records in sync.

    • This endpoint sends a PATCH request to https://secure.fleetio.com/api/v1/acquisitions/{'{id}'}, where {id} is the ID of the acquisition record to update.

    • Enter the ID of the acquisition to update in the Acquisition ID field. This value identifies which existing Fleetio acquisition record will be modified.

      • The Acquisition ID can be sourced from a prior Nexla data flow that ingested acquisition data from Fleetio, or from another system that stores Fleetio acquisition IDs.

    For details about updatable acquisition fields, refer to the Fleetio Acquisitions API documentation.

    Create Expense Entry

    Creates a new expense entry for a vehicle in Fleetio. Use this endpoint to automatically log vehicle-related expenses—such as tolls, fines, or miscellaneous costs—sourced from expense management systems, credit card feeds, or accounting platforms.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v1/expense_entries. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the vehicle ID and expense details required by the Fleetio API.

    For details about the required and optional fields for expense entries, refer to the Fleetio Expense Entries API documentation.

    Update Expense Entry

    Updates an existing expense entry in Fleetio with corrected or additional information. Use this endpoint when expense data needs to be updated after initial entry.

    • This endpoint sends a PATCH request to https://secure.fleetio.com/api/v1/expense_entries/{'{id}'}, where {id} is the ID of the expense entry to update.
    • Enter the ID of the expense entry to update in the Id field. This is a required parameter that identifies which existing Fleetio expense record will be modified.

    For details about updatable expense entry fields, refer to the Fleetio Expense Entries API documentation.

    Create Fault

    Creates a new fault record for a vehicle in Fleetio with code, status, and occurrence details. Use this endpoint to automatically log diagnostic trouble codes (DTCs) or other fault events sourced from telematics systems, OBD readers, or vehicle monitoring platforms.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v1/faults. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the required vehicle ID, fault code, and other relevant fault details.

    For details about the required and optional fields for fault records, refer to the Fleetio Faults API documentation.

    Update Fault

    Updates an existing fault record in Fleetio with new code, status, occurrence details, or other information. Use this endpoint to keep fault records current as diagnostic data changes in telematics or maintenance systems.

    • This endpoint sends a PATCH request to https://secure.fleetio.com/api/v1/faults/{'{id}'}, where {id} is the ID of the fault record to update.

    • Configure the following optional parameters to provide additional context for the fault update:

      • Id (required): The ID of the fault record to update in Fleetio.
      • Vehicle ID: The ID of the vehicle associated with the fault.
      • Fault Code: The diagnostic fault code identifier (e.g., a DTC code such as P0300).
      • Count: The number of times this fault has occurred.
      • Description: A detailed description of the fault.
      • External ID: An external identifier for the fault from another system, useful for cross-referencing records.
      • Last Occurred At: The timestamp when the fault was last detected.
      • Name: The name or title of the fault.
      • Status: The current status of the fault (e.g., active, resolved).
      • Source: The source system or device that reported the fault.

    For details about updatable fault fields and accepted values, refer to the Fleetio Faults API documentation.

    Create Vehicle

    Creates a new vehicle record in Fleetio with details such as make, model, VIN, license plate, and financial information. Use this endpoint to automatically provision new vehicles in Fleetio when they are added to your fleet through dealership integrations, procurement systems, or other data sources.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v1/vehicles. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes required vehicle fields such as name, make, model, and VIN as needed by your Fleetio account configuration.

    For details about the required and optional fields for vehicle records, refer to the Fleetio Create a Vehicle API reference.

    Create a New Fuel Entry

    Creates a new fuel entry in Fleetio representing a fuel transaction, including vendor and odometer information. Use this endpoint to automatically log fuel transactions sourced from fuel card integrations, pump data feeds, or fleet card management systems.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v1/fuel_entries. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the vehicle ID, fuel quantity, and other required fuel entry fields.

    For details about the required and optional fields for fuel entries, refer to the Fleetio Fuel Entries API documentation.

    Record an Odometer or Engine-Hour Reading

    Records an odometer or engine-hour meter reading for a vehicle in Fleetio. Use this endpoint to automatically submit meter readings sourced from telematics devices, GPS trackers, or manual data collection systems, keeping vehicle mileage and usage data current in Fleetio.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v1/meter_entries. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the vehicle ID, meter value, and the date/time of the reading.

    For details about meter entry fields and the bulk API, refer to the Fleetio Bulk API reference.

    Create a Service/Maintenance Entry

    Creates a new service or maintenance entry for a vehicle in Fleetio. Use this endpoint to automatically log completed maintenance work sourced from shop management systems, work order platforms, or external maintenance tracking tools.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v2/service_entries. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the vehicle ID, service description, and completion date as required by the Fleetio API.

    For details about the required and optional fields for service entries, refer to the Fleetio Create Service Entry API reference.

    Archive / Delete a Vehicle Record

    Archives or deletes a vehicle record in Fleetio. Use this endpoint to automatically remove vehicles from your active fleet when they are decommissioned, sold, or otherwise removed from service, based on data from asset management or disposal systems.

    :::warning Important Deleting a vehicle record in Fleetio is a destructive action. Verify that the correct Vehicle ID is being passed before activating this destination. This action may not be reversible. :::

    Create a New Part Record

    Creates a new part record in the Fleetio parts inventory. Use this endpoint to automatically add new parts to Fleetio when they are procured or received, sourcing data from purchase orders, supplier integrations, or inventory management systems.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v1/parts. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the required part fields such as name, part number, and quantity.

    For details about the required and optional fields for parts, refer to the Fleetio Parts API documentation.

    Create a New Purchase Order

    Creates a new purchase order in Fleetio. Use this endpoint to automatically generate purchase orders in Fleetio from data sourced from procurement systems, accounting platforms, or supplier portals.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v1/purchase_orders. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the required purchase order fields as defined by the Fleetio API.

    For details about the required and optional fields for purchase orders, refer to the Fleetio Purchase Orders API documentation.

    Create a New Contact

    Creates a new contact in Fleetio, such as a driver, vendor, or other person associated with your fleet. Use this endpoint to automatically provision contacts in Fleetio from HR systems, onboarding platforms, or directory services.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v2/contacts. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the required contact fields such as first name, last name, and any other fields required by your Fleetio account configuration.

    For details about the required and optional fields for contacts, refer to the Fleetio Contacts API documentation.

    Create a New Issue / Defect Report

    Creates a new issue or defect report in Fleetio. Use this endpoint to automatically log vehicle issues sourced from driver inspection apps, telematics alerts, or external defect tracking systems.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v2/issues. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the required issue fields such as vehicle ID, description, and reported date.

    For details about the required and optional fields for issues, refer to the Fleetio Issues API documentation.

    Update an Existing Fuel Entry

    Updates an existing fuel entry in Fleetio with corrected or supplemental information. Use this endpoint when fuel transaction data needs to be amended after initial creation.

    For details about updatable fuel entry fields, refer to the Fleetio Fuel Entries API documentation.

    Update an Existing Service Entry

    Updates an existing service or maintenance entry in Fleetio. Use this endpoint to amend service records when additional work details, cost corrections, or completion information becomes available after initial entry.

    For details about updatable service entry fields, refer to the Fleetio Create/Update Service Entry API reference.

    Create a New Vehicle Assignment

    Creates a new vehicle assignment in Fleetio, associating a contact or driver with a specific vehicle. Use this endpoint to automatically assign vehicles to drivers sourced from scheduling systems, dispatch platforms, or HR systems.

    • This endpoint sends a POST request to https://secure.fleetio.com/api/v1/vehicle_assignments. Data from the Nexset is sent as a JSON body in the request.
    • No additional template parameters are required. Ensure that the Nexset data includes the required vehicle ID and contact ID fields.

    For details about the required and optional fields for vehicle assignments, refer to the Fleetio Vehicle Assignments API documentation.

    Update an Existing Part Record

    Updates an existing part record in the Fleetio parts inventory. Use this endpoint to synchronize part quantities, pricing, or other attributes when inventory data changes in procurement or warehouse management systems.

    For details about updatable part fields, refer to the Fleetio Parts API documentation.

    Update an Existing Purchase Order

    Updates an existing purchase order in Fleetio with new or corrected information. Use this endpoint to keep Fleetio purchase orders synchronized with changes in procurement or accounting systems.

    For details about updatable purchase order fields, refer to the Fleetio Purchase Orders API documentation.

    Update an Existing Contact

    Updates an existing contact record in Fleetio. Use this endpoint to keep driver or vendor information current when contact details change in HR systems, directories, or onboarding platforms.

    For details about updatable contact fields, refer to the Fleetio Contacts API documentation.

    Update / Resolve an Existing Issue

    Updates or resolves an existing issue in Fleetio. Use this endpoint to automatically close or update issue records when they have been addressed in an external maintenance management system, work order platform, or dispatch tool.

    For details about updatable issue fields and resolution statuses, refer to the Fleetio Issues API documentation.

Configure Manually​

Fleetio destinations can be manually configured to send data to any valid Fleetio API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Fleetio API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Fleetio API from the Method pulldown menu. Common methods used with Fleetio include:

    • POST: For creating new records (vehicles, fuel entries, service entries, contacts, etc.)
    • PATCH: For updating existing records with new or corrected data
    • DELETE: For archiving or removing records from Fleetio

Data Format​

  1. Select the format in which the Nexset data will be sent to the Fleetio API from the Content Format pulldown menu. Fleetio's REST API accepts data in JSON format. Nexla will automatically convert the data to JSON for each API call.

API Endpoint URL​

  1. Enter the URL of the Fleetio API endpoint to which you want to send the Nexset data in the URL field. For update or delete operations, include the ID of the record to be modified at the end of the URL (e.g., https://secure.fleetio.com/api/v1/vehicles/12345).

All Fleetio API endpoints use the base URL https://secure.fleetio.com/api/. Refer to the Fleetio Developer Portal for a complete list of available endpoints and their URL formats.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include the Authorization or Account-Token headers—these are automatically included by Nexla based on your Fleetio credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Fleetio destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Fleetio API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Fleetio API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Fleetio API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Fleetio API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to Fleetio, open the destination resource menu and select Activate.

    The Nexset data will not be sent to Fleetio until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.