Deliverd Analytics API
The Analytics API from Deliverd — 1 operation(s) for analytics.
The Analytics API from Deliverd — 1 operation(s) for analytics.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/deliverd-dev:deliverd-dev-analytics-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Deliverd Dev Analytics API
version: 1.0.0
x-refined-note:
- x-source differs across the merged source definitions and was not carried
description: 'Operations tagged Analytics across 2 of this provider''s published API definitions: deliverd-dev-openapi.json, deliverd-dev-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://deliverd.dev
description: 'Deliverd REST API (paths carry the /api/v1 prefix; https://deliverd.dev/llms.txt: "REST API: https://deliverd.dev/api/v1")'
tags:
- name: Analytics
paths:
/api/v1/analytics:
get:
summary: What is being read, across every report
description: '`GET /reports/{idOrSlug}/analytics` needs to be told which report, so "what is getting read" meant walking the list and adding up. The half that cannot be reconstructed that way is `inactiveReports` — a report nobody has opened does not appear in anything you would think to ask about. Part of analytics, so Team and above; the per-report call returns a total view count on every plan.'
security:
- bearerAuth: []
parameters:
- schema:
type: integer
minimum: 1
maximum: 365
description: The window to count over. 30 by default.
required: false
description: The window to count over. 30 by default.
name: days
in: query
- schema:
type: integer
minimum: 1
maximum: 50
description: How many reports in each list. 10 by default.
required: false
description: How many reports in each list. 10 by default.
name: limit
in: query
responses:
'200':
description: Readership across the organisation
content:
application/json:
schema:
type: object
properties:
days:
type: number
totalViews:
type: number
uniqueViewers:
type: number
activeReports:
type: number
externallySharedReports:
type: number
publicReports:
type: number
publishesInPeriod:
type: number
topReports:
type: array
items:
type: object
properties:
reportId:
type: string
format: uuid
title:
type: string
views:
type: number
uniqueViewers:
type: number
lastViewedAt:
type:
- string
- 'null'
required:
- reportId
- title
- views
- uniqueViewers
- lastViewedAt
inactiveReports:
type: array
items:
type: object
properties:
reportId:
type: string
format: uuid
title:
type: string
lastViewedAt:
type:
- string
- 'null'
publishedAt:
type:
- string
- 'null'
required:
- reportId
- title
- lastViewedAt
- publishedAt
required:
- days
- totalViews
- uniqueViewers
- activeReports
- externallySharedReports
- publicReports
- publishesInPeriod
- topReports
- inactiveReports
'403':
description: '`plan_required` — analytics is on Team and above.'
tags:
- Analytics
operationId: getApiV1Analytics
x-operation-id-source: derived
components:
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: 'API key (dlv_…) created in Settings → API tokens, or an OAuth access token (dlvo_…). Every route below can answer `401 auth_error` — the credential was not accepted — or `403 insufficient_scope`, which is a different thing: the credential is fine and was not issued with the scope this route needs. Reissue it with that scope rather than replacing it with another of the same ones. Older clients may still branch on `auth_error` for both.'
x-refined-from:
- deliverd-dev-openapi.json
- deliverd-dev-openapi.yml