Bridgit PersonHistoricalExperiences API
The PersonHistoricalExperiences API from Bridgit — 2 operation(s) for personhistoricalexperiences.
Bridgit PersonHistoricalExperiences API is one of 40 APIs that Bridgit publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include PersonHistoricalExperiences. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.
This API exposes 6 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against a single base URL, https://bench.gobridgit.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Bridgit PersonHistoricalExperiences API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (Bearer).
By default, every request must be authenticated, though some operations may also be called without credentials.
Bearer— Standard Authorization header using the Bearer scheme
Paths & Operations 6
Across 2 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are HistoricalExperienceFullEntry (14 properties), HistoricalExperienceRequest (12 properties), HistoricalExperienceEntryWithExperienceFields (8 properties), HistoricalExperienceUpdateRequest (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Bridgit 12
Other APIs Bridgit publishes across the network.
This is an independent, third-party profile of Bridgit PersonHistoricalExperiences 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.