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

Bridgit Persons API

The Persons API from Bridgit — 11 operation(s) for persons.

Bridgit Persons API is one of 40 APIs that Bridgit publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Persons. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

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

14 operations 11 paths 14 schemas 1 DELETE7 GET1 PATCH4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://bench.gobridgit.com/rp/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Bridgit Persons 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 14

Across 11 paths, the API surfaces 14 operations — 1 DELETE, 7 GET, 1 PATCH, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Persons 14
GET
/rp/api/v1/accounts/{accountId}/Persons
Gets all people in the given account.
Persons_Query 8 params → 200400401403
POST
/rp/api/v1/accounts/{accountId}/Persons
Add a person to the given account
Persons_Post 1 param body → 200400401403409422
GET
/rp/api/v1/accounts/{accountId}/Persons/availabilities
Gets the number of days until each person in this account is available and their availability ranges for the duration
Persons_QueryNextAvailables 7 params → 200400401403
PUT
/rp/api/v1/accounts/{accountId}/Persons/{id}/externalId
Updates a person to set and externalId that can be referenced by external systems.
Persons_SetExternalId 2 params body → 204400401403
POST
/rp/api/v1/accounts/{accountId}/Persons/_filter
Gets all people in the given account filter by person ids.
Persons_QueryFilter 1 param body → 200400401403
PATCH
/rp/api/v1/accounts/{accountId}/Persons/{id}
Update a person in the given account. Each of the fields in the request body is optional - only fields that are present in the request will be updated.
Persons_Update 2 params body → 200400401403409422
GET
/rp/api/v1/accounts/{accountId}/Persons/{id}
Gets details for the given person
Persons_Get 3 params → 200400401403
DELETE
/rp/api/v1/accounts/{accountId}/Persons/{id}
Deactivate a person
Persons_Delete 2 params → 204400401403
POST
/rp/api/v1/accounts/{accountId}/Persons/{id}/deactivate
Deactivate a person with optional deactivation details (reason, notes, would rehire).
Persons_Deactivate 2 params body → 204400401403
GET
/rp/api/v1/accounts/{accountId}/Persons/{id}/allocations
Get all allocations for the given person within the selected date range.
Persons_GetAllocations 8 params → 200400401403
GET
/rp/api/v1/accounts/{accountId}/Persons/{id}/projects
Get all projects that this person is allocated to, including past, present, and future allocations.
Persons_GetProjects 4 params → 200400401403
GET
/rp/api/v1/accounts/{accountId}/Persons/current-projects
Get all projects that any person in the given account has an active allocation for. That is, each allocation's start date is ≦ now and the end date is ≧ now.
Persons_GetCurrentProjects 5 params → 200400401403
GET
/rp/api/v1/accounts/{accountId}/Persons/current-projects-hourly
Get all projects that any person in the given account has an active allocation for. That is, each allocation's start date is ≦ now and the end date is ≧ now.
Persons_GetCurrentProjectsHourly 4 params → 200400401403
POST
/rp/api/v1/accounts/{accountId}/Persons/{id}/restore
Reactivate a person
Persons_Restore 2 params → 204400401403422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are PersonResponse (20 properties), NewPersonRequest (11 properties), PersonAllocationResponse (11 properties), Project (7 properties). Each schema is shown below with its type and property counts.

NewPersonRequest
object
11 properties
PersonProjectList
object
2 properties
Availability
object
4 properties
EmploymentDatesResponse
object
2 properties
Project
object
7 properties
PersonDeactivateRequest
object
4 properties
PersonResponse
object
20 properties
PersonNextAvailable
object
4 properties
PersonFilterPredicates
object
5 properties
PersonProjectResponse
object
6 properties
PersonFilterPredicatesFilter
object
3 properties
FieldValuesPair
object
2 properties
ExternalIdRequest
object
1 property
PersonAllocationResponse
object
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bridgit-persons-api-openapi.yml Raw ↑

Other APIs Bridgit publishes across the network.

Bridgit AccountActivities API
Bridgit AccountCertifications API
Bridgit AccountGroupings API
Bridgit AccountInvitations API
Bridgit Accounts API
Bridgit AccountUsers API
Bridgit Allocations API
Bridgit ExperienceFields API
Bridgit ExperienceFieldValues API
Bridgit External API
Bridgit HourlyAllocations API
Bridgit HourlyRoleNames API
Where this information came from

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