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

Yodlee Configs API

Configs API

Yodlee Configs API is one of 23 APIs that Yodlee publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Configs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 5 operations across 3 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.1.0.

Requests are made against a single base URL, /.

5 operations 3 paths 9 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.0
Base URL
https://production.api.yodlee.com/ysl
Terms of Service
Resource Areas
1

Paths & Operations 5

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

Configs 5

Configs API

GET
/configs/notifications/events
Get Subscribed Notification Events
getSubscribedNotificationEvents 1 param → 200401404
GET
/configs/publicKey
Get Public Key
getPublicEncryptionKey → 200401404
POST
/configs/notifications/events/{eventName}
Subscribe For Notification Event
createSubscriptionNotificationEvent 1 param body → 201400401404
DELETE
/configs/notifications/events/{eventName}
Delete Notification Subscription
deleteSubscribedNotificationEvent 1 param → 400401204404
PUT
/configs/notifications/events/{eventName}
Update Notification Subscription
updateSubscribedNotificationEvent 1 param body → 400401204404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are YodleeError (3 properties), ConfigsPublicKey (2 properties), ConfigsNotificationEvent (2 properties), ConfigsPublicKeyResponse (1 property). Each schema is shown below with its type and property counts.

ConfigsPublicKey
object
2 properties
ConfigsNotificationEvent
object
2 properties
UpdateConfigsNotificationEvent
object
1 property
ConfigsPublicKeyResponse
object
1 property
UpdateConfigsNotificationEventRequest
object
1 property 1 required
ConfigsNotificationResponse
object
1 property
CreateConfigsNotificationEventRequest
object
1 property 1 required
YodleeError
object
3 properties
CreateConfigsNotificationEvent
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yodlee-configs-api-openapi.yml Raw ↑

Other APIs Yodlee publishes across the network.

Yodlee Account Verification API
Yodlee FastLink
Yodlee Account Token API
Yodlee Accounts API
Yodlee Auth API
Yodlee Cobrand API
Yodlee Consents API
Yodlee DataExtracts API
Yodlee Derived API
Yodlee Documents API
Yodlee Holdings API
Yodlee Institutions API
Where this information came from

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