issue_reports

Report a problem

Tell the Pomerado team about friction Pomerado caused, or something that worked notably well.

  • Report each problem once, when it happens: something slow, an unexpected error, a confusing description or answer, a wrong result, or a design you had to work around. Not your own input mistakes, or website problems Pomerado explained.
  • To change one tool, such as adding a filter, input or output, use POST /v1/tools/{id}/changes instead.
  • Never include passwords, codes, tokens, card numbers, personal details, page content or your users' data.
  • Pomerado attaches who sent the report and from where. It links the related job, tool and integration only when you can read them.
  • The same report from you within a day counts again (status merged). Your account can send 50 reports an hour and 200 a day, across its members and clients; past that it answers report_limit_reached, and you carry on without retrying.
  • Reports are kept 90 days and only help the Pomerado team improve Pomerado. They are not a support channel: if it is urgent, email founders@pomerado.ai (the receipt's message also gives the Discord invite).
post/v1/issue-reports

Request

  • Base URL: https://api.pomerado.ai
  • URL: https://api.pomerado.ai/v1/issue-reports
  • Auth: HTTP bearer

Request body

summarystring required

One sentence saying what happened, 10 to 200 characters.

category'slow' | 'error' | 'confusing' | 'workaround' | 'wrong_result' | 'missing_capability' | 'worked_well' | 'other' required

slow: a tool or job took too long. error: an error you didn't expect, or one that didn't say how to fix it. confusing: a description, input or answer that was unclear. workaround: you had to work around a design, with extra calls, guessing or retrying. wrong_result: a result was wrong. missing_capability: Pomerado can't do something you needed. worked_well: something worked notably well. other: anything else.

task_outcome'completed' | 'completed_with_workaround' | 'partially_completed' | 'blocked'

How your task ended: completed, completed_with_workaround, partially_completed or blocked.

detailsstring

What you tried and what happened, up to 4,000 characters, quoting exact tool names, error codes and parameter names.

suggested_improvementstring

The one change that would have helped, up to 1,000 characters.

waited_secondsinteger

an integer

Example request

{
  "related": {
    "job_id": "job_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190",
    "tool_id": "tool_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190",
    "integration_id": "int_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190"
  }
}

Response

The stored report

report_idstring required

The report's ID: rpt_ and 32 hex digits

status'recorded' | 'merged' required

recorded: a new report. merged: you sent the same report within the last day, so it counted again

severity'high' | 'medium' | 'low' | 'none' required

Derived by Pomerado: high for a blocked task; medium for a partial one, a workaround or an error on a job that failed on Pomerado's side; none for worked_well; otherwise low

messagestring required

What to do next

Changes

No recorded changes to this operation across all 2 revisions of this API.