Skip to navigation

1.5.2

  • analyses:run can poll its own analyses. GET /analyses/{analysisId} now accepts analyses:run for an an_… analysis created by the same key, so a run-only key can follow the Location it gets back from POST /analyses. Listing analyses, reading another key’s analysis, or reading a saved campaign report still requires analyses:read. The same rule applies to GET /analyses/{analysisId}/comments, which also requires comments:read: a key with analyses:run + comments:read can create, poll, and sample comments on its own analyses.
  • GET /posts?link= answers in one page. Up to 25 links (no more than limit) are looked up directly, tracking parameters and trailing slashes ignored, and come back complete with hasMore: false instead of an empty first page. Other filters such as tag walk further per request and follow the partial-page rule below.
  • Collection post pages no longer time out. GET /collections/{collectionId}/posts stops walking after a time budget and returns what it found with hasMore: true, a nextCursor, and meta.partialPage: true. A page can hold fewer than limit posts (even zero) while hasMore is true — keep following nextCursor until hasMore is false.
  • Older shared snapshots now load on GET /insights. Snapshots shared before the card layout returned 404 insights_not_ready even though GET /snapshots listed them. They now return their summary, topics, notable comments, and vibe check.
  • Absolute links. Analyses and content jobs now include url, and every comments object includes comments.url next to comments.path. Both are absolute URLs on the host you called, so you can follow them without joining paths. comments.path and the Location header are unchanged.
  • GET /analyses?kind=report works again. It returned 503 Analyses index unavailable, and kind=all silently left saved campaign reports out. Both now list reports, newest first.
  • Clearer GET /insights error for post_ids. A post_ids value that is not on your team now returns 404 One or more post_ids were not found instead of Snapshot not found.
  • expiresAt on GET /snapshots is ISO-8601, like createdAt. It was previously a millisecond timestamp.