Sequenzy Feedback API
The Feedback API from Sequenzy — 1 operation(s) for feedback.
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/sequenzy:sequenzy-feedback-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 Specification
openapi: 3.2.0
info:
title: Sequenzy Feedback API
description: Sequenzy API for managing subscribers, tags, events, sequences, and transactional emails
version: 1.0.0
servers:
- url: https://api.sequenzy.com/api/v1
description: Production server
- url: https://api.sequenzy.com/v1
description: Legacy production server alias
security:
- bearerAuth: []
tags:
- name: Feedback
paths:
/feedback:
post:
operationId: submitFeedback
summary: Submit feedback
description: Submits product feedback about Sequenzy itself to the Sequenzy team - for example, when a workflow you or your user needed is not exposed via the API, CLI, or MCP server.
tags:
- Feedback
requestBody:
required: true
content:
application/json:
schema:
type: object
additionalProperties: false
required:
- message
properties:
message:
type: string
minLength: 1
maxLength: 10000
description: The feedback itself. Be specific about what was needed and what was missing or wrong.
example: There is no endpoint to bulk-delete campaigns by label.
category:
type: string
enum:
- missing_capability
- bug
- docs
- ux
- praise
- other
description: Feedback category. Use missing_capability when a needed workflow is not supported. Defaults to other.
source:
type: string
enum:
- api
- cli
- mcp
description: Where the feedback was submitted from. Defaults to api.
context:
type: string
maxLength: 10000
description: Optional description of what you were trying to accomplish when you hit the gap.
userIntent:
type: string
maxLength: 5000
description: For bug or wrong-outcome reports - the user's request, verbatim or closely paraphrased. Omit personal data not needed to reproduce the problem.
example: Move the promo send to 9am Tuesday
toolCalls:
type: array
maxItems: 25
description: For bug or wrong-outcome reports - the ordered API calls, CLI commands, or MCP tool calls that led to the problem. Summarize arguments; do not include raw subscriber data.
items:
type: object
additionalProperties: false
required:
- tool
properties:
tool:
type: string
minLength: 1
maxLength: 200
description: Tool, command, or endpoint name.
example: update_campaign
args:
type: string
maxLength: 2000
description: Short summary of the arguments used.
error:
type: string
maxLength: 2000
description: Error returned by this call, if any.
expected:
type: string
maxLength: 5000
description: What you expected to happen.
actual:
type: string
maxLength: 5000
description: What actually happened instead.
resourceIds:
type: array
maxItems: 50
description: IDs of the affected resources so the team can correlate the report with server logs.
items:
type: string
minLength: 1
maxLength: 200
example:
- cmp_123
responses:
'200':
description: Feedback received
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: true
message:
type: string
example: Feedback received. The Sequenzy team reviews every submission.
'400':
description: Validation error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: No company selected
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Feedback could not be delivered
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
components:
schemas:
InputIssue:
type: object
properties:
path:
type: string
description: Dotted field path, such as `audience.subscriberIds[0]`. Empty when the problem is with the request body itself.
example: kind
message:
type: string
description: What is wrong with the field.
example: must be "add_tags"
allowedValues:
type: array
description: Accepted values when the field only takes a fixed set of values.
items: {}
example:
- add_tags
required:
- path
- message
Error:
type: object
properties:
success:
type: boolean
example: false
error:
type: string
example: Error message
code:
type: string
description: Optional stable machine-readable error discriminator when available.
example: COMPANY_CREATE_REQUIRES_PERSONAL_KEY
retryable:
type: boolean
description: Whether retrying the request can recover from the error.
issues:
type: array
description: Field-level problems with the request, when the endpoint reports them. Up to ten entries; `error` summarizes the first three.
items:
$ref: '#/components/schemas/InputIssue'
required:
- error
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: API key passed as Bearer token