Exchange a signed external principal for a platform session credential

POST/v1/internal/principal-sessions

Internal platform-BFF endpoint. The caller presents a short-lived, audience-bound principal assertion. The resulting API credential is time-bounded and must never be exposed to browser JavaScript.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
None.
Query parameters
None.

Body schema

Content type: application/json · Optional

FieldTypeRequiredDescription
ttlSecondsintegerNo—

What the API returns

Each response code below includes the documented payload shape for the ACP API.

201Principal and workload credential resolvedapplication/json
FieldTypeRequiredDescription
profileobjectYes—
profile.userIdstringYesUser ID.
profile.emailstringNo—
profile.displayNamestringNo—
profile.photoURLstringNo—
profile.emailVerifiedbooleanNo—
profile.identityLinkIdstringNo—
profile.identityProvideroidc | firebaseYes—
profile.identityIssuerstringYes—
subscriptionobjectYes—
subscription.tierstringNo—
subscription.statusstringNoCurrent lifecycle status.
credentialobjectYes—
credential.idstringYesUnique identifier.
credential.keystringYes—
credential.expiresAtstringYes—
401Principal assertion required
None.
403Principal assertion invalid or expired
None.
Exchange a signed external principal for a platform session credential
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow