Batch-write historized time-series data to points via the Haystack hisWrite op

domain: project-haystack.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. For a single point, send a grid to the hisWrite op with grid meta id set to the point's Ref and rows of ts/val pairs to append
  2. For a batch write across multiple points, omit the meta id and instead define multiple value columns (v0, v1, ...), each with column meta specifying its point's id, sharing a common ts column
  3. Ensure every point in one batch request shares the same configured timezone, since batch hisWrite does not perform timezone conversion
  4. Match each posted value's kind and unit exactly to the point's configured kind/unit - unit conversion is explicitly disallowed by the spec
  5. Expect an empty grid response on success; servers must gracefully absorb any duplicate or out-of-order samples you resend

Known gotchas

Related routes

Read time-series history for points via Haystack's hisRead op
project-haystack.org · 4 steps · unrated
Read and write a Haystack writable point's priority array via the pointWrite op
project-haystack.org · 6 steps · unrated
Read or write a writable point's priority array via the Haystack pointWrite op
project-haystack.org · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans