Create Onboarded Carriers Bulk

Authentication

  • Include your Access-Token in the header of your requests.

  • Include your x-api-key The API key provided by GenLogs. This header must be included in the request.

Permissions

The external-api-create-onboarded-carrier-contact permission is required to access this endpoint.

Endpoint

  • URL: https://api.genlogs.io/onboarded-carrier/bulk/contacts

  • Method: POST

Headers

  • Access-Token: (string, required): Access token obtained from the "Create Access Token" endpoint.

  • X-Api-Key (string, required): The API key provided by GenLogs.

Request body

  • contacts (list, object, required): List of contacts to be created. Including:

    • usdot (string, required): Carrier USDOT number. Must be a non-empty value.

    • name (string, optional): Contact name.

    • phone (string, optional): Contact phone number

    • email (string, optional): Contact email address.

Request Example:

Response:

  • 200 OK: A JSON object containing two lists for:

    • Success: created carrier contact(s) with relevant information including usdot, name and id.

    • Failed: failed creation with index and reason.

  • 400 Bad Request: If required parameters are missing or invalid.

  • 401 Unauthorized: If the authentication credentials (Access-Token) is missing or incorrect.

  • 403 Forbidden: If the permission has not been added to your user.

  • 500 Internal Server Error: If there is an issue on the server that prevents processing the request.

Response Body:

200 OK – Contacts Deleted Successfully

400 Bad Request

Returned when:

  • The provided contacts list is malformed or missing

  • Malformed usdot number

401 Unauthorized

  • When access-token is missing or expired

403 Forbidden

404 Not Found

Bulk create onboarded carrier contacts

post

Creates multiple onboarded carrier contacts for the authenticated customer in a single request. Each contact entry is validated using the same rules as the single-contact create flow. At least one contact must be valid for the operation to succeed. The operation follows the same authorization, repository, caching, and creation logic as the single-contact create flow.

Authorizations
Body
Responses
chevron-right
200

Contacts processed successfully.

application/json
post
/onboarded-carrier/bulk/contacts

Last updated