Queek docs

Support

Where to ask a question, what to include so it can be answered, and how to report a security issue.

Ask the community

Feature questions, integration help and "how do I…?" belong in GitHub Discussions, asked in the open so the next developer finds the answer.

Talk to us

What to include

A report that can be answered the first time carries:

  • the request_id from the failing response (the error.request_id field, also the X-Request-Id header). It ties your call to Queek's own logs;
  • the method, path and status, and the error.code if there is one;
  • whether the key was _live_ or _test_, and which API (Storefront, Merchant, an app);
  • for a webhook, the webhook-id and the topic;
  • for a theme, the output of npx queek theme info.

Never send a full secret. A key's first characters (sk_live_ab…) are enough to identify it.

Report a security issue

Email [email protected] with the details. Please do not open a public discussion, issue or pull request for a vulnerability: email only, so it can be fixed before it is disclosed.

On this page