Silverflow Fraud Notifications API
Fraud Notifications are created by the schemes when a fraudulent transaction is reported to them. The Fraud Notification endpoints, allow to obtain more information about a Fraud Notification, including the reported Fraud Type code(s) and the related charge.
Silverflow Fraud Notifications API is one of 50 APIs that Silverflow publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Fraud Notifications. 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 2 operations across 2 paths, and defines 33 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Silverflow Fraud Notifications 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 2
Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.
Fraud Notifications are created by the schemes when a fraudulent transaction is reported to them. The Fraud Notification endpoints, allow to obtain more information about a Fraud…
Schemas 33
The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are FraudNotification (15 properties), fraud-notifications_chargeInfo (7 properties), schemas-ProblemDetail (5 properties), cardInfo (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Silverflow 12
Other APIs Silverflow publishes across the network.
This is an independent, third-party profile of Silverflow Fraud Notifications 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.