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

The Distributions API from Silverflow — 2 operation(s) for distributions.

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

Tagged areas include Distributions. 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 5 operations across 2 paths, and defines 52 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.

5 operations 2 paths 52 schemas 1 DELETE2 GET1 PATCH1 POST

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 Distributions 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 5

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

Distributions 5
POST
/distributions
Create a Distribution Object
createDistribution body → 201400401403429
GET
/distributions
List Distribution Objects
listDistributions 5 params → 200400401403429
GET
/distributions/{distributionKey}
Get a Distribution Object
getDistribution 1 param → 200400401403404429
PATCH
/distributions/{distributionKey}
Update a Distribution Object
updateDistribution 1 param body → 200400401403404429
DELETE
/distributions/{distributionKey}
Archive a Distribution Object
archiveDistribution 1 param → 204400401403404429

Schemas 52

The contract defines 52 schemas that model the data the API accepts and returns. The most detailed are BaseDistribution (7 properties), schemas-InputValidationError (6 properties), schemas-ForbiddenError (5 properties), NotAuthorizedError (5 properties). Each schema is shown below with its type and property counts.

BaseDistribution
object
A distribution
7 properties 5 required
DistributionNotFoundError
object
5 properties 5 required
openapi_components-schemas-ValidationError
object
3 properties 3 required
SftpDistributionType
string
SFTP distribution type.
host
string
A valid hostname or IP
accountId
string
AWS account ID that owns the S3 bucket. For security reasons, the file is delivered only if the bucket is still owned by this account.
externalId
string
External ID used when assuming the IAM role. Share it only with Silverflow; the role trust policy should require this value.
components-schemas-version
integer
The version of this object
UpdateDistributionRequest
object
2 properties
directory
string
Optional prefix (subdirectory) inside the bucket where the files will be delivered (e.g., reports/daily/).
schemas-ForbiddenError
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.
EmailDistributionTargets
object
The targets of the email distribution.
1 property 1 required
SftpDistributionTargets
object
The targets of the SFTP distribution.
4 properties 3 required
errorInstance
string
A reference that identifies the specific occurrence of the error. The instance is unique for every error.
Distribution
bucketName
string
Name of the AWS S3 bucket where the files will be delivered.
roleArn
string
IAM role ARN that the Silverflow service will assume to access the bucket.
NotAuthorizedError
object
5 properties 5 required
SftpHost
string
The SFTP Host name or IP address.
SftpDirPath
string
The directory path in the SFTP server where the files will be uploaded.
S3DistributionTargets
object
5 properties 5 required
EmailRecipients
object
The Email recipients.
3 properties 1 required
DistributionType
string
The distribution type.
ListDistributionResponse
SftpPort
integer
The SFTP Host port.
CreateEmailDistributionRequest
object
3 properties 2 required
distributionKey
string
Uniquely identifies a distribution object
errorDetail
string
A human readable explanation specific to this occurrence of the problem.
SftpDistribution
object
S3DistributionType
string
S3 distribution type.
schemas-TooManyRequestsError
object
5 properties 5 required
schemas-PageWithMoreItems
object
2 properties
status
string
The status of the object
DistributionReference
string
A reference to the distribution
CreateS3DistributionRequest
object
3 properties 2 required
moreItems
boolean
schemas-AgentKey
string
Uniquely identifies an Agent
CreateDistributionRequest
S3Distribution
object
schemas-email
string
A valid email address
errorType
string
A relative URI reference, this property can be used to perform automated error handling.
openapi_components-schemas-offsetToken
string
schemas-InputValidationError
object
6 properties 6 required
EmailRecipient
string
An email-address.
schemas-errorStatus
integer
The HTTP status code generated by the origin server for this occurrence of the problem.
sftpUsername
string
The SFTP username.
CreateSftpDistributionRequest
object
3 properties 2 required
openapi_components-schemas-created-2
string
The date and time this object was created
openapi_components-schemas-lastModified
string
The date and time this object was last modified
EmailDistribution
EmailDistributionType
string
Email distribution type.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

silverflow-distributions-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 Distributions 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.