| POST,OPTIONS | /share/{Token}/otp |
|---|
"use strict";
export class ShareLandingResponse {
/** @param {{ResponseStatus?:ResponseStatus,Status?:string,RequireOtp?:boolean,OtpChannel?:string,OtpSent?:boolean,DocumentName?:string,CanView?:boolean,Message?:string}} [init] */
constructor(init) { Object.assign(this, init) }
/** @type {ResponseStatus} */
ResponseStatus;
/** @type {string} */
Status;
/** @type {boolean} */
RequireOtp;
/** @type {string} */
OtpChannel;
/** @type {boolean} */
OtpSent;
/** @type {string} */
DocumentName;
/** @type {boolean} */
CanView;
/** @type {string} */
Message;
}
export class ShareOtpRequest {
/** @param {{Token?:string}} [init] */
constructor(init) { Object.assign(this, init) }
/** @type {string} */
Token;
}
JavaScript ShareOtpRequest DTOs
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 /share/{Token}/otp HTTP/1.1
Host: api.dev.dynamics.trendsic.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
Token: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
ResponseStatus:
{
ErrorCode: String,
Message: String,
StackTrace: String,
Errors:
[
{
ErrorCode: String,
FieldName: String,
Message: String,
Meta:
{
String: String
}
}
],
Meta:
{
String: String
}
},
Status: String,
RequireOtp: False,
OtpChannel: String,
OtpSent: False,
DocumentName: String,
CanView: False,
Message: String
}