API

Base: https://sidro-cjenici.vercel.app/api/v1 · OpenAPI 3.1: /api/v1/openapi.json

Authentication

Authorization: Bearer sidro_live_…

An admin creates keys in the dashboard. A key is shown once; only its hash is stored. Every key belongs to its own source: a full sync with that key only deactivates items it sent.

Errors and limits

{ "error": { "code": "invalid_request", "message": "…", "details": {} } }

400 · 401 · 402 plan_limit · 403 (plan without API) · 404 · 409 · 429 (120 requests per minute per key, Retry-After) · 500.

Writing the catalogue

curl -X PUT https://sidro-cjenici.vercel.app/api/v1/items \
  -H "Authorization: Bearer $SIDRO_KEY" -H "Content-Type: application/json" \
  -d '{"items":[{"sku":"KR-500","name":"Kruh bijeli 500 g","price":1.99,"unit":"g","unit_qty":500}]}'

Up to 500 items per request; invalid items come back in errors, the rest are written. Full catalogue in parts: the same full_sync.id in all parts and "final": true in the last one; items of that source that did not appear are deactivated (a sync that saw no items deactivates nothing). An omitted field means "leave unchanged", an explicit null clears it. If the SKU changes but source_ref stays the same, Sidro renames the item and keeps its anchor price and history.

Anchor price via the API

anchor_price on an item is applied only if the item has no confirmed anchor price yet. For a deliberate change use anchor_override: true + anchor_reason, or PUT /anchors/{sku} with a reason. Changes are audit-logged with the key name.

All endpoints are listed below.

{
  "items": [
    {
      "sku": "KR-500",
      "name": "Kruh bijeli 500 g",
      "brand": "Pekara Primjer",
      "price": 1.99,
      "unit": "g",
      "unit_qty": 500,
      "barcode": "3850000000014"
    }
  ]
}

{
  "anchor_price": 12.49,
  "anchor_date": "2026-09-10",
  "reason": "Ispravak prema blagajni 10. 9."
}