The manifest of a build

Written last by every build: when it ran, the version of the API's shape and of the calculations, each source with its version, date and age in days, and one sha256 for each family of files. The sha256 of every file under /api/v1/ is in /api/v1/sha256sums.txt.gz, in the format of sha256sum. Give built_at and calculation.version beside a figure to cite the exact state it comes from. The list holds every file under /api/v1/ but the manifest and the list. A family's sha256 is the digest of its lines of the list, so it is the same on two nights whose files of that family did not change.

get/manifest.json

Request

Base URL: https://tickerinside.com/api/v1
URL: https://tickerinside.com/api/v1/manifest.json
Auth: none required

Response

The file. The example is a real answer, shortened: long lists and maps keep their first entries.

manifest_versionnumber nullable required

The version of this file's own shape: 1. A field added keeps it.

built_atstring nullable required

When the build that wrote every file listed here ran, in UTC. Give it beside a figure to cite the exact state it comes from.

build_datestring nullable required

The day of built_at.

familiesobject required

One entry per family of files, keyed by a directory followed by a slash (fund/) or by the name of a file at the top (index.json): files, the number of files, bytes, their size, and sha256, the digest of the family's lines of the list, in their order, each ending with a newline.

methods_urlstring nullable required

The methods of the computed figures, /api/v1/methods.json.

contractstring nullable required

The data contract this file belongs to: /contract/.

docsstring nullable required

Where this file is documented.

licensestring nullable required

The licence the file is published under.

attributionstring nullable required

How to credit the data: a link to this file where the medium allows one, the name where it does not.

Changes

No recorded changes to this operation across all 2 revisions of this API.