Product

Endpoint is used to import existing products from your system to Repsly.

Request definition

Keys that determine which records to update or insert are marked with a blue diamond :small-blue-diamond:, while the required keys are marked with a red triangle :small-red-triangle:

Name	Type	Description
Code​ :small-red-triangle: :small-blue-diamond:	String (20)	Unique product code.
Name :small-red-triangle:	String (80)	Product name
ProductGroupCode	String (20)	Unique product group code
ProductGroupName	String (80)	Product group name
Active	Boolean	Marks a product active or inactive
Tag	Text	Tags associated with this product (separated with commas)
UnitPrice ​ :small-red-triangle:	Decimal (18,4)	Product price
EAN	String (20)	International Article Number (Barcode)
Note	String (1000)	Additional product note
ImageUrl	String	Input image url from which product image will be downloaded. ​Must ​be publicly accessible and must ​be direct link to image
MasterProduct	String	Used for grouping purposes
Packaging\Codes\Value	String	List of package code values that match already existing packages inside the system. No new packages can be added through product import
Packaging\IsSet	Boolean	If true, the packaging code values will override existing values in the database for the given product. If false, the packaging values will be ignored

Response definition

Name	Type	Description
Code	Integer	Error identifier (0 = no errors)
Message	String (255)	Response affirmative or error message

For a successful HTTP request (code 200), you will always receive a status response with Code equal to 0 (no error) and Message = “Product import job started asynchronously under ID: {ImportJobID}”, where {ImportJobID} is the key you can use to check the current status of the import. To check the status of the import job you can use **​Import job status​** endpoint.

In case of a HTTP bad request (code 400), you will also receive a status response with Code not equal to 0 and an error message.