Pushed authorization request (PAR) is a secure way to initiate the authorization flow. All parameters are sent in the body of the request (see OAuth 2.0 Pushed Authorization Requests RFC).
URI to redirect to upon completion of the authentication flow. This is the server GET endpoint used to call the token endpoint, and should accept code as a query parameter. This URI must also be configured as an allowed redirect URI in the Admin Portal
Scope of the requested access. Used to request specific user details like email. Must include openid and can include additional values (space delimited). offline_access scope allows refreshing access tokens.
Space-delimited, case-sensitive list of string values that specifies whether the Authorization Server prompts the end-user for reauthentication and consent.
A random value that is included in the authentication request from the client (e.g. browser) to mitigate replay attacks. It will be added to the id_token and the backend service should only accept id_tokens that include the same nonce value as the one included in the original request.
An opaque string that is used to maintain state between the request and the callback. It will be added to the redirect URI as a query parameter, which should be validated by your server to protect against cross-site request forgery (CSRF) attacks
Resource URI the authentication request is attempting to access, which is reflected in the audience (aud claim) of the access token. This must be configured as resource for the application.
A stringified object used to request additional claims in the ID token, such as roles, permissions, and other user profile data. The structure is per the OIDC Standard. For supported claims and how to request custom claims, see the ID Token Reference. Note: You should stringify the value.
Requested ACR values, specified as a space-separated string. The acr claim of the resulting ID token will indicate which requirements were satisfied.
Indicates if a new user should be created if one doesn't already exist (or associated with the app if the user isn't already). Public sign up must be enabled for this application.
Custom message to present on the consent screens for WebAuthn login, which provides authentication context details.
Preferred languages for the user interface for WebAuthn login, specified as a space-separated list of language tag values [RFC5646], ordered by preference.
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/oidc/request
- US production environmenthttps://api.transmitsecurity.io/cis/oidc/request
- EU production environmenthttps://api.eu.transmitsecurity.io/cis/oidc/request
- CA production environmenthttps://api.ca.transmitsecurity.io/cis/oidc/request
- AU production environmenthttps://api.au.transmitsecurity.io/cis/oidc/request
- JP production environmenthttps://api.gasne1-ts01.transmitsecurity.io/cis/oidc/request
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/oidc/request \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d client_id=string \
-d client_secret=string \
-d redirect_uri=string \
-d response_type=code \
-d scope=openid \
-d prompt=none \
-d nonce=string \
-d state=string \
-d resource=string \
-d claims=string \
-d acr_values=mfa \
-d createNewUser=false \
-d login_hint=string \
-d 'custom_message=Welcome to Acme' \
-d ui_locales=string \
-d org_id=string \
-d code_challenge=string \
-d code_challenge_method=stringThe request has been accepted
{ "request_uri": "string", "expires_in": 60 }