Send feedback
Tells Maple about a bug, a missing capability, wrong docs, or an error you could not act on. Cite the request_ids involved so we can see what you sent. Maple copies its request history for ids it recognizes and keeps any other id as given, so a report is never refused over an id. Any credential may send feedback; no scope is required. Each app may send 20 per environment per hour; beyond that the API answers 429 with Retry-After. Maple reads feedback every week. Nothing changes automatically when you send it, and you get no reply through the API. This contract will not break: fields and kind values may be added, never removed, renamed, or made required.
Authorizations
API key — mpk_test_… for the sandbox, mpk_live_… for production. Issued by Maple during partner onboarding.
Body
bug: the API did something wrong. missing_capability: you needed something the API cannot do. docs_wrong: the docs or reference disagree with the API. unclear_error: an error did not tell you what to change. other: anything else.
bug, missing_capability, docs_wrong, unclear_error, other One line, at most 200 characters.
1 - 200^[^\u0000-\u001F\u007F-\u009F\u2028\u2029]*$What you were trying to do, as a goal (for example, "seat a walk-in party of four"). Leave it out when the feedback is not about a task.
1 - 4000^[^\u0000]*$What you expected the API to do.
1 - 4000^[^\u0000]*$What the API did instead.
1 - 4000^[^\u0000]*$The method and path this is about, for example POST /v1/waitlist_entries.
1 - 200^[^\u0000]*$Up to ten ids of the requests this is about, usually the x-request-id response header. Maple copies what its request history holds for ids this app made in this environment in the last seven days; any other id is kept as you sent it.
101 - 200^[^\u0000]*$Response
Success
feedback bug, missing_capability, docs_wrong, unclear_error, other received