I am using sandbox account for docusign everything is working fine. Now I want do this for LIVE account for this I have followed this URL https://developers.docusign.com/esign-rest-api/guides/go-live-steps#review-failed.
While I am going send request to review my AIP transaction. I am getting response Review did not pass.Error in 3rd step. Compliance with [[linkstart]]API rules and limits[[linkEnd]].
Here is a snap shot of error page
https://drive.google.com/open?id=1O7zCfDGHf5YIbZ0EtnWmr7N3hKjvmApG
I have downloaded a error logs. No error found in this log
https://drive.google.com/open?id=1jXxkf53g9_ELsRnEjF44qrMkDpIuV-dt
This review failed due to a known issue in the automated review process (tracked under DCM-3308). In short, the GetEnvelopes call isn't properly tracked, so the review cannot correctly distinguish between valid traffic that complies with the Polling rule and invalid traffic that does not.
For anyone else who encounters this issue (Specifically, with the GetEnvelopes call appearing in the traffic CSV): First confirm your traffic is not polling for the same resource more than once every fifteen minutes, then reach out to go-live#docusign.com: provide your integration key and the CSV of review traffic.
Related
I used ACH transfer with plaid and stripe my website.
Bank connections are currently working. However, after connecting their bank account, the user gets a 400 server error that prevents them from being redirected to the dashboard.
I believe the error code associated with this issue is PRODUCT_NOT_READY
https://plaid.com/docs/errors/assets/#product_not_ready.
The server is a node server.
I want to know how I can fix this error.
Regards
Are you tracking the webhook? It seems that the server will send you a WebHook to the endpoint and only after that the resource will be available.
The Plaid server will send you a PRODUCT_READY webhook before you can call /asset_report/get
The PRODUCT_NOT_READY error you linked to is of type ASSET_REPORT_ERROR. If you're using Plaid for ACH transfers, you're probably not using Assets and you're probably getting the PRODUCT_NOT_READY error of type ITEM_ERROR. For that error, the likely causes listed are:
/transactions/get was called before the first 30 days of transaction data could be pulled. [Not relevant to you if you're not using transactions]
/auth/get was called on an Item that hasn't been verified, which is possible when using micro-deposit based verification [probably the cause of your problem]
Like Nikolas L. says, you will need to listen for webhooks, in this case to be alerted when the Item has been verified.
I tried calling DocuSign sales and support (transferred around 3 times) and no one could give me a straight answer on this. Their "support" actually told be to try stackoverflow, so here I am...
I'm looking at their API pricing levels here: https://www.docusign.com/products-and-pricing/api-plans-b
If I have the Intermediate API, can I make the following API requests?
GET /restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/{documentId}
GET /restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/form_data
The part that's throwing me for a loop is the DocuSign Connect feature in the Advanced API plan. The description of it is:
The DocuSign Connect module lets you configure webhooks for envelope events and recipient actions for some or all users in your account. It can also be used to transport the completed documents back to your app or website and to retrieve any form field data entered by your recipients.
I don't need the webhooks, but I need to be able to get the completed documents as PDFs and get the form field data. Do I really need the DocuSign Connect feature for that?
You will be fine with the intermediate plan. Here is the basic distinction between polling and Connect - With Connect, we will proactively notify YOU when key envelope events occur.
Otherwise, it's up to you to call GET /envelopes and/or GET /form_data to retrieve that information. Be wary of the resource limits when you poll.
As a quick aside, instead of making two requests to retrive that information, just make one - GET /envelopes?include=recipients,tabs. This will provide you all the information you seek in one request.
The important excerpt from that guide:
You may not exceed one GET request per unique envelope endpoint per 15
minutes. If you exceed this limit the request will not fail, but it
will be flagged as a violation of rate limits which can cause your app
to fail review to go-live review.
For example, the following transactions violate API rules due to the repeated GET requests to the first document and second recipient:
[12:00:00] POST /accounts/12345/envelopes
[12:01:00] GET /accounts/12345/envelopes/AAA/documents/1
[12:02:00] GET /accounts/12345/envelopes/AAA/recipients/2
[12:03:00] POST /accounts/12345/envelopes
[12:04:00] GET /accounts/12345/envelopes/AAA/documents/1 *
[12:05:00] GET /accounts/12345/envelopes/AAA/recipients/2 *
However, the following set of requests comply with API rules and limits and would not be flagged by the platform:
[12:00:00] POST /accounts/12345/envelopes
[12:01:00] GET /accounts/12345/envelopes/AAA
[12:16:00] GET /accounts/12345/envelopes/AAA
[12:17:00] GET /accounts/12345/envelopes/AAA/documents/1
[12:32:00] GET /accounts/12345/envelopes/AAA/documents/1
[12:40:00] PUT /accounts/12345/envelopes/AAA/recipients/1
[12:41:00] PUT /accounts/12345/envelopes/AAA/recipients/1
Q: Anyone know any working method, or alternate URL, to create an Authorize.Net Sandbox Account?
After filling out the Sandbox Account form at, https://developer.authorize.net/hello_world/sandbox/ , I received the error message:
URL: https://developer.authorize.net/hello_world/sandbox/
Complete Page Body:
ERROR
The request could not be satisfied.
This distribution is not configured to allow the HTTP request method that was used for this request. The distribution supports only cachable requests.
Generated by cloudfront (CloudFront)
Request ID: eA28WPE73_KAV2p91ixOhETSVWssiFeOdvnr0az40wxLVIT2bDBhBw==
==EOF==
Edit 2017-12-04:
While not an answer to my question (which may be “There is none.”), I ‘mis’-used Authorize.Net’s contact form to request a manual account creation. As opposed to the ~2 days they give for reply ETA, the above form was ‘fixed’ and they replied, “I just tested the page and I could not recreate the error” within ~5 hours.
I’ll leave the question open for a week in case someone knows an answer, and afterwards close it with ‘None.’
We have some Logic Apps setup that monitor our various sites and a Slack connection set up. If a non-200 status code is returned, it sends a message to our alerts channel in Slack. We have about 10 sites that are monitored.
The first was setup, tested the cloned for the other sites.
The issue we're having is that they all seem to work bar one.
The site in question was offline this morning (after host updated the server at 3am this morning) and I can in the Azure log the trigger was fired - but no message in Slack.
I changed the Condition to "status equals 200" (to ensure it always fires), ran it manually and still see no message.
As mentioned this logic app was cloned from one that did work so the only thing that changes from app to app is the site URL and the contents of the slack message.
Being relatively new to various Azure features this was a bit of "R&D" for Logic Apps so I'm not really sure what to check.
Any obvious gotchas we should be aware of? Any pointers you can give to help resolve this would be great.
NB: I added Slack API as a tag to this but as this part is handled by Azure and it's working for other Logic Apps feel free to remove.
I am using the node-whatsapi library
I am getting the number blocked. I am following the exact protocol as mentioned in the WIKI.
The flow that i follow is:
Create Adapter
Connect()
On Connect - Login
On Login
sendIsOnline()
requestPrivacySettings()
requestServerProperties()
requestContactsSync()
For Each Contact sendPresenceSubscription(), getStatus() and getProfilePicture()
And when i receive a message:
adapter.requestContactsSync('1234567890', 'delta', 'background');
getProfilePicture()
Save to DB
Now, what we do and why do we use WhatsApi
We enable our existing Customers to talk to their internal teams on WhatsApp. So, a customer initates a chat and a help desk team responds to them on an application.
Got the number blocked now. Unable to understand where am i going wrong.
Also, the total number of messages exchanged between the customer and the helpdesk team is around 1k a day.
What you're "doing wrong" is using a third party API which is against WhatsApp's terms of service and, if detected, will get your relevant accounts blocked. It's not a fault with WhatsAPI itself or how you are using it.
WhatsApp openly publishes the only approved/compliant way to programmatically interact with their network.
http://www.whatsapp.com/faq/en/iphone/23559013
http://www.whatsapp.com/faq/en/android/28000012
Outside of that, you are going to get blocked whenever you are detected as using an unapproved means of interacting with their network.
In your particular example you're using a Node.js port of the original WhatsAPI. As of May 2015 this is the kind of pressure they are dealing with from WhatsApp (despite many years of trying to negotiate an amicable compromise with them around things like message limits and identity verification):
It sucks but that's just how it is. You can look at some alternatives which are still actively updated and may continue working for a while, but given that WhatsApp is now owned by Facebook and considering the kind of legal resources at their disposal, you should be able to see why one might be reluctant to continue updating a rogue API.
Well, got a satisfactory answer from WhatsApi collaborator matteocontrini.
Here is the answer that i got, if somebody is intrested.
It says:
the reason of getting blocked doesn't have to be because you wrote
wrong code. It could be a filter on the kind of messages you send or a
report from someone about your number.