Skip to content

Report a bug or request a feature

Found a bug, missing a feature, unsure how something works? Tell us. Every message reaches the Meetingize team with the context needed to investigate (account, credential, meeting).

POST /v1/feedback sends a bug report, a feature request, a question or general feedback to the Meetingize team. It works with any valid API key or OAuth token, no specific scope needed.

Terminal window
curl -s -X POST "https://app.meetingize.com/api/v1/feedback" \
-H "Authorization: Bearer $MEETINGIZE_API_KEY" -H "Content-Type: application/json" \
-d '{
"type": "bug",
"message": "GET /v1/meetings/{id}/transcript?format=srt returns an empty file for this meeting. Request id: req_5f0c...",
"meeting_id": "6f0c2a4e-1b7d-4c55-9a51-3e2d8f0b7c11"
}'
FieldDescription
typebug, feature_request, question or feedback (default)
messageyour message, up to 10,000 characters (required)
meeting_idoptional, a meeting of your account the message is about

Response 201 Created:

{ "id": "fb_812", "object": "feedback", "type": "bug", "meeting_id": "6f0c2a4e-...",
"message": "GET /v1/meetings/{id}/transcript?format=srt returns ...", "status": "received" }
  • the endpoint and parameters you called, and what you expected;
  • the request_id of the error (in the error body and in the X-Request-Id header);
  • the meeting, job or document id concerned;
  • the time of the call (UTC).

Never paste API keys, webhook secrets or access tokens in a message.

When Meetingize is connected to Claude, ChatGPT or another assistant through the MCP server, just ask it: “Report to Meetingize that the transcript of my meeting of Monday has the speakers swapped.” The send_feedback tool sends the message after showing you what will be sent.

The Feedback button on every page of the web app lets you send feedback or report a bug.

Write to support@meetingize.com for anything that needs a conversation: integration questions, commercial terms, higher limits, partnership.