Content

Optional. Without a key this endpoint answers under the public policy; a key raises your limits and unlocks plan-gated fields. Authorization: Bearer <key> is accepted in its place.

Page number, from 1 to 10,000

Range

1 – 10000

Example

1

Items per page (max 100)

Range

1 – 100

Example

20

Filter by entry category

Accepts

featureimprovementbugfixdatabreaking

Max length

60

One page of results

Slug of the entry, taken from the file it was authored in.

Entry headline.

Entry body, in Markdown.

What kind of change: feature, improvement, bugfix, data, breaking.

When it was published, ISO 8601.

Integer flag, 1 when the entry is live. The public feed only returns published entries, so this is 1 on every row a consumer sees.

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

When it last changed, ISO 8601.

Current page number

Items per page

Total matching records (Builder and above)

Optional. Without a key this endpoint answers under the public policy; a key raises your limits and unlocks plan-gated fields. Authorization: Bearer <key> is accepted in its place.

Changelog entry id

Example

039-3d-models-line-art-and-a-phantom-firearm

The response payload

Slug of the entry, taken from the file it was authored in.

Entry headline.

Entry body, in Markdown.

What kind of change: feature, improvement, bugfix, data, breaking.

When it was published, ISO 8601.

Integer flag, 1 when the entry is live. The public feed only returns published entries, so this is 1 on every row a consumer sees.

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

When it last changed, ISO 8601.

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

Page number, from 1 to 10,000

Range

1 – 10000

Example

1

Items per page (max 100)

Range

1 – 100

Example

20

Entries on or after this ISO date or UTC instant, or after this seq

Max length

40

Example

2026-10-01

Entries on or before this ISO date (the whole day) or UTC instant

Max length

40

Only changes to this kind of record

Accepts

firearmmanufacturercalibercatalog

Only this kind of change

Accepts

createdupdateddeletedmergedresynced

Only changes to this manufacturer's firearms, or to the manufacturer itself

Max length

100

Example

glock

Newest first, or oldest first for reading forward from a seq

Accepts

ascdesc

Example

desc

One change to the catalogue.

The entry's position in the feed. Increases with every entry; store the highest you have read and pass it as since to continue from there.

What kind of record changed. catalog is a resynced entry, which belongs to no one record.

The record's id, for GET /v1/{entity}s/{id}. Null on a resynced entry.

created, updated, deleted, merged (folded into the record named by mergedInto), or resynced: too many records changed at once to list, so re-read what you hold.

When the change was recorded, ISO 8601 UTC.

The record's version after the change. Null for a removal.

For merged, the id of the record it was folded into. An old id also answers with that record.

The record's name when it changed, kept after it is removed.

The maker of a firearm, or the manufacturer itself, when it changed.

Manufacturer id.

Manufacturer name.

For updated, the fields that moved. Null when the change happened before an earlier version of the record had been kept, so it is known to have changed and no more.

The field as the record names it; a nested field is a dotted path.

The value before the change. Null when the field was empty.

The value after the change. Null when the field was emptied.

Present and true when a long value was cut to its start; the record holds the rest.

Present and true when your plan does not include this field: it moved, and before and after are null.

For resynced, how many records the rewrite touched.

A firearm's current pictures, for showing the entry. Empty for a removed record and for other kinds of record.

Image id.

Where to fetch it.

What kind of picture it is.

Alternative text.

Width in pixels.

Height in pixels.

The quality tasks behind the change, at most three, newest first: the task on the same record and field whose fix or accepted answer closed it, up to two days after or sixty days before the change. Empty when none is linked.

The task's number, for GET /v1/data/tasks/{id}.

The task's key.

What kind of task it is.

The quality check that raised it.

The check's name, readable.

What the check found on this record, in one sentence.

fixed where the record was corrected so the check no longer finds it; otherwise how an accepted answer ended.

When the task closed.

What the research found: the value a source states and the page, or why the value was removed. Null when nothing was recorded, or when the task is withheld.

Present and true when every field the task concerns is above your plan: finding is null and why is the check's rule.

The task's public page.

Current page number

Items per page

Total matching records (Builder and above)

Optional. Without a key this endpoint answers under the public policy; a key raises your limits and unlocks plan-gated fields. Authorization: Bearer <key> is accepted in its place.

Page number, from 1 to 10,000

Range

1 – 10000

Example

1

Items per page (max 100)

Range

1 – 100

Example

20

Filter by post category

Max length

60

Example

guides

A published post. Both endpoints serve the stored row; body is markdown.

Opaque post id. A string, not a number: posts are keyed like every other authored record here.

URL-safe slug, and what /v1/blog/{slug} addresses.

Post headline.

One-line description, for a card or a feed. Null where the author wrote none.

The post itself, as markdown.

Path of the hero image on the assets CDN, or null. Prefix it with the assets host to fetch.

What the hero image shows, as alt text. Null where the post has no hero or none was written.

Editorial category, e.g. guides. Null where the post has none.

Always published on these endpoints: a draft is not served publicly.

When the post was published, which is what the list orders by. Null on a post never given a date.

When the post was first written, YYYY-MM-DD HH:MM:SS in UTC. Not the publication date: postedAt is.

When the post was last edited, YYYY-MM-DD HH:MM:SS in UTC.

Who wrote the post: the display name on the account that created it, never its address. Null when that account has no display name, and the post is then attributed to the publisher.

The author's display name, as set on their GunSpec account.

URL segment of the author's page on the blog, made from their display name.

Which avatar style the author chose on their account.

Seed the avatar is drawn from. Stable per author, and not their account id.

Current page number

Items per page

Total matching records (Builder and above)

Optional. Without a key this endpoint answers under the public policy; a key raises your limits and unlocks plan-gated fields. Authorization: Bearer <key> is accepted in its place.

Blog post slug

Accepts

a lowercase slug: letters, digits and hyphens

Example

complete-guide-firearm-calibers-for-developers

The response payload.

A published post. Both endpoints serve the stored row; body is markdown.

Opaque post id. A string, not a number: posts are keyed like every other authored record here.

URL-safe slug, and what /v1/blog/{slug} addresses.

Post headline.

One-line description, for a card or a feed. Null where the author wrote none.

The post itself, as markdown.

Path of the hero image on the assets CDN, or null. Prefix it with the assets host to fetch.

What the hero image shows, as alt text. Null where the post has no hero or none was written.

Editorial category, e.g. guides. Null where the post has none.

Always published on these endpoints: a draft is not served publicly.

When the post was published, which is what the list orders by. Null on a post never given a date.

When the post was first written, YYYY-MM-DD HH:MM:SS in UTC. Not the publication date: postedAt is.

When the post was last edited, YYYY-MM-DD HH:MM:SS in UTC.

Optional. Without a key this endpoint answers under the public policy; a key raises your limits and unlocks plan-gated fields. Authorization: Bearer <key> is accepted in its place.

The response payload.

Published notices inside their display window, best first: highest priority, then newest.

Row id of the notice. The website keys its dismissal on this, so a new notice is seen even by a reader who dismissed the last one.

Short label shown before the message.

The sentence shown in the banner.

A second line, shown under the highlight where one is set.

How prominently a site notice is shown.

Text of the call to action, or null when the banner has none.

Where the call to action goes.

Higher sorts first. Ties break on newest.

When the notice becomes visible. Null means immediately.

When it stops being shown. This is why notices are rows rather than copy: an end date is the only version of "take this down later" that does not rely on somebody remembering.