GET /feed.json
The published atom changes as a JSON Feed, narrowed by the query string.
GET /feed.jsonA JSON Feed 1.1 document (https://jsonfeed.org/version/1.1), one item per atom change of every release this service has published that the query string admits. The format is the JSON Feed specification’s and is not restated by this project; what is this project’s is the _openregs member the spec reserves for extensions, which carries the change and the release it came from so a reader does not have to parse the prose back out of content_text.
Every date in the document is the release’s own build stamp, which is the committer date of the commit it was compiled from. No clock is read, so two services that have published the same releases render identical bytes.
A release that was built but never announced to this service is not in the feed: a feed is a log of publications and not a walk of a checkout.
Authentication
Section titled “Authentication”No authentication requirement is stated for this operation.
Parameters
Section titled “Parameters”| Parameter | |
|---|---|
jurisdiction | Only changes whose jurisdiction is one of the values given. Repeat the key to mean ‘or’; leave it out to match every jurisdiction. (in query) |
regime | Only changes whose regime is one of the values given. Repeat the key to mean ‘or’; leave it out to match every regime. (in query) |
topic | Only changes whose topic is one of the values given. Repeat the key to mean ‘or’; leave it out to match every topic. (in query) |
entity_type | Only changes whose entity_type is one of the values given. Repeat the key to mean ‘or’; leave it out to match every entity_type. (in query) |
Responses
Section titled “Responses”The matching changes, newest release first.
application/feed+json — JsonFeed
the query names a key that is not one of the four filter dimensions. An unknown dimension is refused rather than ignored, because a subscriber who misspells one and is quietly sent everything has been widened without being told
application/json — Error
Rendered from openregs/openregs@f3a2d10:docs/reference/feed-openapi.json