Authorize
GET {{baseUrl}}/vault/authorize/:service_id/:application_id?state=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJjb25zdW1lcl9pZCI6InRlc3RfdXNlcl9pZCIsInVuaWZpZWRfYXBpIjoiZGVmYXVsdCIsInNlcnZpY2VfaWQiOiJ0ZWFtbGVhZGVyIiwiYXBwbGljYXRpb25faWQiOiIxMTExIiwiaWF0IjoxNjIyMTI2Nzg3fQ.97_pn1UAXc7mctXBdr15czUNO1jjdQ9sJUOIE_Myzbk&redirect_uri=http://example.com/integrations&scope=openid%20leads:write%20profile:read
In most cases the authorize link is provided in the /connections endpoint. Normally you don't need to manually generate these links.
Use this endpoint to authenticate a user with a connector. It will return a 301 redirect to the downstream connector endpoints.
Auth links will have a state parameter included to verify the validity of the request. This is the url your users will use to activate OAuth supported integration providers.
Vault handles the complete Authorization Code Grant Type Flow for you and will redirect you to the dynamic redirect uri you have appended to the url in case this is missing the default redirect uri you have configured for your Unify application.
Request Params
| Key | Datatype | Required | Description |
|---|---|---|---|
state | string | (Required) An opaque value the applications adds to the initial request that the authorization server includes when redirecting the back to the application. This value must be used by the application to prevent CSRF attacks. | |
redirect_uri | string | (Required) URL to redirect back to after authorization. When left empty the default configured redirect uri will be used. | |
scope | string | One or more OAuth scopes to request from the connector. OAuth scopes control the set of resources and operations that are allowed after authorization. Refer to the connector's documentation for the available scopes. | |
cursor | null | ||
resource_id | null |
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
Accept | string |