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

Tollbit Reporting API

The Reporting API from Tollbit — 1 operation(s) for reporting.

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

Tagged areas include Reporting. The published artifact set on APIs.io includes an OpenAPI specification and an AsyncAPI specification.

This API exposes 1 operation across 1 path, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version v2.

Requests are made against a single base URL, https://gateway.tollbit.com.

1 operations 1 paths 8 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://gateway.tollbit.com
Authentication
API Key, API Key, API Key, HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 4

Tollbit Reporting API declares 4 security schemes for authenticating requests. An API key is passed in the header as TollbitKey (ApiKeyAuth). An API key is passed in the header as Tollbit-Token (ApiKeyAuth_). An API key is passed in the header as TollbitKey (TollbitKey). It accepts HTTP bearer tokens (SubdomainAccessToken).

  • TollbitKey — Your API key which can be found in the access page of the dashboard.
  • SubdomainAccessToken — To access content on a TollBit subdomain, you will need an access token. This token is a JWT that is signed by TollBit and includes information about the subdo…

Paths & Operations 1

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

Reporting 1
POST
/dev/v2/transactions/selfReport
ReportingService_reportContentUsage body → 200400401403404500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are SelfReportUsage (6 properties), ProblemJSON (5 properties), SelfReportUsageReceipt (5 properties), RateLicenseResponse (4 properties). Each schema is shown below with its type and property counts.

SelfReportContentUsageResponse
object
1 property 1 required
ProblemJSON
object
5 properties 3 required
SelfReportContentUsageRequest
object
2 properties 2 required
SelfReportLicensePermission
object
1 property 1 required
RateLicensePermission
object
1 property 1 required
SelfReportUsage
object
6 properties 4 required
RateLicenseResponse
object
4 properties 4 required
SelfReportUsageReceipt
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tollbit-reporting-api-openapi.yml Raw ↑

Other APIs Tollbit publishes across the network.

Tollbit Auth Tokens API
Tollbit Dev API
Tollbit Search API
Tollbit Tollbit Content API
Tollbit Tollbit Subdomain API
Where this information came from

This is an independent, third-party profile of Tollbit Reporting 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.