Envestnet Account Token API
Account verification customers looking to integrate with one of our payment partners can use the Account Token endpoints. These APIs allow creating a secure processor token for your user's verified financial accounts. You can then share the processor token with our payment partners to enable them to securely request the user's account details from Envestnet | Yodlee.You will have to set the header before making the API call. The following headers apply to all the APIs:Authorization: This header holds the access token Api-Version: 1.1Note: If there are any API-specific headers, they are mentioned explicitly in the respective API's description.
Envestnet Account Token API is one of 21 APIs that Envestnet publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Account Token. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 2 operations across 1 path, and defines 4 schemas. It is described by OpenAPI 3.0.1, at version 1.1.0.
Requests are made against a single base URL, /.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 2
Across 1 path, the API surfaces 2 operations — 1 DELETE, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Account verification customers looking to integrate with one of our payment partners can use the Account Token endpoints. These APIs allow creating a secure processor token for yo…
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are YodleeError (3 properties), AccountToken (2 properties), PaymentProcessorTokenRequest (2 properties), PaymentProcessorTokenResponse (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Envestnet 12
Other APIs Envestnet publishes across the network.