We were using grant_type=password. It stopped working now. Is DocuSign still supporting grant_type=password?
This would be what we call "legacy auth" which is less secure and we highly recommend you move to OAuth.
As far as I know, it's still supported, if you're seeing an error - please let us know what error you are seeing. It's hard to help without additional information.
Related
So I've been looking around for answers but haven't been able to find any up to date solutions to my problem. So my use case is pretty simple, I want to be able to check the online status of a list of users at my organisation using Skype for Business. Opening chats with them is simple enough, but actually getting the online status has shown to be a challenge.
I've been looking into the SDK but it seems a bit over the top for my use case, and I haven't been able to get web ticket authentication working (I'm implementing this in an Electron app). Even if I got that far, would I have to make an account with specifically only the contacts I need added and use that as authentication?
Sorry if this is a stupid question, but it seems like the SDK/API is a bit over my level and I'm missing something. Do I need to add in my own server middleware between the node/electron-app and their API or something similar maybe?
Any help is greatly appreciated.
I have been working with Facebook API and there documentation is awesome. Now i need to use the Instagram API and there documentation is not developer friendly, I want to use the Direct message functionality using Instagram API and i am unable to find that how to do it? as i can't see it in there documentation and I have been doing research for hours but unable to find any best possible resource.
I don't even know that are they providing the "Direct message" functionality or not? After my all research i have come to know about "Instagram Private API" which provides direct messaging functionality but i don't know that are they officially using there API's for messaging. I am sure they are using a Hack for that but i don't know that for how much time hack lasts long.
Any One who can guide me would be great.
I appreciate for your time and consideration.
Please do let me know about your concerns on this.
Thanks in advance!
A Bit Late To Answer (Aug, 2022)
I have successfully cracked it by myself, after doing a lot of research on google over this topic. You can use the mentioned deep link to open Instagram Direct with some text to share from your application,
instagram://sharesheet?text={AnyTextOrLinkToShare}
Moreover, the below code should work on iOS to launch Instagram Direct (Messenger) from your app with some content
if let url = URL(string: "instagram://sharesheet?text=https://google.com/") {
UIApplication.shared.open(url, options: [:], completionHandler: nil)
}
Not sure, why did they hide this information from their official documentation but now who cares, I have achieved it with the continuous efforts of 16-18 hrs! :)
I understand this isn't a typically appropriate question for Stack Exchange but the Nest customer service has basically no information whatsoever on developer support, and the Works with Nest support contact form recommends using Stack Exchange tagged with nest-api. Anyway, I have created an application in the developer portal I need to submit for a user limit increase, and I have been unable to submit the form for the last 3 days. I receive a generic error that says:
We're sorry. Something went wrong. Please try again later. The backend responded with an error
As I said, I contacted every customer support outlet Nest offers and have yet to get any assistance. If anyone has encountered this error or has the proper avenue to reach out to Nest's developer support team, please let me know. Thank you in advance, again I apologize for the narrow scope of this question.
If anyone else runs into this issue, my final resolution was to re-create a second application on a different developer account, and then migrate my web service to use the new application's client secret, API tokens etc.. Albeit a huge hassle, the submission (using the exact same form data as before) worked on the new application.
I am very confused as to how the API of DocuSign works, I tried looking it up here:
https://www.docusign.com/p/RESTAPIGuide/RESTAPIGuide.htm
But that didn't help me much, especially not because I need to implement DocuSign into the open source version of Vtiger.
Does anybody here know a site where I can learn more about DocuSign and how I can combine it with Vtiger open source?
As for what I already tried that is nothing, I first need to make a functional design which is kind of hard to do when you don't even understand the basic API.
I would really appreciate it.
I have never worked with an API before, so this is all new for me.
Have you tried the API overview instead of the reference guide? Check this out:
https://www.docusign.com/developer-center/api-overview
You can also look at the API Recipes to see some starting examples of what you can do in any language. I believe VTiger is written in PHP so you can find the PHP code to copy and paste to get you started.
I saw the commercial library for iAd's from Monte but he isn't developping it anylonger due to the coming of InnerActive Ads in Livecode, right? So, I have created an InnerActive account and tried the only lesson I found on Livecode Lessons. That didn't work. So I posted a comment there which is awaiting moderation for quite some time now. I also mailed Inneractive, got a ticket replied, but no answer from them either.
If anyone has Ads with Inneractive running please tell/show us how you did it. I am calling mobileAdRegister with my appID and that seems okay. Then I try mobileAdCreate and mobileAdSetTopVisible and 'the result' tells me 'could not create ad'.
Dictionairy then tells me the app does not have Internet permissions or the registered app key is not valid. But I do check for internet connection and I'm sure I'm using my valid appID..
Regards, Amsterfrank
I have tested ads in the current release of LiveCode and they do indeed seem to be broken.
The LiveCode quality control team is aware of this and are currently investigating what could be the cause of this. A report on this issue can be viewed here-
http://quality.runrev.com/show_bug.cgi?id=11224
A workaround for now is to use an older version of LiveCode. After running a few tests, the last version of LiveCode that does not exhibit the mobile ad bug is LiveCode 6.0.0. This is available to download from here-
http://downloads.livecode.com/livecode/
With that being said, I would recommend holding off until the issue is resolved in a more current releases as there have been many bug/enhancements to LiveCode since 6.0.0