Exploring the Perk SCIM API schemas

Before you build against Perk's SCIM API, it helps to ask the API what it supports rather than guessing.

The Perk SCIM API includes three read-only discovery endpoints for exactly this — they tell you which operations are available, what resource types exist, and what attributes each schema holds. Querying them keeps your integration in step with Perk without hard-coding assumptions.

All three are GET endpoints under the base URL https://app.perk.com/api/v2/scim, and they take the same API key as every other SCIM call.

📘
Note
You can use https://app.perk.com/api/v2/scim or https://app.travelperk.com/api/v2/scim. Both are currently accepted; however, we recommend you use the perk domain. Some responses may still return the travelperk domain.

What each endpoint tells you

Endpoint	What you get back	Use it when you want to
`GET /ServiceProviderConfig`	Perk's SCIM configuration, including which operations the API supports.	Check what the API can do before you rely on a feature (for example, whether `PATCH` is supported).
`GET /ResourceTypes`	The resource types the SCIM API exposes.	Discover which kinds of resources you can work with.
`GET /Schemas`	The core schema plus Perk's attribute extensions.	Inspect the exact attributes — including the Enterprise, travel, and expense extensions — before you build a payload.

Try a discovery call

To see your account's configuration, call /ServiceProviderConfig with your API key:

curl \
  --url "https://app.perk.com/api/v2/scim/ServiceProviderConfig" \
  --header "Authorization: apikey <your_api_key>"

Swap in /ResourceTypes or /Schemas to explore the others. They all work the same way — no request body, just your key.

Next steps

User model reference — every user attribute and extension, if you'd rather jump straight into the Users API.
Using the Perk SCIM API — learn about what SCIM is, how Perk implements it, and the base URL.