Competitor data endpoints

quick reference verb path method post /api/v1/competitor prices/schema/create schema/ create competitors schema post /api/v1/competitor prices/bulk create or update/ bulk update competitors entries define competitors schema description with our api, you can easily create or update entries in our competitor table this table keeps track of all your competitors data before that you need to define the competitors schema curl location request post 'https //api pricemoov com/api/v1/competitor prices/schema/create schema/' \\ \ header 'authorization jwt \<your token>' \\ \ raw data '{ "attributes config" \[ &#x9; "code", &#x9; "product attribute 1", &#x9; "product attribute 2", &#x9; "product attribute x", &#x9; "extension name 1", &#x9; "extension name 2", &#x9; "extension name y" &#x9;], &#x9;"is dated" false }' parameters attributes config type list\[string] , required is dated type boolean , default false , optional allow to defined the granularity of competitors data it corresponds to a subset of the product catalog fields ( code , product attribute 1 , product attribute x , extension name 1 , extension name y ) ⚠️ note that if the product code is specified, then it is not necessary to add any product attributes ( product attribute 1 , product attribute x , …) for rental users, this allows to specify a date at which the corresponding item would be rented example upon success, the response is 201 and returns { "input" { "dimensions" \[ "code", "product attribute 1" "product attribute 2", "product attribute x", "extension name 1", "extension name 2", "extension name y" ] }, "output" {"total" "decimal", "latest update" "date"}, } loading competitor prices into pricemoov description with our api, you can easily create or update entries in your competitors table this table keeps track of all your the prices of your competitors curl location request post 'https //api pricemoov com/api/v1/competitor prices/bulk create or update/' \\ \ header 'authorization jwt \<your token>' \\ \ raw data '\[ { "code" "pc value", "product attribute 1" "pa value 1", "product attribute 2" "pa value 2", "product attribute x" "pa value x", "extension name 1" "en value 1", "extension name 2" "en value 2", "extension name x" "en value x", "competitor price" "59", "competitor name" "notmycompany", "departure date" "2023 07 14", // note this field is optional "latest update" "2023 05 05" // note this field is optional }, ]' parameters code, product attribute 1, product attribute 2, product attribute x, extension name 1,extension name 2, extension name y type string , optional|required competitor price type float , required competitor name type string , required departure date type date , optional latest update type date|datetime , default ingestion date , optional field from product catalog defined by competitors schema corresponds to the price of the item for the competitor name of your competitor for rental users date at which the item is rented format should be yyyy mm dd optional date or datetime at which you recorded this competitor price if not given, it will be set to the date at which you call this api format should be iso 8601 (e g 2023 01 06t09 32 02 788611z ) example upon success, the response is 201 and returns { "created" \[created hash], "updated" \[updated hash], }