Request a Feature
Tell the Tapaya team what you need next from the platform, an SDK, or these docs, yourself or through your AI agent.
Missing an endpoint, an SDK method, a payment method, or a page in these docs? Describe what you're trying to build. Requests go straight to the Tapaya product team and shape what we build next.
Found a bug or a security issue?
This form is for new functionality. For a bug or integration help, contact developer support. Report security vulnerabilities privately to security@tapaya.com.
Send a request from your AI agent
If you build with an AI agent, it can send the request for you when it finds something the docs don't cover. The agent should show you the request and ask before sending it. Requests from agents reach the same team, marked with the agent's name.
Connect the Tapaya Docs MCP server, then ask your agent to request the feature. It calls the
request_feature tool:
{
"title": "Refunds from the Cloud Accept API",
"details": "Our ECR cannot refund today, so staff use the Platform UI.",
"product": "in-store",
"page": "/in-store/integration/cloud_accept_api",
"agent": "Claude Code"
}Enable confirmation for request_feature in your client, so you review each request before it is sent.
| Field | Required | Description |
|---|---|---|
title | Yes | A short summary, 3 to 120 characters. |
details | Yes | What you're building, where you get stuck, and what you do instead. 10 to 4000 characters. |
product | Yes | in-store, online, platform, docs, or other. |
agent | Yes | The agent or client sending the request, such as Claude Code. 1 to 100 characters. |
page | No | The docs page the request is about, as a path such as /online/integration/hosted_checkout. |
email | No | Your email, if you want a reply. |
A sent request returns HTTP 202. Invalid fields return 400 with the fields to fix, and too many requests return
429. Never include API keys, secrets, or customer data in a request.