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

SnapAPI Storage API

File storage — list, retrieve, delete stored files; configure custom S3

SnapAPI Storage API is one of 13 APIs that SnapAPI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Storage. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 9 operations across 6 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.snapapi.pics.

9 operations 6 paths 1 schemas 2 DELETE4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.snapapi.pics
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

SnapAPI Storage API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Your SnapAPI API key
  • BearerAuth — JWT access token obtained from /auth/login or /auth/refresh

Paths & Operations 9

Across 6 paths, the API surfaces 9 operations — 2 DELETE, 4 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Storage 9

File storage — list, retrieve, delete stored files; configure custom S3

GET
/storage/overview
Storage Overview
getStorageOverview → 200
POST
/storage/vault-preference
Set Vault Preference
setVaultPreference body → 200403
GET
/storage/files
List Stored Files
listStoredFiles 3 params → 200
GET
/storage/files/{id}
Get Stored File
getStoredFile 3 params → 200302401404
DELETE
/storage/files/{id}
Delete Stored File
deleteStoredFile 1 param → 200404
GET
/storage/user-s3
Get S3 Configuration
getUserS3Config → 200
POST
/storage/user-s3
Save S3 Configuration
saveUserS3Config body → 200400
DELETE
/storage/user-s3
Delete S3 Configuration
deleteUserS3Config → 200
POST
/storage/user-s3/test
Test S3 Connection
testUserS3Connection body → 200400

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is StoredFile (10 properties). Each schema is shown below with its type and property counts.

StoredFile
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

snapapi-pics-storage-api-openapi.yml Raw ↑

Other APIs SnapAPI publishes across the network.

SnapAPI Analyze API
SnapAPI Auth API
SnapAPI Dashboard API
SnapAPI Extract API
SnapAPI Health API
SnapAPI PDF API
SnapAPI Scrape API
SnapAPI Screenshot API
SnapAPI Usage API
SnapAPI Utilities API
SnapAPI Video API
SnapAPI Webhooks API
Where this information came from

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