We are using the API to submit a form after a user signs a document, we add the integrator key and have performed 20+ transactions without errors. However, we continually fail.
We have submitted over 20 forms.
Awaiting approval.
In general, it's best to reach out to go-live#docusign.com to request assistance with the API Review process. When you reach out, please include your integration key, your Demo account ID and your Production account ID.
The Go Live Troubleshooting Guide may help you investigate your cause of failure.
Related
I requested one tap signup/signin for website API as documented in https://developers.google.com/identity/one-tap/web/
However, there has been no update or hear an update from them for more than a week. Does anybody know how long it usually takes to get the request reviewed?
Thanks
I got mail back from them after around 3 weeks of submitting the form.
They said currently you won't be granted access to API. However, they are in the process of including some additional security from their side and it may take a few months. We can hope to get API access then.
We have a client account of Amazon seller central. We need to pull campaign performance data from this account. With Amazon Advertising API we can pull this report.
Here are the documentation links:
https://images-na.ssl-images-amazon.com/images/G/01/AdProductsWebsite/downloads/Amazon_Advertising_API_Getting_Started_Guide.TTH.pdf
https://images-na.ssl-images-amazon.com/images/G/01/AdProductsWebsite/downloads/Amazon_Advertising_API_Reference.TTH.pdf
I followed the procedure in Getting Started Guide
1) Created a developer account(Login with Amazon)
2) completed the sign up form as specified in second step.
I am not sure what to do next as I did not receive any reply from amazon regarding this. Does anyone faced similar issue before?
Thanks.
It takes two or three days from Amazon to reply in most case and as they are getting high volume of application it might be possible that they have rejected it so try more then once. And try to give some information to use in the comment section.
In addition, a business registration in either NA or EU is required before they can grant permission to the Advertising API.
After all this verification they can allow access.
Hope this help to you.
Thanks,
James
If you have already received the onboarding e-mail, and you are sure that you are sending the correct API communications yet you are getting bad scope errors, then you are not yet White Listed so your requests are all rejected.
For me and many others I found while googling for hours to find the answer, this problem was due to not yet signing a license agreement which is in a very easy to overlook link hidden in a paragraph of the e-mail which starts: "Before you can register your application, you need to agree to the Amazon Advertising API License Agreement" Hit that link and accept the agreement to become white listed.
As a last resort if the above doesn't work, Amazon support had given me a direct e-mail to LWA and you can contact their support: lwa-support at amazon com.
I have read this article
Please explain the refresh process that yodlee employs..
We understand this happens within a 19 hour window, is there anyway to stop the automatic refresh (the initial refresh on a Site based AddAccount1 is fine) - so that the subsequent refreshes can be manually controlled.
Thanks
The automatic refresh can be turned off for any client by Yodlee. You can contact the customer care team by logging a service request through YCC(Yodlee customer care ) tool and they will help you with that.
I have a bunch of IAPs in my iOS application, and I have implemented receipt validation for the IAPs.
I'm wondering what error handling I should be doing if the receipt validation request fails.
So, say you have a user who legitimately purchases one of the IAPs, the transaction was successful but the request to verify the receipt fails for whatever reason (e.g. no connection, Apple's server is down). I assume that the user will have been charged because the transaction was successful, but as the validation failed the user will not have been given the content.
What should I do in this situation? I know it might be a rare case but I want to account for it anyway.
I was thinking I could save the receipt to persistent storage and retry the receipt validation in the background until it succeeds. Is this a viable option? Do the receipts remain valid forever or do they expire after a certain amount of time?
I couldn't find much information on this from Apple's documentation so I'm asking you guys.
Thanks in advance
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.