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.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/sendly-now:sendly-now-support-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: Sendly Now Support API
version: 1.0.0
contact:
name: Sendly Support
url: https://sendly.now
license:
name: AGPL-3.0
url: https://www.gnu.org/licenses/agpl-3.0.txt
description: 'Operations tagged Support across 2 of this provider''s published API definitions: openapi.json, sendly-now-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.sendly.now
tags:
- description: Write to Sendly's support team and list what was written, and appeal a project's sending suspension. A ticket reaches the same inbox as the dashboard's support form.
name: Support
paths:
/api/projects/{id}/appeals:
get:
description: Requires the `support:read` scope — See your support tickets.
operationId: listAppeals
parameters:
- description: Project id.
in: path
name: id
required: true
schema:
description: Project id.
type: string
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/AppealList'
description: OK
'400':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Validation error
'401':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Unauthorized — missing or invalid auth
'403':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Forbidden — insufficient permissions or project disabled
'404':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Resource not found
'429':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Rate limit or billing limit exceeded
'500':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Internal server error
security:
- SessionAuth: []
- OAuth2:
- support:read
summary: List a project's appeals
tags:
- Support
post:
description: 'Only for a disabled project, and one per project per 24 hours. A person reviews it and answers by `respondBy`.
Requires the `support:write` scope — Open support tickets and suspension appeals.'
operationId: createAppeal
parameters:
- description: Project id.
in: path
name: id
required: true
schema:
description: Project id.
type: string
requestBody:
content:
application/json:
schema:
properties:
message:
maxLength: 4000
minLength: 20
type: string
required:
- message
type: object
required: true
responses:
'201':
content:
application/json:
schema:
$ref: '#/components/schemas/AppealFiled'
description: Created
'400':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Validation error
'401':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Unauthorized — missing or invalid auth
'403':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Forbidden — insufficient permissions or project disabled
'404':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Resource not found
'429':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Rate limit or billing limit exceeded
'500':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Internal server error
security:
- SessionAuth: []
- OAuth2:
- support:write
summary: Appeal a sending suspension
tags:
- Support
servers:
- url: https://api.sendly.now
/api/v1/support/tickets:
get:
description: 'A person''s own tickets, or an API key''s project''s, newest first (up to 50).
Requires the `support:read` scope — See your support tickets.'
operationId: listSupportTickets
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/SupportTicketList'
description: OK
'401':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`invalid_api_key` or `invalid_session` — missing or invalid credentials.'
'403':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`scope_missing`, `project_access_denied`, or `project_disabled`.'
'422':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`validation_error` — query, path, or body parameters did not match the schema.'
'429':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`rate_limited` — see `Retry-After` and the `RateLimit` headers.'
'500':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`internal_error`.'
security:
- ApiKeyAuth: []
- SessionAuth: []
- OAuth2:
- support:read
summary: List support tickets
tags:
- Support
post:
description: 'Emails the support inbox, with the person''s account email as Reply-To. An API key has no account email, so it sends `wantsReply: false`. Attachments are https links the support team opens; nothing fetches them. Ten tickets per caller per hour.
Requires the `support:write` scope — Open support tickets and suspension appeals.'
operationId: createSupportTicket
requestBody:
content:
application/json:
schema:
properties:
attachments:
items:
format: uri
type: string
maxItems: 5
type: array
body:
maxLength: 4000
minLength: 1
type: string
subject:
maxLength: 200
minLength: 1
type: string
type:
default: question
enum:
- problem
- feature
- question
- other
type: string
wantsReply:
default: true
type: boolean
required:
- subject
- body
type: object
required: true
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/SupportTicketCreated'
description: OK
'401':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`invalid_api_key` or `invalid_session` — missing or invalid credentials.'
'403':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`scope_missing`, `project_access_denied`, or `project_disabled`.'
'422':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`validation_error` — query, path, or body parameters did not match the schema.'
'429':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`rate_limited` — see `Retry-After` and the `RateLimit` headers.'
'500':
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
description: '`internal_error`.'
security:
- ApiKeyAuth: []
- SessionAuth: []
- OAuth2:
- support:write
summary: Write to Sendly support
tags:
- Support
servers:
- url: https://api.sendly.now
components:
schemas:
AppealList:
properties:
data:
properties:
appeals:
items:
additionalProperties: {}
properties: {}
type: object
type: array
firstResponseHours:
type: integer
required:
- appeals
- firstResponseHours
type: object
success:
enum:
- true
type: boolean
required:
- success
- data
type: object
AppealFiled:
properties:
data:
properties:
createdAt:
format: date-time
type: string
firstResponseHours:
type: integer
id:
type: string
respondBy:
format: date-time
type: string
required:
- id
- respondBy
- createdAt
- firstResponseHours
type: object
success:
enum:
- true
type: boolean
required:
- success
- data
type: object
Problem:
description: RFC 9457 problem document, served as `application/problem+json`. Returned by every 4xx/5xx response on the `/api/v1` surface.
properties:
code:
description: Machine-readable lowercase error code, e.g. `scope_missing`.
type: string
detail:
description: Explanation specific to this occurrence.
type: string
errors:
description: Field-level failures. Present on 422 `validation_error` responses.
items:
properties:
code:
type: string
message:
type: string
pointer:
description: RFC 6901 JSON Pointer to the offending field.
type: string
required:
- pointer
- code
- message
type: object
type: array
instance:
description: Request path the failure occurred on.
type: string
next:
description: The tool an agent calls next to repair this failure — `request_scopes` for a missing permission, `upgrade_plan` for an exhausted plan. Absent when no tool repairs it.
properties:
args:
additionalProperties: {}
description: Arguments to call it with.
type: object
tool:
description: The MCP tool that repairs this failure, e.g. `upgrade_plan`.
type: string
required:
- tool
type: object
request_id:
description: Correlation id — quote it in support requests.
type: string
status:
description: HTTP status code, repeated in the body.
type: integer
title:
description: Short, stable summary — the same for every occurrence of a `type`.
type: string
type:
description: Dereferenceable URI identifying the error class, anchored on the docs errors page.
format: uri
type: string
required:
- type
- title
- status
- code
type: object
Error:
description: 'Standard error envelope returned by all 4xx/5xx responses. Migrated routes include `success: false`; 422 validation errors add `error.details.errors`.'
properties:
error:
properties:
code:
type: string
details:
properties:
errors:
items: {}
type: array
required:
- errors
type: object
message:
type: string
required:
- message
- code
type: object
success:
enum:
- false
type: boolean
required:
- error
type: object
SupportTicketCreated:
properties:
status:
description: '`sent`: the support inbox got it. `logged`: it was recorded but the email failed; support still sees it.'
enum:
- sent
- logged
type: string
ticketId:
type: string
required:
- ticketId
- status
type: object
SupportTicketList:
properties:
items:
items:
properties:
createdAt:
format: date-time
type: string
id:
type: string
source:
enum:
- support_page
- error_prompt
- mcp
- api
type: string
status:
enum:
- sent
- logged
type: string
subject:
type: string
type:
enum:
- problem
- feature
- question
- other
type: string
required:
- id
- type
- subject
- status
- source
- createdAt
type: object
type: array
required:
- items
type: object
securitySchemes:
ApiKeyAuth:
bearerFormat: API Key
description: 'API key authentication. Use a `sk_*` (FULL) or `pk_*` (SENDING_ONLY) key as the bearer token. Public keys (`pk_*`) are restricted to the email-send endpoints and the self-serve list subscribe/unsubscribe pair; every other endpoint — event tracking included — answers 403 for them. In scope terms (used by `/api/v1/*` operations): FULL keys hold every scope; SENDING_ONLY keys hold only `emails:send`.'
scheme: bearer
type: http
MailgunBasicAuth:
description: 'Mailgun-style authentication for the `/api/compat/mailgun/*` operations only: HTTP Basic with the username `api` and a Sendly API key (`sk_*`, or a `pk_*` send-only key) as the password, exactly as mailgun.js sends it.'
scheme: basic
type: http
OAuth2:
description: 'OAuth 2.1 with PKCE, for AI agents and other delegated clients (this is what the MCP endpoint at `/api/mcp` uses, and how a third-party application sends on a user''s behalf). Tokens are minted through the consent screen and carry ONLY the scopes the user ticked there, so an operation lists the single scope it requires and a token without it answers `403` with code `SCOPE_MISSING` — before any input is parsed. Unlike an API key, a delegated token reaches an operation only where the route itself declares a scope; every other route refuses it outright.
**Ask for the right audience.** Pass `resource=https://app.sendly.now/api` on the authorization AND the token request to receive a token for this REST API; `resource=https://app.sendly.now/api/mcp` is the MCP endpoint''s identifier. A request carrying no `resource` receives an OPAQUE token, which every endpoint here rejects. Each identifier publishes RFC 9728 metadata at `/.well-known/oauth-protected-resource/api` and `/.well-known/oauth-protected-resource/api/mcp`.
**Name the project on every call.** An OAuth grant belongs to a USER, not to a project — the same person may belong to several — so a delegated token carries no tenant and the project is chosen per request with the `x-project-id` header, checked against real membership. Omit it and a project-scoped operation answers `400`; send one the user does not belong to and it answers `403 PROJECT_ACCESS_DENIED`. List the projects a token may name with `GET /api/users/me/projects` (scope `projects:read`), which needs no header. API keys are unaffected: a key already names its project.'
flows:
authorizationCode:
authorizationUrl: https://app.sendly.now/api/auth/oauth2/authorize
refreshUrl: https://app.sendly.now/api/auth/oauth2/token
scopes:
account:read: See your profile and notification preferences
account:write: Edit your profile and preferences, export your data, delete your account
analytics:read: View your sending analytics and engagement metrics
api-keys:read: See which API keys exist, including what each one is allowed to do
api-keys:write: Create, rotate, and revoke API keys — these keep working even after you disconnect this app
billing:read: See your plan, usage, invoices and spending limits
billing:write: Start a checkout, change spending limits, open the billing portal, cancel or refund
campaigns:read: View your campaigns and their performance
campaigns:send: Send or schedule your campaigns to their audience
campaigns:write: Create, edit, and organize your campaigns
connections:read: See connected services such as Slack and connected AI apps
connections:write: Connect, re-verify and disconnect services
contacts:read: View your contacts and their custom fields
contacts:write: Create, update, and delete your contacts
deliverability:read: Check why mail from one of your domains is not arriving
domains:read: View your sending domains and their verification status
domains:write: Add and remove sending domains, and trigger verification
emails:read: View the emails you have sent and their delivery status
emails:send: Send emails from your verified domains
emails:test: Send test emails to your own address from the Sendly sandbox
events:read: View the custom events your application has recorded
events:write: Record custom events for your contacts
lists:read: View your subscriber lists and who is on them
lists:write: Create, rename, and delete your subscriber lists
mailbox-conversations:read: Read the conversations in your hosted mailboxes — every message and attachment people have sent you
mailbox-conversations:reply: Reply to conversations in your hosted mailboxes, from the mailbox's own address
mailboxes:read: View the mailboxes on your domains and their settings
mailboxes:send: Write and send new email from your hosted mailboxes, as that address
mailboxes:write: Create and delete mailboxes on your verified domains
members:read: See who belongs to your projects
members:write: Add and remove project members and change their roles
projects:read: View your projects and their settings
projects:write: Create, change, reset and delete projects on your account
segments:read: View your segments and who belongs to them
segments:write: Create, edit, and delete your segments
support:read: See your support tickets
support:write: Open support tickets and suspension appeals
suppression:read: View the addresses on your suppression list
suppression:write: Add and remove addresses on your suppression list
templates:read: View your email templates
templates:write: Create, edit, and delete your email templates
topics:read: View the topics you mail about and who is subscribed to each
topics:write: Create and edit topics, and change what your contacts are subscribed to — this decides who your campaigns reach
usage:read: View your usage totals and billing limits
validation:read: View your email validation runs and their results
validation:write: Check whether email addresses can receive mail — this is billed per address
webhooks:read: View your webhook endpoints and their delivery history
webhooks:write: Create, edit, and delete your webhook endpoints
workflows:read: View your automation workflows and their runs
workflows:write: Create, edit, enable, and delete your automation workflows
tokenUrl: https://app.sendly.now/api/auth/oauth2/token
type: oauth2
PostmarkServerToken:
description: 'Postmark-style authentication for the `/api/compat/postmark/*` operations only: a Sendly API key (`sk_*`, or a `pk_*` send-only key) sent in the `X-Postmark-Server-Token` header, exactly where the postmark SDK puts its server token.'
in: header
name: X-Postmark-Server-Token
type: apiKey
SessionAuth:
description: BetterAuth session cookie. Used by the dashboard / browser clients. When present, the active project is taken from the `x-project-id` header.
in: cookie
name: better-auth.session_token
type: apiKey
x-refined-from:
- openapi.json
- sendly-now-openapi.json