| All Verbs | /session-to-token |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PreserveSession | query | bool | No | |
| Meta | query | Dictionary<string, string> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Meta | form | Dictionary<string, string> | No | |
| AccessToken | form | string | No | |
| RefreshToken | form | string | No | |
| ResponseStatus | form | ResponseStatus | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST //session-to-token HTTP/1.1
Host: api.lsu-staging.abodehms.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
preserveSession: False,
meta:
{
String: String
}
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
meta:
{
String: String
},
accessToken: String,
refreshToken: String,
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}