Fetch the documents of all the drivers

• Endpoint: v1/documents
• Description: This endpoint retrieves a list of all documents associated with the drivers in a company's fleet.
• Use Case: Fleet managers have to manage all the compliance and audit requirements. In order to do so, they will require the accurate documents. The Fleet Managers can use this endpoint to fetch all the fuel receipts of their drivers and ensure all the regulations are met on time.

Fetch a specific document using its ID

• Endpoint: v1/documents/{id}
• Description: This endpoint retrieves detailed information for a specific document associated with a driver by using the document's unique ID.
• Use Case: Documents such as a bill of lading provide the shipment details that are in transit. By fetching the Bill of Lading using its ID, the Fleet Manager is then able to access and verify the shipping, as well as the consignee and the shipper details.

Create a new document

• Endpoint: v1/documents
• Description: This endpoint allows the Fleet Manager to create a new document such as a Bill of Lading, or a Fuel Receipt.
• Use Case: Having documents digitally allows for a quick access and verification. The Fleet Manager can quickly create a new document, and add details such as Consignee, Shipper, Weight, and the destination. This makes it easy for the opposite party to view and verify the details at their end.

Update the status of a document

• Endpoint: /v2/documents/{id}
• Description: This endpoint allows the Fleet Mangers to update critical information such as a Shipper, or a Consignee information on a document.
• Use Case: There may be situations where the specific information regarding shipment may require an update, such as a destination or a stopover. To ensure the driver is on the desired route and does not miss the shipment guidelines, Fleet Managers can use this endpoint to update the document and its contents accordingly.

Delete a document

• Endpoint: /v2/documents/{id}
• Description: Use this endpoint to delete an existing document.
• Use Case: This endpoint allows you to organize your documents properly by allowing you to delete an existing document. Sometimes, the Fleet Managers may end up have the same document at multiple places. To manage the documents efficiently and to ensure the drivers are sent proper documents, the Fleet Manager can delete a duplicate document. This ensure smoother operations.

Fetch the document forms of your company

• Endpoint: v2/document/forms
• Description: Document forms are structured templates that are used to collect specific information. They server as standardized formats for uploading and storing documents such as the Bill of Lading and others.
• Use Case: Fleet Managers can use this endpoint to fetch all the document forms of company, and ensure all drivers are using the forms as is without any modification. This standardized approach makes it easy for the companies to meet all the regulatory and compliance requirements.

Fetch the documents for a specified time range

• Endpoint: v2/documents
• Description: This allows you to specify a time period for fetching documents and shows the list of documents for that particular time range.
• Use Case: Fleet Managers can use this endpoint to fetch all the documents of company, by specifying the start and the end date. This makes it convenient if the Fleet Manager does not have the ID of the document, or wants to check the documents that were generated during a particular period.

Fetch a document using its ID (v2)

• Endpoint: v2/documents/{id}
• Description: This endpoint retrieves detailed information for a specific document associated with a driver by using the document's unique ID.
• Use Case: Documents such as a bill of lading provide the shipment details that are in transit. By fetching the Bill of Lading using its ID, the Fleet Manager is then able to access and verify the shipping, as well as the consignee and the shipper details.

Create a new document (v2)

• Endpoint: v2/documents
• Description: This endpoint allows the Fleet Manager to create a new document such as a Bill of Lading, or a Fuel Receipt.
• Use Case: Having documents digitally allows for a quick access and verification. The Fleet Manager can quickly create a new document, and add details such as Consignee, Shipper, Weight, and the destination. This makes it easy for the opposite party to view and verify the details at their end.

Update the status of a document (v2)

• Endpoint: /v2/documents/{id}
• Description: This endpoint allows the Fleet Mangers to update critical information such as a Shipper, or a Consignee information on a document.
• Use Case: There may be situations where the specific information regarding shipment may require an update, such as a destination or a stopover. To ensure the driver is on the desired route and does not miss the shipment guidelines, Fleet Managers can use this endpoint to update the document and its contents accordingly.

📘

AI Bulk Upload Endpoints

The following 3 endpoints, must be used in the order mentioned-below. This will allow you to view the categories, generate the URLs for document upload, and submit them for AI processing.

List AI-Enabled Document Categories

• Endpoint: v4/documents/categories
• Description: This endpoint returns the list of document category identifiers that are available for AI-powered processing for your company. The returned categories (e.g. driver_license, bill_of_lading, fuel_receipt) are the values you pass as document_category when submitting documents for AI processing. The list is filtered by your company's enabled document classifications (e.g. some Driver Qualification categories are subject to the Workforce Management Subscription).
• Use Case: Integration partners building automated document ingestion need to know which document types they can submit for AI processing to avoid rejected submissions and ensuring a smooth upload workflow.

Generate Document Upload URLs

• Endpoint: v4/documents/bulk/upload_urls
• Description: This endpoint generates one or more secure upload URLs for document files that will be submitted for AI processing. You provide a list of file types (1–500 files per request) and receive a unique upload URL per file. After uploading files directly to these URLs, you pass the returned file_path values to the Submit Documents for AI Processing endpoint. Upload URLs expire after 10 minutes, expires_in_seconds key can be utilized to check the url expiry time..
• Use Case: An enterprise customer onboarding a new fleet of drivers needs to upload hundreds of qualification documents at once. Their internal system calls this endpoint to get upload URLs for each file, uploads the documents directly, and then submits them for AI extraction — all without manual interaction with the Motive dashboard.

Submit Documents for AI Processing

• Endpoint: v4/documents/bulk/process
• Description: This endpoint submits one or more uploaded documents for AI-powered categorization and field extraction. You provide the file paths from the previous upload step, the desired document categories, and an optional driver assignment. Processing is asynchronous — the endpoint returns immediately with a session ID to track progress. Supports 1–500 files per request.
• Use Case: A Professional Services team migrating a customer's existing driver qualification files into Motive can submit an entire batch of scanned CDLs, medical certificates, and MVRs in a single API call. Motive's AI automatically extracts fields like expiration dates, license numbers, and driver names — eliminating hours of manual data entry and ensuring documents are audit-ready from day one.