GunSpec

My Reports

Submit and track data quality reports for specific firearms. Use reports to flag inaccurate or missing specifications so the GunSpec team can review and correct the data.

Auth RequiredExplorer+

Returns the data corrections you have submitted, with their review status.

GET/v1/me/reports

  • stringheaderrequired

    Your API key. Authorization: Bearer <key> is accepted in its place.

  • integerdefault1

    Page number, from 1 to 10,000

    Range
    1 – 10000
    Example
  • integerdefault20

    Items per page (max 100)

    Range
    1 – 100
    Example

  • DataReport[]

    A community-submitted data correction against a firearm.

  • string

    Opaque report id.

  • string

    Slug of the firearm this row belongs to.

  • string

    Which part of the record the report is about.

  • ReportIssueType

    What a data report says is wrong.

  • string

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

  • string | null

    What the reporter believes the value should be.

  • string[]

    Pages the reporter cited in support.

  • ReportStatus

    Lifecycle of a data report.

  • string

    When the record was first added, YYYY-MM-DD HH:MM:SS in UTC.

  • string | null

    When staff reviewed it, or null while it is pending.

  • number

    Current page number

  • number

    Items per page

  • number

    Total matching records (Builder and above)

  • 400VALIDATION_ERRORValidation error
  • 401UNAUTHORIZEDAPI key required
  • 403FORBIDDENValid key, not permitted
  • 429RATE_LIMITEDRate limit exceeded
  • 500INTERNAL_ERRORUnexpected server error

Reports are sorted by created_at descending (most recent first).

Filter by status=pending to see reports still awaiting review.

Minimum tier
Explorer+
Monthly quota
200/mo
Rate limit
10/min
Daily cap
50

Figures shown are for this endpoint's minimum tier. Higher tiers raise every limit.

Auth RequiredExplorer+

Flags incorrect, missing, or outdated specification data on a firearm. Reports are reviewed by staff before the catalog changes.

POST/v1/me/reports

  • stringheaderrequired

    Your API key. Authorization: Bearer <key> is accepted in its place.

  • stringrequired

    Slug of the firearm this row belongs to.

  • stringrequired

    Which part of the record the report is about.

  • stringrequired

    What kind of problem: incorrect, missing, outdated.

  • stringrequired

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

  • string

    What the reporter believes the value should be.

  • string[]

    Pages the reporter cited in support.

  • DataReport

    A community-submitted data correction against a firearm.

  • string

    Opaque report id.

  • string

    Slug of the firearm this row belongs to.

  • string

    Which part of the record the report is about.

  • ReportIssueType

    What a data report says is wrong.

  • string

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

  • string | null

    What the reporter believes the value should be.

  • string[]

    Pages the reporter cited in support.

  • ReportStatus

    Lifecycle of a data report.

  • string

    When the record was first added, YYYY-MM-DD HH:MM:SS in UTC.

  • string | null

    When staff reviewed it, or null while it is pending.

  • 400VALIDATION_ERRORValidation error
  • 401UNAUTHORIZEDAPI key required
  • 403FORBIDDENValid key, not permitted
  • 413PAYLOAD_TOO_LARGERequest body too large
  • 429RATE_LIMITEDRate limit exceeded
  • 500INTERNAL_ERRORUnexpected server error

Valid issueType values are: incorrect, missing, outdated.

Valid section values are: game-stats, specs, ballistics, barrel, materials, operating, calibers, users, description.

The description field must be at least 10 characters.

Reports are reviewed within 5–7 business days.

Minimum tier
Explorer+
Monthly quota
200/mo
Rate limit
10/min
Daily cap
50

Figures shown are for this endpoint's minimum tier. Higher tiers raise every limit.