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

TreasurySpring Subscriptions API

FTF Subscriptions

TreasurySpring Subscriptions API is one of 13 APIs that TreasurySpring publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Subscription. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version v0.7.3.

Requests are made against 2 base URLs: https://api.treasuryspring.com/api/v1, https://api.sandbox.treasuryspring.com/api/v1.

4 operations 4 paths 10 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v0.7.3
Base URL
https://api.treasuryspring.com/api/v1
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 2

TreasurySpring Subscriptions API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (bearerAuth).

  • basicAuth — Base64-encoded clientid:clientsecret (sent as Authorization: Basic ). Used by the OAuth token-exchange endpoint.
  • bearerAuth — API Key or OAuth access token (sent as Authorization: Bearer ).

Paths & Operations 4

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

Subscriptions 4

FTF Subscriptions

POST
/subscribe
Subscribe to an FTF
post.subscribe 1 param body → 200422
GET
/subscription
Get a list of all subscriptions
get.subscriptions 7 params → 200422
GET
/subscription/{entity_code}/{uid}
Get a single subscription by id
get.subscription 2 params → 200422
POST
/validate
Validate a prospective subscription
post.validate body → 200422

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Indication (29 properties), Subscription (19 properties), SubscriptionBody (7 properties), ValidateBody (6 properties). Each schema is shown below with its type and property counts.

Indication
object
Indication schema.
29 properties 18 required
SubscriptionBody
object
SubscriptionBody schema.
7 properties 3 required
HTTPValidationError
object
1 property
SubscriptionMaturityActionEnum
string
PaginatedSubscriptions
object
PaginatedSubscriptions schema.
2 properties 2 required
PageInfo
object
PageInfo schema.
5 properties 5 required
ValidateBody
object
Body for validating a prospective subscription before committing to it. Mirrors the fields of a subscription request. The endpoint performs a full validation:…
6 properties 3 required
ValidationError
object
3 properties 3 required
SubscriptionStatusEnum
string
Subscription
object
Subscription schema.
19 properties 14 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

treasuryspring-subscriptions-api-openapi.yml Raw ↑

Other APIs TreasurySpring publishes across the network.

TreasurySpring Calendar API
TreasurySpring Cells API
TreasurySpring Entities API
TreasurySpring Event Checkpoints API
TreasurySpring Events API
TreasurySpring Healthcheck API
TreasurySpring Holdings API
TreasurySpring Indications API
TreasurySpring OAuth API
TreasurySpring Obligor Exposure API
TreasurySpring Tasks API
TreasurySpring Webhooks API
Where this information came from

This is an independent, third-party profile of TreasurySpring 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.