Not able to get User Transaction details from Yodlee API - yodlee

I'm using the http://developer.yodlee.com/TestDrive developer Test API module and using one of the 5 dummy accounts provided by Yodlee, For a particular user I have managed to add a dummy DAG bank account and one real bank account which is visible in getAllSiteAccounts details Api so its obvious that site have been added.
But while using the getUserTransactions API I'm getting error
{
"errorOccurred": "true",
"exceptionType": "com.yodlee.core.transactionsearch.exceptions.InvalidSearchIdentifierException",
"referenceCode": "_567afa0b-9d5a-4fb4-9db1-afd4f43c39c2",
"message": "Invalid argument value: com.yodlee.core.transactionsearch.TransactionSearchIdentifier#2ad082d0"
}
I also tried using the executeUserSearchRequest still didn't get any transaction details
{
"searchIdentifier": {},
"numberOfHits": 0
}
Can you please guide me If I'm using the API's correctly ?

You should use executeUserSearchRequest API to get the transactions. You should check the date range you have provided while searching for transactions and also try to remove itemAccountId.identifier and then search, you should get the transactions.

I'm having the same issue the only difference though is that I don't have any issues on DAG accounts, but when I used our production account I can't get the user transactions. I was reading this post Get all user transactions with executeUserSearchRequest and I guess the solution is to make sure that your server/code have the same timezone configuration.

Related

how to retrieve bill pay transactions using yodlee rest api

I using the executeUserSearchRequest to get transactions for bank,credit etc.
But I'm not able to get Bill Pay transactions.
Should I not be using this method to retrieve the lines, or perhaps I'm doing the search wrong. I know the account I'm using does contain lines as I've verified using another application that uses the yodlee api;s.
I using these settings
ContainerType: All
SplitType : ALL_TRANSACTION
transactionSearchRequest.searchFilter.itemAccountId.identifier = 9999999
where 99999 is the itemaccountid
all other values are defaults from the API testing tool
https://developer.yodlee.com/Aggregation_API/Aggregation_Services_Guide/Aggregation_REST_API_Reference/executeUserSearchRequest
You should be able to retrieve transactions for billpay using the same API i.e., executeUserSearchRequest. Please remove itemAccountId.identifier and try to get transactions, it will return transactions for all accounts.
You can then verify is transactions for your billpay account is present or not.
If you want transactions for specific account then you can first call getItemSummariesForSite API to get the account level details for the added account and from there you can use the itemAccountId and pass it on to executeUserSearchRequest API.
If you still face any problem, please share your memSiteAccId over our chat support and we will be able to help you.

InvalidSearchIdentifierException on using the yodlee testdrive

I have just login to Yodlee platform and exploring the API, I have gone through the quick start and test drive, now I'm getting the InvalidSearchIdentifierException when I'm just using default values provided by test drive sample app. The error shown is
{
"errorOccurred": "true",
"exceptionType": "com.yodlee.core.transactionsearch.exceptions.InvalidSearchIdentifierException",
"referenceCode": "_47ee0b3c-ea92-4a7a-9ba7-0a02bad49d47",
"message": "Invalid argument value: com.yodlee.core.transactionsearch.TransactionSearchIdentifier#21d77397"
}
but according to the documentaion the search identifier is 192168210225-1377612242609--1002083317-TX_SEARCH mentioned in link
please anybody tell me why I'm getting this error
anyway testdrive app is here
You are using getUserTransactions API, so I assume you want to get user's transactions. You should be using excuteUserSearchRequest API to get the user's transactions, getUserTransactions API should be used when you user has more than 500 transactions as excuteUserSearchRequest API returns transactions in batches of 500. For more details refer this.

Invalid account details accepts while adding new site account in yodlee live API

I'm using yodlee live API to link the bank transaction details.
Invalid bank account details accepts, when we add new site account in yodlee via live API, For example, the the account details like xxxxx and yyyyy, then the account added successful.
It's normal or any settings to be turned on in yodlee account or API parameters?
How can i validate the account details? while user add new site account?
Thanks in advance.
Though Yodlee accepts the invalid details/credentials, the account would fail. This would be represented by an Error code such as 402, which would mean that the credentials are wrong.
This is normal setting and teh only way you can validate if the details are right is by checking the status of the account. The error code should be "0" if everything is right.
Hope this helps. You can get more details on error codes under different scenarios #Error Code
Hope this helps
-Vijay
In short: Yodlee doesn't know the username/password entered during add account are correct or not; it has to validate the same with Bank website.
To explain you the process:
When you are adding a particular Bank account, you provides the username/password(it may be correct or incorrect) Yodlee doesn't know and can't validate at the time of submission. Yodlee takes the inputs(username/password) and submits the same to the Bank website(which consumer had selected); meanwhile you'll receive a response from API- addSiteAccount1, which will have the code as 801 (Refresh Never Done and Yodlee is going to update your account).
Once Bank website validate the same and found them incorrect Yodlee return 402 error code(invalid credentials), you need to call getSiteRefreshInfo API to check the same in loops each of 3-4sec.

Yodlee REST API: How to resolve CobrandUserAccountLockedException?

Currently, I am making the following POST call:
https://rest.developer.yodlee.com/services/srest/restserver/v1.0/authenticate/coblogin?cobrandLogin=sbCobFoo&cobrandPassword=Bar
(Note that I inserted a fake login and password for the purpose of this post). I am getting the following response:
{"Error":[{"errorDetail":"The account for user sbCobFoo is locked"}]}
I wasn't able to find anything in the Yodlee documentation, other than that this error represents CobrandUserAccountLockedException. Has any one encountered this error and/or know how to resolve it (i.e. unlock my account)?
You will need to reach out to your Yodlee Customer Service representative to get your credentials unlocked. Yodlee does not provide any API to unlock user/cobrand account(s).

Authorize.net Integration

I am attempting to integrate Authorize.net into my site. I have set up and activated a test account in their test.authorize.net domain and have obtained and inserted their API key/login for my account into my configurations. I run my script through their API and I get the proper success message that they've received the information. However, every time I log into the test.authorize.net domain and search for the transactions via their Search tab, it always returns with nothing regardless of what parameters I search with. What can cause this?
Look in the unsettled transactions. That's where they'll be.
FYI, Authorize.Net developer accounts do not actually process transactions. They only validate that the data you sent over via their API was valid and complete. If it is you will receive an approved response with a fake transaction number, approval, and AVS response code (which is always a match). If your made an invalid API call an error message will be returned alerting you to your error so you can correct it.
If you don't want o call Authorize.Net for support or they give you the run around, you can also get help in their developer forums.
Authorize.net does not actually log transactions in test mode.
You should call their support; they are fantastic. However, from my experience you typically get a shared account where lots of tests are running and it can be hard to search for your transaction.