Inbound Subjects
Every inbound subject with its submit and delete endpoints, task type, extended data support and page.
Every kind of data you can load into GAINS has its own inbound endpoint. The table below lists each subject with its submit and delete endpoints, the TaskType its tasks carry, and whether it accepts ExtendedData. The subject pages explain what each subject represents in GAINS, what identifies a record, and how records nest. The API Reference lists every field, which fields are required, and the values each accepts.
Subjects
TaskType is given as load / delete. Use these values to filter GET /tasks and TaskStatusUpdate webhooks.
ExtendedData is accepted only where your GAINS representative has configured attributes; at which level of a nested record is described in Sending Extended Data. Subjects with no delete endpoint cannot be removed through the API.
Rules common to every subject
- Field names, value types, date formats and the
400for an unknown field are described in Data Formats & Conventions. - How a batch is accepted is described in Loading Data, and how it is tracked in Integration Tasks.
- Which subjects to load first is described in Initial Load & Load Order.
Related
- Master Data: SKUs, locations, SKU-locations, customers and vendors.
- Sourcing & Product Structure: vendors per item, constraints, kits, replacements and price breaks.
- Demand Planning: sales history, events, forecasts and calendars.
- Inventory & Supply: stock on hand, open orders and usage.
- Deleting Data: how deletes work and the SKU-location review.
- Integration Tasks: task statuses and following a task.
- Sending Extended Data: sending your own attributes.
Updated 8 days ago