Making a SCIM API Request¶
To use the Snowflake SCIM API, the identity provider’s SCIM client must be verified during each API request. Snowflake assigns the identity provider SCIM client a role with sufficient privileges to make the API requests. Currently, Snowflake supports and wraps those privileges into a Bearer Token, which must be passed in the authorization header of each API request.
Headers Parameters¶
Each SCIM API request must include the following parameters in the request header.
Parameter |
Type |
Value |
---|---|---|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
Sending a SCIM API Request to Snowflake¶
Users can access representative examples of the Snowflake SCIM API here.
You can integrate the Postman collection into the local Postman application on your machine by clicking Run in Postman and then make an API request.
Using Postman as a representative example, follow these steps to send a SCIM API request to Snowflake.
Define the method and enter the request URL.
The request URL consists of the Snowflake account URL appended with
/scim/v2/
. For a list of supported formats for the Snowflake account URL, see Connecting with a URL. So the request URL takes the following form:<snowflake_account_url>/scim/v2/
Enter and verify the parameters in the Params tab to ensure the authorization header contains the correct key-value pairs.
Ensure the Body tab contains any necessary JSON string.
Click Send.