| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| TranslateKeys | query | List<string> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Translations | form | List<Translation> | No | |
| PreferredLanguage | form | string | No | |
| PreferredLanguageShort | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Key | form | string | No | |
| NL | form | string | No | |
| EN | form | string | No | |
| DE | form | string | No | |
| FR | form | string | No | |
| C1 | form | string | No | |
| C2 | form | string | No | |
| C3 | form | string | No | |
| C4 | form | string | No | |
| C5 | form | string | No | |
| C6 | 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/GetTranslations HTTP/1.1
Host: doapigw.baasbv.nl
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
TranslateKeys:
[
String
]
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
Translations:
[
{
Key: String,
NL: String,
EN: String,
DE: String,
FR: String,
C1: String,
C2: String,
C3: String,
C4: String,
C5: String,
C6: String
}
],
PreferredLanguage: String,
PreferredLanguageShort: String
}