Count updates since a time

Returns the number of published, non-blog updates created for a project since a given point in time. This is the same set of updates that would be rendered to users, so it’s handy for polling clients (for example a mobile widget) that want to show a “new updates” badge without downloading the full list.

GET /api/v1/projects/{id}/updates_since?time={unix_epoch}

Authentication

None. Like the updates listing, this endpoint only exposes already-public data (published updates), so it’s safe to call from widgets embedded in mobile apps or other clients where a token would be exposed.

Path parameters

Parameter	Type	Description
`id`	string	The project ID to count updates for.

Query parameters

Parameter	Type	Required	Description
`time`	integer	Yes	Unix epoch time in seconds. Only updates created after this instant are counted.
`audience`	string	No	Narrows the count to one or more audiences, matching the filtering of the updates listing.

Pass audience whenever the client that shows the badge also passes it when fetching the list, otherwise the badge counts updates that client will never display. Identify an audience by slug or id, and pass several either comma separated (audience=beta,enterprise) or as an array (audience[]=beta&audience[]=enterprise).

Example request

curl "https://updatify.io/api/v1/projects/PROJECT_ID/updates_since?time=1752710400"

# Only counting what beta testers would see
curl "https://updatify.io/api/v1/projects/PROJECT_ID/updates_since?time=1752710400&audience=beta"

Response

200 OK with the count of matching updates.

{
  "result": 3
}

Field	Type	Description
`result`	integer	Number of published, non-blog updates created after `time`.

Errors

Status	Meaning
`400 Bad Request`	The `time` parameter is missing or not a valid unix epoch value.
`404 Not Found`	The project doesn’t exist.

If time is missing or invalid:

{
  "success": false,
  "errors": "Invalid or missing `time` param (expected unix epoch seconds)"
}

See Errors for details.