Files

1 file · 514 KB · verbatim copies of public vendor files

File	Format	Size	Download
`keepeek_swagger_rest-api-v1.json`	Swagger / OpenAPI	514 KB	Download

README — provenance

DAM Wiki downloaded this file on 2026-09-30 from a public vendor URL (no login needed). It is an unmodified copy, exactly as the vendor serves it.

File	Format	Version	Public source URL
`keepeek_swagger_rest-api-v1.json`	Swagger 2.0 (JSON), title "Keepeek REST API"	`info.version` = 1 (API representation version); doc instance reported release 4.146.0 on GET`/api` the same day	https://test-doc.keepeek.com/api/doc/swagger.json

Size 526,397 bytes; SHA-256 8f89bc1f1f99cb75b5ef01139703bc449f14e0d4dde3be12a1daecc6ee8fe81d.
Rendered by the Swagger UI at https://test-doc.keepeek.com/api/doc/ ("Keepeek API Documentation"), which the official help center article "Keepeek - REST API reference" links to (https://support.papirfly.com/hc/en-us/articles/24318920795292-Keepeek-REST-API-reference). test-doc.keepeek.com is Keepeek's own documentation instance.
Content: 266 paths, 378 operations, 451 definitions, 35 tags. basePath is /, no host and no securityDefinitions — paths are absolute from the instance root (/api/dam/…, /api/public/…, /api/share/{tokenId}/…, /api/stat/…, /api/geo/…, /api/recognition/…). Operation lists under several tags overlap (e.g. download / api / public).
The Swagger UI loads the spec from the host-relative path /api/doc/swagger.json, so it reflects the release of the instance serving it (whether every customer instance exposes it too was not checked). Methods: 227 GET, 65 POST, 60 DELETE, 26 PUT. DAM Wiki refreshes these copies when the release returned by GEThttps://test-doc.keepeek.com/api changes materially.
Quick inventory: python -c "import json;s=json.load(open('keepeek_swagger_rest-api-v1.json',encoding='utf-8'));print(len(s['paths']))"

API_Helpdesk.postman_collection.json (Postman v2.1, attachment of help article 24319118927388, https://support.papirfly.com/hc/article_attachments/24319122607132). It is public, but it contains hard-coded demo credentials in request auth blocks and a hostname that looks like a customer instance. Per wiki rule 4 (no credentials, no customer tenant names) it is neither copied nor quoted; its path inventory was only used to cross-check the Swagger file.