Sign in
← AI PulseSep 22, 2026

Wire · news · Single-source brief

Artifacts Endpoints in Claude API Reference

The Claude API reference now includes Artifacts endpoints, allowing users to retrieve artifact-creation activity for a specific day, categorized by MIME type.

By Illumora Editorial

Source · Sep 22, 2026, 1:00 AM · On Illumora · Sep 22, 2026, 1:02 AM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →Anthropic Docs (prompting) — Artifacts - Claude API Reference
Save

The Claude API Reference has been updated to include Artifacts endpoints. These new endpoints enable users to access data on artifact creation activity for a given day, with results broken down by MIME type.

Key Points

  • The Claude API Reference now includes Artifacts endpoints.
  • These endpoints provide artifact-creation activity for a specified day.
  • Activity data is broken out by MIME type.
  • The next_page field is null for ungrouped queries, as the artifact-type cube is finite and returned completely.
  • Grouped queries (using group_by[] on product, user_id, or rbac_group_id) paginate results.

Context

According to the Anthropic Docs, the Artifacts endpoints are part of the /v1/organizations/analytics/artifacts path. Ungrouped queries return the full artifact-type cube, while grouped queries multiply the cube and paginate similarly to other analytics list endpoints.

Why It Matters

Builders can now programmatically access detailed daily artifact creation metrics, which can inform usage patterns and resource allocation within their organizations.

What To Do

  • Review the Artifacts endpoints documentation in the Claude API Reference.
  • Test the GET /v1/organizations/analytics/artifacts endpoint to retrieve daily artifact activity.
  • Experiment with group_by[] parameters (product, user_id, rbac_group_id) to explore paginated, grouped analytics.
  • Note how next_page behaves differently for grouped versus ungrouped queries.