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 Reconciliation Events API

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

Tagged areas include Reconciliation Events. 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 0 operations across 0 paths, and defines 11 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.

0 operations 0 paths 11 schemas

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

Authentication & Security 3

Silverflow Reconciliation Events 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…

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are PublicCloudEvent (6 properties), NftCompletedNotificationVersion1_0 (6 properties), NftCompletedNotificationDataVersion1_0 (2 properties). Each schema is shown below with its type and property counts.

openapi_components-schemas-version-3
string
The version of the spec.
source
string
Source system of the event.
NftCompletedNotificationVersion1_0
object
6 properties 1 required
common_agentKey
string
Uniquely identifies an Agent.
time
string
Date and time when the event was sent.
eventId
string
Uniquely identifies an event.
NftCompletedNotificationDataVersion1_0
object
2 properties 2 required
dataContentType
string
The content type of the event.
schemas-networkFundsTransferKey
string
Uniquely identifies a Network Funds Transfer
dataschema
string
The event schema with the data version of the event.
PublicCloudEvent
object
6 properties 10 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

silverflow-reconciliation-events-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 Reconciliation Events 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.