Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
RegistrationProfileID | query | Guid? | No | |
Values | query | List<RegistrationValue> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
PidTag | form | string | No | |
ItemId | form | string | No | |
EwsUrl | form | string | No | |
Token | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Key | form | Guid | No | |
Value | form | string | No | |
ShadowValue | form | string | 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 /jsv/reply/SaveDraftMail HTTP/1.1
Host: doapigw.baasbv.nl
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
RegistrationProfileID: 00000000-0000-0000-0000-000000000000,
Values:
[
{
Value: String,
ShadowValue: String
}
],
PidTag: String,
ItemId: String,
EwsUrl: String,
Token: String
}
HTTP/1.1 200 OK Content-Type: text/jsv Content-Length: length False