SocialHz Engineering · 31 October 2026 · Requested by a customer
Streaming progress, search history and export
GET /api/v1/search?stream=true · GET /api/v1/search/history · POST /api/v1/search/export
What shipped
Three additions behind the new Search page, all available from the API: streamed progress for long searches, a history of the workspace's searches, and export of posts to CSV or XLSX. The page also slices results by keyword, sentiment, language, date and verified authors, and charts them.
Why
Customers were exporting raw JSON and building their charts in spreadsheets before they could share anything. They wanted to watch a big search progress and share the picture straight away.
stream=true
The answer comes as JSON lines (application/x-ndjson), one event per line. The last line is either result, with every field of the usual answer, or error. A mistake found before anything is fetched, like a bad parameter or too few credits, is answered as usual with its HTTP status.
{"type":"start","terms":["Brightleaf","Northwind"],"pages":2}
{"type":"term","term":"Northwind","posts":11,"pages":2}
{"type":"term","term":"Brightleaf","posts":28,"pages":2}
{"type":"result","posts":[…],"terms":[…],"credits":{…}}History
GET /api/v1/search/history lists the workspace's 20 newest searches: query, terms, params as sent, at, and the posts, pages and credits over all their pages. Searches are kept for good, so a search can be run again exactly as it was.
Export
POST /api/v1/search/export?format=csv (or xlsx) with {"name": "…", "posts": […]} returns a file with one row per post, including its link and the terms that found it. Up to 5,000 posts. Nothing is fetched, so nothing is charged.
Switched on per workspace. Ask us and we'll turn it on for yours.
Request a feature
Tell us what you need on the updates page. The engineering team reads every request.