| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| SyncName | query | string | No | |
| ClientId | query | Guid | No | |
| Scopes | query | List<ScopeRequest> | No | |
| GzipResponse | query | bool | No | |
| Id | query | Guid | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Name | form | string | No | |
| ClientBlob | form | byte[] | No | |
| Parameters | form | List<SyncParamValue> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Name | form | string | No | |
| Value | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| FilePath | form | string | 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 /json/reply/MqGetSyncChanges HTTP/1.1
Host: apex.nikoratrade.ge
Accept: application/json
Content-Type: application/json
Content-Length: length
{"SyncName":"String","ClientId":"00000000000000000000000000000000","Scopes":[{"Name":"String","ClientBlob":"AA==","Parameters":[{"Name":"String","Value":"String"}]}],"GzipResponse":false,"Id":"00000000000000000000000000000000"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"FilePath":"String"}