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 auth API

Access-token creation and refresh

GenLogs auth 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 Authentication. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, an AsyncAPI specification, and 1 JSON Schema.

This API exposes 2 operations across 2 paths, and defines 8 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.

2 operations 2 paths 8 schemas 2 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 auth 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 2

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

auth 2

Access-token creation and refresh

POST
/auth/token
Create access and refresh tokens
createAccessToken 2 params → 200401422
POST
/auth/token/refresh
Get the AccessToken And Refresh Token
refresh_token_get 3 params → 200422

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are AuthSchema (5 properties), AuthenticationResponse (4 properties), ValidationError (3 properties), AccessTokenSchema (2 properties). Each schema is shown below with its type and property counts.

HTTPError
object
1 property
ValidationError
object
3 properties 3 required
AuthenticationResponse
object
4 properties 4 required
HTTPValidationError
object
1 property
RefreshTokenSchema
object
2 properties 2 required
TokenSchema
object
2 properties 2 required
AccessTokenSchema
object
2 properties 2 required
AuthSchema
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

genlogs-auth-api-openapi.yml Raw ↑

Other APIs GenLogs publishes across the network.

GenLogs Alerts API
GenLogs Carrier 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 auth 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.