Skip to main content

Organization API Overview

The Organization API is the org-scoped external surface on api.propper.ai. It resolves organization-level state from your access token, so the organization is never passed in the path.

Endpoints

  • GET /v1/org: read the calling organization's profile (name, data residency, timestamps). Requires the org:read scope.
  • GET /v1/org/members: list the calling organization's members with their role and status, paginated. Requires the users:read scope.
  • GET /v1/org/entitlements: resolve the calling organization's derived entitlement verdict. The response projection is selected with the view query parameter. Platform-only (see below).

Authentication

OAuth 2.0 Bearer token; the organization is resolved from the token. Customer integrations request the org:read scope (organization profile) and the users:read scope (membership); both can be assigned to client applications you create and manage in your organization settings. Individual endpoints may carry stricter, platform-only scope requirements, so check each endpoint's scope before integrating: the entitlement verdict projection, view=salesforce below, is platform-only and is NOT reachable with org:read (it requires the platform-reserved org:entitlements:read scope, which is not customer-requestable).

Entitlement verdict projections

The view query parameter selects the projection of the entitlement verdict.

view=salesforce

GET /v1/org/entitlements?view=salesforce returns the verdict shaped for the Salesforce connector. This projection is platform-only: the path is callable exclusively by Propper-generated Salesforce client applications, gated on the platform-reserved org:entitlements:read scope (with entitlements:read as its legacy alias). Neither is a customer-requestable scope, so customer-created applications cannot call it.