How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

GenLogs Carrier API

The Carrier API from GenLogs — 3 operation(s) for carrier.

GenLogs Carrier API is one of 10 APIs that GenLogs publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Carrier. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, an AsyncAPI specification, and 1 JSON Schema.

This API exposes 3 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api.genlogs.io.

3 operations 3 paths 7 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.genlogs.io
Authentication
API Key, API Key
Contact
Resource Areas
1

Authentication & Security 2

GenLogs Carrier API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). An API key is passed in the header as Access-Token (AccessToken). By default, every request must be authenticated.

  • ApiKeyAuth — API key provided by GenLogs. Required on every request.
  • AccessToken — Short-lived access token obtained from POST /auth/token (or refreshed via /auth/token/refresh).

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Carrier 3
GET
/carrier/recommendations
Get carrier recommendations based on location
getCarrierRecommendations 21 params → 200
POST
/carrier/contacts
Get contacts for carriers
searchCarrierContacts → 200401403500
GET
/carrier/profile
Get carrier profile details
getCarrierProfileDetail 4 params → 200400401403500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are CarrierRecommendation (30 properties), FmcsaDetail (23 properties), Sighting (5 properties), CarrierRealTimeLocs (4 properties). Each schema is shown below with its type and property counts.

EquipmentPairings
object
2 properties
CarrierResponse
object
2 properties 2 required
CarrierRecommendation
object
30 properties 24 required
Sighting
object
A single sighting record for a carrier location/date.
5 properties
ErrorResponse
object
2 properties 2 required
CarrierRealTimeLocs
object
4 properties 2 required
FmcsaDetail
object
23 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

genlogs-carrier-api-openapi.yml Raw ↑

Other APIs GenLogs publishes across the network.

GenLogs Alerts API
GenLogs auth API
GenLogs carrier-vetting API
GenLogs Compliance Rules API
GenLogs Facilities API
GenLogs Mismatch alerts API
GenLogs Onboarded Carriers API
GenLogs Shipper API
GenLogs Webhook Alerts API
Where this information came from

This is an independent, third-party profile of GenLogs Carrier API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.