| PUT | /v1/account |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| EmailAddress | body | string | No | |
| FullName | body | string | No | |
| ProfileImageId | body | string | No | |
| SignatureImageId | body | string | No | |
| SignatureFont | body | string | No | |
| SignatureAppearance | body | SignatureAppearance | No |
| Name | Value | |
|---|---|---|
| None | none | |
| Text | text | |
| Upload | upload |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Data | form | PutAccountResponseData | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| OneTimeToken | 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.
PUT /v1/account HTTP/1.1
Host: api.booklinker.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
newEmail: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
success: False,
oneTimeToken: String,
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
},
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}