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 containers API

**Container** entities represent publication venues like journals, # TAGLINEconference proceedings, book series, or blogs. They group publications # TAGLINE("releases"). # 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[Container Entity Reference](https://guide.fatcat.wiki/entity_container.html). # TAGLINE

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

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

This API exposes 11 operations across 10 paths, and defines 10 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.

11 operations 10 paths 10 schemas 2 DELETE6 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 containers 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 11

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

containers 11

Container entities represent publication venues like journals, TAGLINE conference proceedings, book series, or blogs. They group publications TAGLINE ("releases"). TAGLINE See the…

POST
/editgroup/{editgroup_id}/container
Create a single Container entity as part of an existing editgroup. Editgroup must be mutable (aka, not accepted) and editor must have permission (aka, have created the editgroup or have admin role).
create_container 2 params → 400404500401403201
POST
/editgroup/auto/container/batch
Create a set of Container 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…
create_container_auto_batch 1 param → 400404500401403201
GET
/container/{ident}
Fetches a single container entity from the catalog.
get_container 3 params → 400404500200
PUT
/editgroup/{editgroup_id}/container/{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_container 3 params → 400404500401403200
DELETE
/editgroup/{editgroup_id}/container/{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 deletecontaineredit.
delete_container 2 params → 400404500401403200
GET
/container/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_container_revision 3 params → 400404500200
GET
/container/{ident}/history
Fetches the history of accepted edits (changelog entries) for a specific entity fatcat identifier.
get_container_history 2 params → 400404500200
GET
/container/{ident}/redirects
Returns the set of entity identifiers which currently redirect to this identifier.
get_container_redirects 1 param → 400404500200
GET
/container/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_container 7 params → 400404500200
GET
/container/edit/{edit_id}
Returns the entity edit object with the given identifier. This method is expected to be used rarely.
get_container_edit 1 param → 400404500200
DELETE
/editgroup/{editgroup_id}/container/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_container_edit 2 params → 400404500401403200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are container_entity (14 properties), editgroup (10 properties), entity_edit (7 properties), editgroup_annotation (7 properties). Each schema is shown below with its type and property counts.

changelog_entry
object
4 properties 3 required
container_auto_batch
object
2 properties 2 required
entity_edit
object
7 properties 3 required
error_response
object
3 properties 3 required
container_entity
object
14 properties
editgroup
object
10 properties
entity_history_entry
object
3 properties 3 required
success
object
2 properties 2 required
editgroup_annotation
object
7 properties
editor
object
5 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fatcat-containers-api-openapi.yml Raw ↑

Other APIs Fatcat publishes across the network.

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

This is an independent, third-party profile of Fatcat containers 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.