---
title: "Get a post's numbers day by day"
method: GET
path: "/network-posts/{id}/timeline"
tags: ["Network posts"]
---

# Get a post's numbers day by day

`GET /network-posts/{id}/timeline`

## Request

- Base URL: `https://api.rizamo.com/v1`
- URL: `https://api.rizamo.com/v1/network-posts/{id}/timeline`
- Auth: HTTP bearer

What each day added to the post's numbers, and the totals after it, from Rizamo's reads: 1 hour and 6 hours after it went out (TikTok's and YouTube's from 24 hours), then daily to day 90 and every 30 days after (YouTube every 28). A day with no point had no change. A change between two reads several days apart is one point over those days, never split, and `gaps` says why, as it does for days Rizamo could not read. Days are the profile's.

## Path parameters

- `id` string, required: The post on the network's id (`npost_`).

## Query parameters

- `timeZone` string: The time zone the days are in: the profile's when left out.

## Response `200`

OK

- NetworkPostTimeline
  - `networkPostId` string, required
  - `timeZone` string, required: The time zone the days are in.
  - `points` object[], required: Oldest first. A day with neither a point nor a gap had no change. A point over several days is a change Rizamo cannot place on one day, never split: `gaps` says why.
    - `from` string, date, required: The first day the change covers: the same as `date` for one day.
    - `date` string, date, required: The last day it covers.
    - `change` object, required: What each count gained over those days. A value the network hides counts as 0. An average, such as avg_watch_time, is not a count: it is in `total` only, since the difference of two averages is not what the days added.
    - `total` object, required: Each of those numbers at the end, as the network reported it, averages included: null where it hides it.
    - `masked` string[], required: The numbers in `total` the network hides because they are small (Meta: under 5).
    - `source` 'poll' | 'webhook' | 'network_daily', required
    - `checkedAt` string, date-time, required: When the numbers at the end were read or received.
  - `gaps` object[], required: Days whose numbers Rizamo could not read one by one, or not at all, and why.
    - `from` string, date, required
    - `to` string, date, required
    - `reason` string, required

## Other responses

- `400`: `invalid_request`: A field is missing or wrong, or the request cannot be done as asked: the message names the field or says what to change.
- `401`: `unauthorized`: No API key or sign-in, or the key does not work: it was deleted, or it expired.
- `403`: `forbidden`: The caller may not do this: the key or agent lacks the scope (the message names it), or the action needs another role or a fresh sign-in.
- `404`: `not_found`: No such object, or it is outside your team or the profiles your key reaches.
- `429`: `rate_limited`: Over one of Rizamo's limits, or a network asked Rizamo to slow down: wait for `Retry-After` seconds, or as long as the message says.
- `500`: `internal`: Our side failed: retry, and send the `requestId` if it keeps failing.
- `503`: `timeout`: The request took too long to work out, most often a report: try again in a moment, or ask a report for a shorter period or one profile.

---

[API](https://skmtc.dev/rizamo/apis/rizamo-api.md) - [All operations](https://skmtc.dev/rizamo/apis/rizamo-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rizamo/apis/rizamo-api/revisions/31b0c1b1ffb5?raw)
