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

TrueBiz History API

The History API from TrueBiz — 1 operation(s) for history.

TrueBiz History API is one of 11 APIs that TrueBiz publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include History. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

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

Requests are made against a single base URL, https://ae.truebiz.io.

1 operations 1 paths 9 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://ae.truebiz.io
Authentication
API Key, HTTP Bearer, API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 4

TrueBiz History API declares 4 security schemes for authenticating requests. An API key is passed in the header as X-API-KEY (AsyncApiKeyAuth). It accepts HTTP bearer tokens (AsyncPropelAuthBearer). An API key is passed in the header as X-API-KEY (ApiKeyAuth). It accepts HTTP bearer tokens (PropelAuthBearer).

Paths & Operations 1

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

History 1
GET
/api/v1/history/combined_lookups
Get Combined Lookups History
core_api_company_lookup_get_combined_lookups_history 7 params → 200400401404422429500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are CombinedMetaLookup (8 properties), PagedCombinedMetaLookup (4 properties), InvalidRequest (2 properties), InvalidInputParameter (2 properties). Each schema is shown below with its type and property counts.

TooManyRequests
object
1 property 1 required
InvalidInputParameter
object
2 properties 1 required
BadRequest
object
1 property 1 required
NotFound
object
1 property 1 required
CombinedMetaLookup
object
8 properties 4 required
PagedCombinedMetaLookup
object
4 properties 4 required
InternalServerError
object
1 property 1 required
InvalidRequest
object
2 properties 1 required
Unauthorized
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

truebiz-history-api-openapi.yml Raw ↑

Other APIs TrueBiz publishes across the network.

TrueBiz Async Web Presence Review API
TrueBiz Fraud Searches API
TrueBiz Industry Discovery API
TrueBiz Industry Discovery History API
TrueBiz Monitoring Alerts API
TrueBiz Monitoring Domains API
TrueBiz Web Presence Review API
TrueBiz Web Presence Review Blocklist API
TrueBiz Web Presence Review History API
TrueBiz Website Status API
Where this information came from

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