How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Fatcat releases API

**Release** entities represent specific published versions of a research # TAGLINEwork, such as a pre-print, a journal article, a book (or chapter), or a # TAGLINEscholarly blog post. Releases are always grouped together under Works; # TAGLINEthey may be published in a specific Container; they may have known # TAGLINECreators; and there may exist known File/Fileset/WebCapture digital copies # TAGLINEof the release. # TAGLINESee the "Catalog Style Guide" section of the guide for details and # TAGLINEsemantics of what should be included in specific entity fields. # TAGLINESpecifically, the # TAGLINE[Release Entity Reference](https://guide.fatcat.wiki/entity_release.html). # TAGLINE

Fatcat releases API is one of 11 APIs that Fatcat publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Releases. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a GitHub repository, and rate-limit docs.

This API exposes 14 operations across 13 paths, and defines 24 schemas. It is described by OpenAPI 2.0, at version 0.5.0.

Requests are made against the base URL https://api.fatcat.wiki/v0.

14 operations 13 paths 24 schemas 2 DELETE9 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
0.5.0
Base URL
https://api.fatcat.wiki/v0
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Fatcat releases API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

  • Bearer — The only current API authentication mechanism is HTTP bearer authentication using the Authorization HTTP header. The header should be formatted as the string "…

Paths & Operations 14

Across 13 paths, the API surfaces 14 operations — 2 DELETE, 9 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

releases 14

Release entities represent specific published versions of a research TAGLINE work, such as a pre-print, a journal article, a book (or chapter), or a TAGLINE scholarly blog post. R…

POST
/editgroup/{editgroup_id}/release
Create a single Release entity as part of an existing editgroup. If the workid field is not set, a work entity will be created automatically and this field set pointing to the new work. Editgroup mus…
create_release 2 params → 400404500401403201
POST
/editgroup/auto/release/batch
Create a set of Release entities as part of a new editgroup, and accept that editgroup in the same atomic request. This method is mostly useful for bulk import of new entities by carefully written bo…
create_release_auto_batch 1 param → 400404500401403201
GET
/release/{ident}
Fetches a single Release entity from the catalog.
get_release 3 params → 400404500200
PUT
/editgroup/{editgroup_id}/release/{ident}
Updates an existing entity as part of a specific (existing) editgroup. The editgroup must be open for updates (aka, not accepted/merged), and the editor making the request must have permissions (aka,…
update_release 3 params → 400404500401403200
DELETE
/editgroup/{editgroup_id}/release/{ident}
Creates a new "deletion" edit for a specific entity as part of an existing editgroup. This is not the method to use to remove an edit from an editgroup; for that use deletereleaseedit.
delete_release 2 params → 400404500401403200
GET
/release/rev/{rev_id}
Fetches a specific entity revision. Note that the returned revision will not be associated with any particular fatcat identifier (even if one or more identifiers do currently point to this revision).…
get_release_revision 3 params → 400404500200
GET
/release/{ident}/history
Fetches the history of accepted edits (changelog entries) for a specific entity fatcat identifier.
get_release_history 2 params → 400404500200
GET
/release/{ident}/files
Returns the set of File entities that have a releaseid pointing to this release entity.
get_release_files 2 params → 400404500200
GET
/release/{ident}/filesets
Returns the set of Fileset entities that have a releaseid pointing to this release entity.
get_release_filesets 2 params → 400404500200
GET
/release/{ident}/webcaptures
Returns the set of Web Capture entities that have a releaseid pointing to this release entity.
get_release_webcaptures 2 params → 400404500200
GET
/release/{ident}/redirects
Returns the set of entity identifiers which currently redirect to this identifier.
get_release_redirects 1 param → 400404500200
GET
/release/lookup
Looks for an active entity with the given external identifier. If any such entity is found, returns a single complete entity. If multiple entities have the same external identifier, this is considere…
lookup_release 16 params → 400404500200
GET
/release/edit/{edit_id}
Returns the entity edit object with the given identifier. This method is expected to be used rarely.
get_release_edit 1 param → 400404500200
DELETE
/editgroup/{editgroup_id}/release/edit/{edit_id}
Removes a single edit from the specified editgroup. The editgroup must be mutable (aka, not accepted/merged), and the editor making this request must have permission (aka, have created the editgroup…
delete_release_edit 2 params → 400404500401403200

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are release_entity (34 properties), file_entity (15 properties), container_entity (14 properties), release_ext_ids (14 properties). Each schema is shown below with its type and property counts.

release_auto_batch
object
2 properties 2 required
release_ref
object
8 properties
container_entity
object
14 properties
editor
object
5 properties 1 required
webcapture_url
object
2 properties 2 required
file_entity
object
15 properties
file_url
object
2 properties 2 required
creator_entity
object
11 properties
entity_edit
object
7 properties 3 required
error_response
object
3 properties 3 required
fileset_entity
object
11 properties
release_contrib
object
9 properties
webcapture_cdx_line
object
8 properties 4 required
release_ext_ids
object
14 properties
fileset_file
object
7 properties 2 required
release_abstract
object
4 properties
editgroup
object
10 properties
fileset_url
object
2 properties 2 required
release_entity
object
34 properties 1 required
changelog_entry
object
4 properties 3 required
webcapture_entity
object
13 properties
entity_history_entry
object
3 properties 3 required
success
object
2 properties 2 required
editgroup_annotation
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fatcat-releases-api-openapi.yml Raw ↑

Other APIs Fatcat publishes across the network.

Fatcat auth API
Fatcat changelog API
Fatcat containers API
Fatcat creators API
Fatcat editgroups API
Fatcat editors API
Fatcat files API
Fatcat filesets API
Fatcat webcaptures API
Fatcat works API
Where this information came from

This is an independent, third-party profile of Fatcat releases API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.