| 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 .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
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: recaudoenee.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"PreserveSession":false,"Meta":{"String":"String"}}
HTTP/1.1 200 OK
Content-Type: application/json
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"}}}