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

TravelPerk Cost Centers API

Cost center management and user assignment.

TravelPerk Cost Centers API is one of 5 APIs that TravelPerk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against 2 base URLs: https://api.travelperk.com, https://api.sandbox-travelperk.com.

6 operations 4 paths 3 schemas 2 GET2 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.travelperk.com
Authentication
HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

TravelPerk Cost Centers API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (token) (bearerAuth). An API key is passed in the header as Authorization (apiKeyAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 access token obtained via the Authorization Code grant, passed as Authorization: Bearer .
  • apiKeyAuth — Personal API key passed as Authorization: ApiKey for customer (non-partner) integrations.

Paths & Operations 6

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

Cost Centers 6

Cost center management and user assignment.

GET
/cost_centers
List all cost centers
listCostCenters 2 params → 200
POST
/cost_centers
Create cost center
createCostCenter body → 201
PATCH
/cost_centers/bulk_update
Bulk update cost centers
bulkUpdateCostCenters body → 200
GET
/cost_centers/{id}
Get cost center
getCostCenter 1 param → 200
PATCH
/cost_centers/{id}
Update cost center
updateCostCenter 1 param body → 200
PUT
/cost_centers/{id}/users
Set users to a cost center
setCostCenterUsers 1 param body → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are CostCenter (7 properties), CostCenterInput (5 properties), CostCenterList (3 properties). Each schema is shown below with its type and property counts.

CostCenter
object
7 properties
CostCenterInput
object
5 properties 1 required
CostCenterList
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

travelperk-cost-centers-api-openapi.yml Raw ↑

Other APIs TravelPerk publishes across the network.

TravelPerk Invoices API
TravelPerk Members API
TravelPerk Trips API
TravelPerk Webhooks API
Where this information came from

This is an independent, third-party profile of TravelPerk Cost Centers 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.