POST /api/v2/product/set
Creates a new product or updates an existing one, and assigns it to the specified event.
Authentication
Authorization: Bearer <your_api_key>
Endpoint
POST /api/v2/product/set
Content-Type: multipart/form-data
Create vs Update
-
Create: Omit
id.event_id,exhibitor_id,name, andcategoriesare required -
Update: Pass
id. Other fields are optional
How products work in ExpoPlatform
Products are exhibitor-level records — a product must be attached to an exhibitor profile to exist. Products do not automatically appear in events; they must be explicitly assigned via event_id.
The product/set endpoint handles both the product record (name, description, images, categories — shared across all events) and event assignment in a single call. The status parameter is the only event-scoped value.
Cross-entity dependencies
|
What you need |
Where to get it |
|---|---|
|
Exhibitor ID |
|
|
Category IDs |
|
Body Parameters
Required on create
|
Parameter |
Type |
Description |
|---|---|---|
|
|
integer |
The event to assign the product to |
|
|
integer |
The exhibitor that owns this product |
|
|
string |
Product display name |
|
|
string |
Comma-separated product category IDs |
Optional
|
Parameter |
Type |
Description |
|---|---|---|
|
|
integer |
When provided, updates the matching product |
|
|
string |
Product description |
|
|
integer |
|
|
|
file or URL |
Product images ( |
|
|
boolean |
When |
|
|
boolean |
When |
Error Responses
|
HTTP Code |
Condition |
Error Message |
|---|---|---|
|
400 |
|
|
|
400 |
Required field missing |
|
|
400 |
|
|
|
403 |
Missing or invalid API key |
|
Non-fatal: Invalid category IDs are reported in
data.errorbut do not fail the request.