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 Event Subscriptions API

Silverflow Event 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 Event 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 5 operations across 2 paths, and defines 19 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 19 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 Event 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 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.

Event Subscriptions 5
GET
/eventSubscriptions
List Event Subscriptions
getEventSubscriptions 3 params → 200400401403429
POST
/eventSubscriptions
Create Event Subscription
createEventSubscription body → 201400401403429
GET
/eventSubscriptions/{eventSubscriptionKey}
Get Event Subscription
getSubscription 1 param → 200400401403404412429
DELETE
/eventSubscriptions/{eventSubscriptionKey}
Archive Event Subscription
deleteEventSubscription 1 param → 204401403404412429
PATCH
/eventSubscriptions/{eventSubscriptionKey}
Update Event Subscription
updateEventSubscription 1 param body → 200400401403404412429

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are EventSubscription (10 properties), ProblemDetail (5 properties), PreconditionFailedProblemDetail (5 properties), EventSubscriptionCreate (3 properties). Each schema is shown below with its type and property counts.

Page
object
2 properties
eventSubscriptionKey
string
ProblemDetail
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
FreeTextField
string
offsetToken
string
created
string
The date and time this object was created
PreconditionFailedProblemDetail
object
5 properties 5 required
EventSubscriptionCreate
object
3 properties 2 required
eventSubscriptionStatus
string
The status of the Event Subscription
EventSubscriptionsPage
url
string
A valid URL
version
integer
The version of this object
EventSubscriptionMergeUpdate
object
2 properties
eventSourceRequest
string
lastModified
string
The date and time this object was last modified
moreItems
boolean
agentKey
string
Uniquely identifies an Agent
BadRequestProblemDetail
A 'problem detail' object for Bad Request (400) errors. Extends the base ProblemDetail with a validationErrors array that provides detailed information about v…
EventSubscription
object
10 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

silverflow-event-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 Event 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.