Deliverd Audiences API
The Audiences API from Deliverd — 1 operation(s) for audiences.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/deliverd-dev:deliverd-dev-audiences-api"
All apis
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.
Get an API 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 Specification
openapi: 3.2.0
info:
title: Deliverd Dev Audiences API
version: 1.0.0
x-refined-note:
- x-source differs across the merged source definitions and was not carried
description: 'Operations tagged Audiences 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: Audiences
paths:
/api/v1/audiences/resolve:
post:
summary: Resolve natural-language audience phrases
security:
- bearerAuth: []
requestBody:
content:
application/json:
schema:
type: object
properties:
phrases:
type: array
items:
type: string
minLength: 1
maxLength: 200
minItems: 1
maxItems: 20
required:
- phrases
responses:
'200':
description: Resolution result with disambiguation candidates
content:
application/json:
schema:
type: object
properties:
resolved:
type: array
items:
type: object
properties:
phrase:
type: string
principal:
type: object
properties:
type:
type: string
enum:
- owner
- user
- workspace
- group
- org
- guest
- link
- public
- domain
id:
type:
- string
- 'null'
format: uuid
value:
type: string
maxLength: 253
label:
type: string
required:
- type
- id
confidence:
type: number
minimum: 0
maximum: 1
required:
- phrase
- principal
- confidence
ambiguous:
type: array
items:
type: object
properties:
phrase:
type: string
candidates:
type: array
items:
type: object
properties:
type:
type: string
enum:
- owner
- user
- workspace
- group
- org
- guest
- link
- public
- domain
id:
type:
- string
- 'null'
format: uuid
label:
type: string
detail:
type: string
score:
type: number
required:
- type
- id
- label
- score
required:
- phrase
- candidates
unresolved:
type: array
items:
type: object
properties:
phrase:
type: string
suggestion:
type: string
required:
- phrase
- suggestion
required:
- resolved
- ambiguous
- unresolved
tags:
- Audiences
operationId: postApiV1AudiencesResolve
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