{
"opencollection": "1.0.0",
"info": {
"name": "Yodlee Core APIs Account Token Auth API",
"version": "1.1.0"
},
"items": [
{
"info": {
"name": "Auth",
"type": "folder"
},
"items": [
{
"info": {
"name": "Generate Access Token",
"type": "http"
},
"http": {
"method": "POST",
"url": "{{baseUrl}}/auth/token"
},
"docs": "Generate Access Token using client credential authentication.
This service returns access tokens required to access Yodlee 1.1 APIs. These tokens are the simplest and easiest of several alternatives for authenticating with Yodlee servers.
The most commonly used services obtain data specific to an end user (your customer). For these services, you need a user access token. These are simply tokens created with the user name parameter (loginName) set to the id of your end "
},
{
"info": {
"name": "Delete Token",
"type": "http"
},
"http": {
"method": "DELETE",
"url": "{{baseUrl}}/auth/token"
},
"docs": "This endpoint revokes the token passed in the Authorization header. This service is applicable for JWT-based (and all API key-based) authentication and also client credential (clientId and secret) based authentication. This service does not return a response body. The HTTP response code is 204 (success with no content).
Tokens generally have limited lifetime of up to 30 minutes. You will call this service when you finish working with one user, and you want to delete the valid token rather th"
},
{
"info": {
"name": "Delete API Key",
"type": "http"
},
"http": {
"method": "DELETE",
"url": "{{baseUrl}}/auth/apiKey/:key",
"params": [
{
"name": "key",
"value": "",
"type": "path",
"description": "key"
}
]
},
"docs": "This endpoint allows an existing API key to be deleted.
You can use one of the following authorization methods to access this API: