| POST,OPTIONS | /v1/records/entry |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Name | body | string | No | |
| SeriesId | body | int? | No | |
| Classification | body | string | No | |
| Format | body | string | No | |
| TriggerDate | body | string | No | |
| MetaJson | body | string | No | |
| FilesJson | body | string | No | |
| Warehouse | body | string | No | |
| Aisle | body | string | No | |
| Shelf | body | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Ok | form | bool | No | |
| Id | form | int | No | |
| Key | form | string | No | |
| Matches | form | List<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 /v1/records/entry HTTP/1.1
Host: api.dev.dynamics.trendsic.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"Name":"String","SeriesId":0,"Classification":"String","Format":"String","TriggerDate":"String","MetaJson":"String","FilesJson":"String","Warehouse":"String","Aisle":"String","Shelf":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}},"Ok":false,"Id":0,"Key":"String","Matches":["String"]}