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

**File** entities represent unique digital files which are full # TAGLINEmanifestations of specific releases (publications), such as fulltext PDF # TAGLINEfiles, JATS XML documents, or video files. File entities also include a # TAGLINEset of locations where they can be found on the public web. # 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[File Entity Reference](https://guide.fatcat.wiki/entity_file.html). # TAGLINE

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

Tagged areas include File. 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 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.

11 operations 10 paths 24 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 files 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.

files 11

File entities represent unique digital files which are full TAGLINE manifestations of specific releases (publications), such as fulltext PDF TAGLINE files, JATS XML documents, or…

POST
/editgroup/{editgroup_id}/file
create_file 2 params → 400404500401403201
POST
/editgroup/auto/file/batch
create_file_auto_batch 1 param → 400404500401403201
GET
/file/{ident}
get_file 3 params → 400404500200
PUT
/editgroup/{editgroup_id}/file/{ident}
update_file 3 params → 400404500401403200
DELETE
/editgroup/{editgroup_id}/file/{ident}
delete_file 2 params → 400404500401403200
GET
/file/rev/{rev_id}
get_file_revision 3 params → 400404500200
GET
/file/{ident}/history
get_file_history 2 params → 400404500200
GET
/file/{ident}/redirects
get_file_redirects 1 param → 400404500200
GET
/file/lookup
lookup_file 5 params → 400404500200
GET
/file/edit/{edit_id}
get_file_edit 1 param → 400404500200
DELETE
/editgroup/{editgroup_id}/file/edit/{edit_id}
delete_file_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), release_ext_ids (14 properties), container_entity (14 properties). Each schema is shown below with its type and property counts.

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
file_auto_batch
object
2 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-files-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 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 files 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.