Connect Sessions
Authenticate Connect Session
POST
Authorizations
Basic authentication header of the form Basic <encoded-value>
, where <encoded-value>
is the base64-encoded string username:password
.
Body
application/json
The parameters to authenticate
The token to authenticate with
Response
201
application/json
The details of the authenticated connect session.
Available options:
ats
, hris
, hris-legacy
, crm
, iam
, marketing
, lms
, stackone
, documents
, ticketing
, screening
, messaging
Example:
[
"ats",
"hris",
"hrisLegacy",
"crm",
"iam",
"marketing",
"lms",
"stackOne",
"documents",
"ticketing",
"screening",
"messaging"
]
Arbitrary set of key and values defined during the session token creation. This can be used to tag an account (eg. based on their pricing plan)
External trigger token to be used to trigger actions on the account
Example:
"f0bc3d88-2178-5423-8c81-b81d6c9da824"
Was this page helpful?