TruckerTechTruckerTech
Request access

Developer Lab · Changelog

Changelog

Every published version, what changed, and how to move. Published versions never change.

The changelog as an Atom feed.

connectors 1.1.0

The integration API: the client-credentials token endpoint, whoami, Core reads and Core document metadata.

  • POST /oauth/token issues an access token to an integration client that signs a client assertion (private_key_jwt).
  • GET /v1/whoami returns the organisation, environment and scopes of the calling integration client.
  • GET /v1/cores lists the Cores the integration client’s organisation created or takes part in, with the facts that are shared between participants.
  • GET /v1/cores/{coreId} returns one such Core, or 404 when it is not one of them.
  • GET /v1/cores/{coreId}/documents lists the documents of one such Core as metadata only: id, class, file name, content type, size, recorded time and visibility. Never the bytes, the digest or the storage location.
  • The new scope ops.cores:read gates the Core reads and the document list; a client without it receives 403 insufficient_scope.

OpenAPI · AsyncAPI · components canon/2 envelope/1 manifest/1 port/1 tt-nexus-remote/1

connectors 1.0.0

The first published version of the TruckerTech Nexus connector contract.

  • Ingress: signed Partner event delivery, one event per request, with its answers and limits.
  • The remote connector protocol, as the request TruckerTech Nexus sends to a connector and the signed reply it expects.
  • The canonical Capability Socket schemas, the attribution envelope, the status and fault taxonomies, and the capability manifest.

OpenAPI · AsyncAPI · components canon/2 envelope/1 manifest/1 port/1 tt-nexus-remote/1