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 Settlement Reports API

The Settlement Reports API from Silverflow — 1 operation(s) for settlement reports.

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

Tagged areas include Settlement Reports. 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 1 operation across 1 path, and defines 26 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.

1 operations 1 paths 26 schemas 1 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 Settlement Reports 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 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Settlement Reports 1
POST
/reports/settlementDetails
Create Settlement Details Report [EXPERIMENTAL]
createSettlementDetailsReport body → 201400401403429

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are CreateSettlementDetailsReportResponse (9 properties), InputValidationError (6 properties), NotAuthorizedErrorDetails (5 properties), InvalidReportNameErrorDetails (5 properties). Each schema is shown below with its type and property counts.

openapi_components-schemas-ValidationError
object
3 properties 3 required
SettlementDetailsReportMimeType
string
The mime-type in which the SettlementDetails report is available.
errorTitle
string
A short, human-readable summary of the problem type. It does not change from occurrence to occurrence of the error.
SettlementDetailsReportName
string
The name of the report.
errorInstance
string
A reference that identifies the specific occurrence of the error. The instance is unique for every error.
CreateSettlementDetailsReportRequest
object
Create SettlementDetails Report
4 properties 2 required
components-schemas-reference
string
Unique ID used to identify a report.
SettlementDetailsReportParameters
errorStatus
integer
The HTTP status code generated by the origin server for this occurrence of the problem.
InputValidationError
object
6 properties 6 required
SettlementDetailsReportByNftKeyParameters
object
The query parameters used for a report.
1 property 1 required
InvalidDateRangeErrorDetails
object
5 properties 5 required
distributionKey
string
Uniquely identifies a distribution object
errorDetail
string
A human readable explanation specific to this occurrence of the problem.
NotAuthorizedErrorDetails
object
5 properties 5 required
AgentKey
string
Uniquely identifies an Agent
openapi_components-schemas-ProblemDetail-2
object
The 'problem detail' object relays detailed information about the error that occurred. It is defined by [RFC 7807 - Problem Details for HTTP APIs](https://tool…
5 properties
createReportStatus
string
The status of the report.
CreateSettlementDetailsReportResponse
object
9 properties 7 required
errorType
string
A relative URI reference, this property can be used to perform automated error handling.
SettlementDetailsReportByCreatedTimeParameters
object
The query parameters used for a report.
2 properties 1 required
reportKey
string
Uniquely identifies a report object
distributions
array
The distribution objects' keys. If passed, the report will be distributed when generation is completed.
networkFundsTransferKey
string
Uniquely identifies a Networks Funds Transfer
InvalidReportNameErrorDetails
object
5 properties 5 required
openapi_components-schemas-created-2
string
The date and time this object was created

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

silverflow-settlement-reports-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 Settlement Reports 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.