GunSpec
Feedback

Feedback and support

A wrong figure, a missing record, a bug in an endpoint, a page that did not answer your question: every one of those has a channel, and each one lands with a person.

Which channel

Pick by what you found. Data corrections and support both have an API, so an integration can file them without a browser.

A wrong or missing figure

File a data report against the record and the section it concerns. Reviewed by a person; a correction goes into the catalog through the same path staff use.

How it works

Something broken or unclear

Open a support ticket. Include the X-Request-Id of a failing call and we can see the request itself.

How it works

This documentation

Every page has a helpful / not helpful control and a report link in its footer. Both reach us as tickets with the page and endpoint attached.

How it works

A feature you need

A ticket in the feature-request category. The ones that recur shape the roadmap; a reply tells you when one ships.

How it works

A security weakness

Not a ticket. Email security@gunspec.io privately; the disclosure policy says what to include and what we promise back.

How it works

Support tickets over the API

POST /v1/me/support opens a ticket with a category and a requested priority; GET /v1/me/support lists yours, and replies go to /v1/me/support/{ticketId}/replies. The same tickets appear in your profile on the site. Shapes are in the reference.

Open a technical ticket
bash
curl -X POST https://api.gunspec.io/v1/me/support \  -H "X-API-Key: your_api_key" \  -H "Content-Type: application/json" \  -d '{    "subject": "Webhook deliveries stopped after rotating the secret",    "category": "technical",    "priority": "normal",    "description": "Endpoint ep_… has returned 401 since 09:40 UTC. Request id 8f3c2b1a."  }'

Request body

  • subjectstringrequired

    One-line summary of the issue.

  • descriptionstringrequired

    Prose summary of the record, where one has been written.

  • categoryenum

    What the ticket is about. Not a firearm or attachment category.

    • billing
    • technical
    • data_quality
    • feature_request
    • other
  • priorityenum

    Triage priority you are asking for. Staff may change it.

    • low
    • normal
    • high
    • urgent

Lifecycle

  1. open
  2. in_progress
  3. waiting
  4. resolved
  5. closed
  • Quote the request id of a failing call. It finds the request, its status and its error code in our logs without a back-and-forth.
  • Priority is what you are asking for; staff may change it. Studio and Enterprise plans carry priority and dedicated support respectively.
  • Replies from us arrive on the ticket and by email; a reply from you reopens a resolved ticket.

Support in the referenceYour tickets in your profile

Feedback on these pages

Two controls sit in the footer of every page.

  • Was this page helpful: one click, no account. Counted per page so we know which pages need work.
  • Report a problem: a short form that opens a support ticket with the page, the endpoint in view and the URL attached, so you never have to describe where you were.
  • Every page also has Copy page and Open in ChatGPT / Claude / Perplexity in its header, and a Markdown version, so you can ask an assistant about it and send us what it got wrong.

What happens next

Tickets are answered by a person. Data reports have a page of their own, with the path a report takes from filed to corrected.

  1. 1A ticket answers on the ticket itself and by email. Feature requests stay open until they ship or are declined with a reason.

Security issues

Do not file a security weakness as a ticket or a data report. Email security@gunspec.io privately; the disclosure policy covers scope, safe harbour and what you can expect from us.