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

Emburse person-controller-v4 API

Person Web Services

Emburse person-controller-v4 API is one of 48 APIs that Emburse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include person-controller-v4. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 16 operations across 9 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, http://hades.pool.

16 operations 9 paths 5 schemas 2 DELETE6 GET1 PATCH6 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.emburse.com/v1/
Resource Areas
1

Paths & Operations 16

Across 9 paths, the API surfaces 16 operations — 2 DELETE, 6 GET, 1 PATCH, 6 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

person-controller-v4 16

Person Web Services

GET
/v4/persons/{personUniqueId}/person-entities/{person-entity-id}
Get Person Relationship Attributes by Identifier
getPersonEntityById 4 params → 200
PUT
/v4/persons/{personUniqueId}/person-entities/{person-entity-id}
Modify Person Relationship Attributes by Identifier
modifyPersonEntityById 4 params body → 200
DELETE
/v4/persons/{personUniqueId}/person-entities/{person-entity-id}
Delete Person Relationship Attributes by Identifier
deletePersonEntityById 4 params → 200
GET
/v4/persons
Get Persons
getPersons 10 params → 200
POST
/v4/persons
Create a Person
createPerson 2 params body → 200
POST
/v4/persons/{toPersonUniqueId}/assists/{fromPersonUniqueId}
Add Person Delegate
addPersonDelegate 4 params → 200
DELETE
/v4/persons/{toPersonUniqueId}/assists/{fromPersonUniqueId}
Delete Person Delegate
deletePersonDelegate 4 params → 200
GET
/v4/persons/{personUniqueId}/udas
Fetch Person's User Defined Attributes
getPersonUdas 3 params → 200
POST
/v4/persons/{personUniqueId}/udas
Creates Person's User Defined Attribute
createPersonUda 3 params body → 200
GET
/v4/persons/{personUniqueId}/person-entities
Get Person Relationship Attributes
getPersonEntities 3 params → 200
POST
/v4/persons/{personUniqueId}/person-entities
Create a Person-to-Entity association
addEntityToPerson 3 params body → 200
POST
/v4/persons/reprocess-depersonalization
Reprocess depersonalization for a person
reprocessDepersonalization 2 params body → 200
POST
/v4/persons/batch
Create/update persons
upsertPersons 2 params body → 200
GET
/v4/persons/{personUniqueId}
Get Person
getPersonByUniqueId 3 params → 200
PATCH
/v4/persons/{personUniqueId}
PATCH a Person
patch 3 params body → 200
GET
/v4/persons/search
Search for Persons
searchPersons 5 params → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are PersonView (29 properties), PersonEntityView (5 properties), Response (3 properties), AlternateCurrency (2 properties). Each schema is shown below with its type and property counts.

Response
object
3 properties
PersonUdaView
object
2 properties 2 required
PersonEntityView
object
5 properties 3 required
AlternateCurrency
object
2 properties 2 required
PersonView
object
29 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emburse-person-controller-v4-api-openapi.yml Raw ↑

Other APIs Emburse publishes across the network.

Emburse Professional API
Emburse Spend API
Emburse Accounts API
Emburse allocation-api-controller-v-1 API
Emburse allocation-api-controller-v-2 API
Emburse allocation-api-controller-v-3 API
Emburse Allowances API
Emburse Cards API
Emburse Categories API
Emburse Company API
Emburse Departments API
Emburse Entity Type API
Where this information came from

This is an independent, third-party profile of Emburse person-controller-v4 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.