Verify

Allows user to verify if a carrier has been observed in the Genlogs Sensor network near the origin, destination, or along the lane within the last 90 days.

This information can help to mitigate fraud and ensure accurate capacity claims during the carrier vetting process.

Authentication

Include the following headers in your requests:

  • Access-Token: The access token obtained from the "Create Acess Token" endpoint.

  • x-api-key: The API key provided by Genlogs. This header must be included in the request.

Endpoint

  • URL: https://api.genlogs.io/visual_sightings/verify

  • Method: GET

Query Parameters

  • usdot (string, Required): usdot of the detected carrier.

  • origin_city (string, Required): Name of the city of the starting location.

  • origin_state (string, Required): Name of the state of the starting location.

  • destination_city (string, Optional): Name of the city of the destination location.

  • destination_state (string, Optional): Name of the state of the destination location.

Response

  • 200 OK: A JSON object containing the message verified true or false

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

  • 401 Unauthorized: If the authentication credentials (email and password) are missing or incorrect.

  • 403 Forbidden: Access to the requested resource is forbidden.

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

Response Body:

  • verified (boolean): true or false

Request Example:

curl -X GET 'https://api.genlogs.io/visual_sightings/verify?usdot=2523551&origin_state=Georgia&origin_city=Tucker' \
-H 'Access-Token: {access_token}' \
-H 'x-api-key: {your_api_key}' \
-i

PreviousCarrier Observation

Last updated