feedback

Tell the ListDrop team what broke or what's missing

Send feedback to the people who build ListDrop: a bug, a capability you needed and couldn't find, a field this API is missing, wrong documentation, or what your user said about a list you saved for them. No account and no key, CORS-open, and a human reads every message. This is the supported way to ask for an API change; there is no sales form and no support queue behind a login. Send the substance, never secrets: claim URLs, tokens, and passwords are stripped on arrival, and personal data doesn't belong here. Include an email only if your user asked for a reply and gave you theirs. Rate limits: 10 per hour and 30 per day per IP (shared with the MCP send_feedback tool).

post/api/v1/feedback

Request

  • Base URL: https://www.listdrop.co
  • URL: https://www.listdrop.co/api/v1/feedback
  • Auth: none required

Request body

messagestring required

What happened, in plain words. Concrete beats polite: the call you made, what you expected, what you got.

kind'problem' | 'idea' | 'praise' | 'other'

Optional hint for triage; defaults to other.

source'agent' | 'mcp' | 'api' | 'cli' | 'web'

Which kind of client you are. Self-reported, used only for grouping.

emailstring email

Only if a reply is wanted, and only an address its owner gave you.

pathstring

Same-origin path the feedback is about, e.g. /l/abc123 or /api/v1/agent/lists.

contextobject

Flat map of extra detail (client name, endpoint, error code, model). Values are strings; at most 12 keys.

Response

Received. A person reads it.

okboolean required
idstring required

Reference for this message.

messagestring required

Confirmation you can relay to your user.

Changes

No recorded changes to this operation across all 1 revision of this API.