Reprice Simulate - Custom JSON Data

Simulates repricing using custom JSON data instead of database. Bypasses prepare_data entirely - you provide the product data directly and get the full repricing result with execution log.

HTTP: POST /reprice_simulate

Query parameters

Name	Type	Required	Description	Example
domain	string	yes	Domain name or project ID to use for strategy/rule lookup.	profi-parfemy.cz
data	json	yes	Complete product data in the same format as prepare_data output. Use dsl_data for DSL variables, basic_data for product info, and competition for competitor prices.	{"product_id":"900258","dsl_data":{"price_buy":450,"price_rrp":890,"current_price":699,"stock":15,"brand":"Calvin Klein","category":"parfemy","competition_count":3,"competition_min":620,"competition_max":750,"competition_avg":680},"basic_data":{"nazev_produktu":"CK One EDT 200ml","price_buy":450,"price_rrp":890},"competition":{"count":3,"products":[{"price":620,"shop":"parfemy.cz"},{"price":680,"shop":"notino.cz"},{"price":750,"shop":"elnino.cz"}]}}
strategy_id	integer	no	Optional: Test only specific strategy (default: all project strategies).	5
rule_id	integer	no	Optional: Test only specific rule (default: all matching rules).	42

Notes

Bypasses prepare_data and database entirely - uses provided JSON data directly.
DSL variables: price_buy, price_rrp, current_price, stock, brand, category, warehouse_cnt, competition_count/min/max/avg.
Competition array: include actual competitor prices for competition-based rules.
Returns complete execution log with all DSL evaluations and guardrail checks.
Does NOT save results to database or logs - pure simulation.
Useful for testing repricing logic with custom/hypothetical data.

Sample request

curl -X POST https://admin.elpricing.com/api/reprice_simulate
  -H "Authorization: ApiKey YOUR_API_KEY"
  -H "Content-Type: application/json"
  -d '{"domain":"profi-parfemy.cz","data":{"product_id":"900258","dsl_data":{"price_buy":450,"price_rrp":890,"current_price":699,"stock":15,"brand":"Calvin Klein","category":"parfemy","warehouse_cnt":2,"competition_count":3,"competition_min":620,"competition_max":750,"competition_avg":680},"basic_data":{"nazev_produktu":"CK One EDT 200ml","price_buy":450,"price_rrp":890,"stock":15},"competition":{"count":3,"products":[{"price":620,"shop":"parfemy.cz"},{"price":680,"shop":"notino.cz"},{"price":750,"shop":"elnino.cz"}]}}}'

Interactive call

HTTP MethodDomainDomain name or project ID to use for strategy/rule lookup.Product Data JSONComplete product data in the same format as prepare_data output. Use dsl_data for DSL variables, basic_data for product info, and competition for competitor prices.Strategy IDOptional: Test only specific strategy (default: all project strategies).Rule IDOptional: Test only specific rule (default: all matching rules).

Queue workflow

Tasks are persisted to var/api_queue/tasks.json. Process them with:

php go.php cron:list\nphp go.php cron:go

Logs are written to var/api_queue/logs/{task_id}.log.