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

Silverflow File Subscriptions API

Subscribe to raw files from the card networks.

Silverflow File Subscriptions API is one of 50 APIs that Silverflow publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include File Subscriptions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 4 operations across 2 paths, and defines 25 schemas. It is described by OpenAPI 3.2.0, at version 1.417.0.

Requests are made against 3 base URLs: https://eu-west-1.api.silverflow.com/v1, https://us-east-2.api.silverflow.com/v1, https://eu-west-1.api-sbx.silverflow.com/v1.

4 operations 2 paths 25 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.417.0
Base URL
https://eu-west-1.api.silverflow.com/v1
Authentication
HTTP Basic, HTTP Bearer, API Key
License
Commercial
Resource Areas
1

Authentication & Security 3

Silverflow File Subscriptions API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (ApiKey). It accepts HTTP bearer tokens (JWT) (BearerToken). An API key is passed in the header as - (MutualTLS). By default, every request must be authenticated.

  • ApiKey — The primary method of authenticating to the Silverflow API is through API keys. API keys can be created by calling the [createApiKey](operation/createApiKey) e…
  • BearerToken — Bearer tokens are temporary security credentials that can be used to authorize 'third parties' (bearers) access to the Silverflow API on behalf of the agent. T…
  • MutualTLS — The client must set up mTLS connection with a valid X.509 client certificate signed by a customer-provided CA (certificate authority) that is registered to a s…

Paths & Operations 4

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

File Subscriptions 4

Subscribe to raw files from the card networks.

GET
/fileSubscription
List File Subscriptions [EXPERIMENTAL]
ListFileSubscriptions → 200400401403500
POST
/fileSubscription
Create File Subscription [EXPERIMENTAL]
CreateFileSubscription body → 201400401403409500
PUT
/fileSubscription/{subscriptionKey}
Update File Subscription [EXPERIMENTAL]
PutFileSubscription 1 param body → 200400401403404409500
DELETE
/fileSubscription/{subscriptionKey}
Delete File Subscription [EXPERIMENTAL]
DeleteFileSubscription 1 param → 204400401403404500

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are schemas-InvalidInputError (6 properties), schemas-InternalServerError (5 properties), ConflictError (5 properties), NotFoundError (5 properties). Each schema is shown below with its type and property counts.

DistributionKey
string
Key of the distribution where files will be sent.
ListFileSubscriptionsResponse
object
1 property 1 required
BadRequestError
object
schemas-InternalServerError
object
5 properties 5 required
errorTitle
string
A short, human-readable summary of the problem type. It does not change from occurrence to occurrence of the error.
schemas-InvalidRequestError
object
5 properties 5 required
FileSubscription
object
5 properties 5 required
errorInstance
string
A reference that identifies the specific occurrence of the error. The instance is unique for every error.
schemas-UnauthorizedError
object
5 properties 5 required
NotFoundError
object
5 properties 5 required
CreateFileSubscriptionRequest
object
4 properties 4 required
SubscriptionKey
string
The key of a subscription.
validationError
object
3 properties 3 required
AcquirerReferences
array
Network-specific references for file routing. The type of reference required depends on the card network: | Card Network | Required Value | BIN Object Field |…
schemas-InvalidInputError
object
6 properties 6 required
errorDetail
string
A human readable explanation specific to this occurrence of the problem.
UpdateFileSubscriptionRequest
object
3 properties 3 required
validationErrors
array
components-schemas-errorStatus
integer
The HTTP status code generated by the origin server for this occurrence of the problem.
FileTypes
array
List of card network file types to subscribe to. Each file type represents a specific format of raw data files from different card networks.
components-schemas-AgentKey
string
The key of an agent.
errorType
string
A relative URI reference, this property can be used to perform automated error handling.
components-schemas-ForbiddenError
object
5 properties 5 required
ConflictError
object
5 properties 5 required
PublicKey
string
ASCII-armored PGP public key for file encryption. Supported algorithms: RSA (2048+ bits), Ed25519, ECDSA.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

silverflow-file-subscriptions-api-openapi.yml Raw ↑

Other APIs Silverflow publishes across the network.

Silverflow 3DS Authentication API
Silverflow Agents API
Silverflow AMMF Submission Events API
Silverflow API Keys API
Silverflow BEP Authentication API
Silverflow Bins API
Silverflow Card Info API
Silverflow Card Management API
Silverflow Card Network Reports API
Silverflow Charge Actions API
Silverflow Charges Events API
Silverflow Charges Reports API
Where this information came from

This is an independent, third-party profile of Silverflow File Subscriptions 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.