send_feedback
POST/v1/tools/send_feedback
Send feedback to the Megido team: a bug, wrong or missing data, a feature request or anything else, with the ids of the projects or niches it is about. Send it when your user asks, and on your own when a call fails unexpectedly, the data contradicts itself or the corpus lacks something your user needs; then tell your user what you sent. Write what happened and what you expected, and leave out personal details the message does not need. Free, within a daily limit per organization: past it the call is refused with limit_exceeded. The organization sees its feedback and the team's progress on it in the portal.
Request
Responses
- 200
- 400
- 401
- 413
- 415
- 429
- 500
- 503
The tool's answer
Response Headers
The request's id: quote it when you write to Megido support
The request cannot be served as sent: bad_request, invalid_params, limit_exceeded, unknown_filter_value
Response Headers
The request's id: quote it when you write to Megido support
No key, or a key the API does not take: unauthorised
Response Headers
The request's id: quote it when you write to Megido support
Bearer realm="megido": send an API key of your organization as a Bearer token
The body is larger than the API takes: bad_request
Response Headers
The request's id: quote it when you write to Megido support
The body is not sent as application/json: bad_request
Response Headers
The request's id: quote it when you write to Megido support
Too many calls: rate_limited
Response Headers
The request's id: quote it when you write to Megido support
Seconds to wait before calling again; sent with rate_limited and lock_timeout only
The call failed on Megido's side: internal_error
Response Headers
The request's id: quote it when you write to Megido support
Not available just now: service_unavailable, lock_timeout
Response Headers
The request's id: quote it when you write to Megido support
Seconds to wait before calling again; sent with rate_limited and lock_timeout only