Docker Hub Tag Monitor API

Docker Hub Tag Monitor API collects clean, structured Docker Hub tag data for one or more repositories. Use it to monitor image releases, track latest tags, power release dashboards, and keep deployment automation up to date.

Why use this Docker Hub tag monitor?

Docker images ship fast and break things faster. This actor gives you a simple way to watch the public Docker Hub ecosystem without building your own polling pipeline.

Typical use cases:

• Track the newest image tags for production dependencies
• Watch release cadence for third-party images
• Power notifications, dashboards, and CI/CD checks
• Feed release metadata into analytics or AI workflows

Features

• Monitor one or more Docker Hub repositories in a single run
• Return either a compact latest-tag summary or individual tag records
• Normalize common repository formats like nginx and library/redis
• Include tag timestamps, digest, status, size, and image variant count
• Pay-per-event pricing tied to the records you actually use

Input

Example: quick latest-tag check

{
  "repositories": "nginx, library/redis, apify/actor-python",
  "latestTagOnly": true,
  "maxResults": 5,
  "pageSize": 50
}

Example: detailed tag monitoring

{
  "repositories": "library/nginx, library/postgres",
  "latestTagOnly": false,
  "maxResults": 20,
  "pageSize": 100
}

Input fields

Field	Type	Description
repositories	string	Comma or newline separated Docker Hub repositories to monitor, such as nginx or library/redis.
latestTagOnly	boolean	When enabled, returns one summary record per repository using the newest available tag.
maxResults	integer	Maximum number of dataset records to return across all repositories. Values above 100 are clamped.
pageSize	integer	Number of tags to request per API page. Values above 100 are clamped.

Output

Example record: latest-tag summary

{
  "repositoryName": "library/nginx",
  "namespace": "library",
  "imageName": "nginx",
  "tagName": "latest",
  "tagDigest": "sha256:abc123...",
  "lastUpdated": "2026-05-26T02:00:00.000000Z",
  "lastPulled": "2026-05-26T03:00:00.000000Z",
  "lastPushed": "2026-05-26T02:00:00.000000Z",
  "tagStatus": "active",
  "imagesCount": 2,
  "fullSizeBytes": 123456789,
  "repositoryUrl": "https://hub.docker.com/r/library/nginx",
  "tagUrl": "https://hub.docker.com/r/library/nginx/tags/latest",
  "lastUpdaterUsername": "docker-bot",
  "recordType": "repository_summary"
}

Example record: tag detail

{
  "repositoryName": "library/nginx",
  "namespace": "library",
  "imageName": "nginx",
  "tagName": "1.27.5",
  "tagDigest": "sha256:def456...",
  "lastUpdated": "2026-05-26T02:00:00.000000Z",
  "lastPulled": "2026-05-26T03:30:00.000000Z",
  "lastPushed": "2026-05-26T02:00:00.000000Z",
  "tagStatus": "active",
  "imagesCount": 3,
  "fullSizeBytes": 124000000,
  "repositoryUrl": "https://hub.docker.com/r/library/nginx",
  "tagUrl": "https://hub.docker.com/r/library/nginx/tags/1.27.5",
  "lastUpdaterUsername": "docker-bot",
  "recordType": "tag_record"
}

Limits and caveats

• Repository names must point to public Docker Hub repositories.
• If a repository has very active tag churn, use latestTagOnly=true for a cheaper summary run.
• maxResults is capped at 100 to keep runs predictable and affordable.
• Some repositories expose more tag metadata than others.

Pricing

This actor uses Pay-Per-Event pricing.

Event	Price	Charged when
repository-summary-produced	$0.25 / 1k	A latest-tag summary record is produced
tag-record-produced	$0.75 / 1k	An individual tag record is produced

FAQ

Do I need a Docker Hub account?
No. The actor reads public repository metadata.

What is the difference between summary mode and detail mode?
Summary mode returns one record per repository using the latest tag. Detail mode returns each tag as its own record.

Can I monitor official images?
Yes. Use names like nginx, redis, or python; the actor will resolve them to the library/ namespace.

What if a repository does not exist?
The actor stops with a clear error message so you can fix the input quickly.