A log of a single request to change catalog data for an item that could have come from a file or from an API and the request may have succeeded or failed.
- isodate fields use one of these ISO 8601 formats: 2014-01-01T10:30:00.000+01:00, 2014-01-01T10:30:00.000+0100, 2014-01-01T10:30:00.000Z
- Dsco reserves the right to add new attributes at any time so Partners should ensure their validators won't break should this happen
Attributes
| Name | Req | Type | Description |
|---|---|---|---|
| payload | ✓ |
ItemCatalog |
The catalog object containing the change that was requested |
| dateProcessed | ✓ | isodate | The date the request was actually processed |
| status | ✓ | enum | The status of the change, one of...
|
| requestMethod | ✓ | enum | How the request was made, one of...
|
| requestId | string | The ID of the API request that included the request to make this change if done via an API. | |
| processId | string | The ID of the file process that included the request to make this change id done via file process | |
| results | array of object - code: string - severity: enum info, warn, error - description: string |
The list of results that apply to the payload where each entry in the list has a code identifying what happened where a severity of error means the change was not made and info and warn means it was made | |
| messages | ApiResponseMessage[] | A list of messages about what happened |
Example
{
"logs": [ItemCatalogChangeLogObj, ItemCatalogChangeLogObj, ...]
}
Comments
Please sign in to leave a comment.