Adobe sign Webhook : Invalid webhook url - invalid-url

Currently we are trying to use webhook for getting back the signed document. But in the creation of webhook itself, we are getting an error that "webhook URL is invalid". We have tried becceptor for testing purpose. So it worked there . But when we tried with our production environment's webapi URL, we weren't able to create webhook.
We were thinking that due to change in the web hook url which contains special characters like "#" , ":" and few like that in text, for authenticating our webapi URL.
Does adobe is making validation over the webapi URL? If someone is facing similar kind of issues, assistance over this will be really helpful.
Thanks in advance.

Related

How do I create a notification url endpoint for microsoft graph api change notifications

I am trying to get change notifications for users using microsoft graph api. For testing purpose I have been using ngrok as suggested by many.
But now I want to use the real notification url to test my code.
How do I do it? The microsoft documentation says "This URL must make use of the HTTPS protocol".
Do I create an endpoint in azure or what are the other options?
Thanks in advance.
The notificationUrl is just your proxy URL. See the example here: https://github.com/OfficeDev/hands-on-labs/blob/master/O3653/O3653-19%20WebHooks/Lab.md
The one in the sample using ngrok looks like:
https://74c48253.ngrok.io/notification/listen
You could use a Power Automate Instant Cloud Flow with the trigger as "When an HTTP request is received" and the subsequent steps could include emails with the details of the notification.
When you save the flow a URI will be generated which you can copy and use as your Graph change notification URI.

Netsuite Token Based Authentication (TBA) with PHPToolkit?

Does anyone have a working sample using Token Based Authentication with the Netsuite PHP Toolkit (Version 2017_1)? I have it working with User/Request based authentication using the sample files but need to move over to token based. I have generated both the consumer and user-based keys, and the integration works with my user/password.
I keep getting the error of "Your connection has timed out. Please log in again." The keys generated are brand new. Does anyone have any trouble with this integration that sounds similar to this?
Try creating a new login passport before each request made to the NetSuite API.
I work with C#, but had the same issue when I initially switched over to TBA. I have a method which creates the token passport and adds it to my NetSuite service object. I then call this method before each API call.
I hope this helps!

Instagram subscription - Unable to reach callback URL - ONGOING

This issue has been posted many times before but I haven't found a solution yet. I've contacted Instagram Developer support but a week later I've still had no luck or a response form them so hoping someone here can help me out. My app has been approved by Instagram for basic permissions.
Doing a Form POST to https://api.instagram.com/v1/subscriptions/ with all the relevant data (callback_url, object=user, aspect=media, verify_token, client_secret, client_id) to create a subscription for Instagram User Subscriptions yields the error: APISubscriptionError - Unable to reach callback URL
The callback URL I'm using has logging on it to log all requests which works
when accessed directly via a browser. Using the logs I can see Instagram isn't even reached my callback URL.
The callback URL is accessible publicly over the internet and the domain is being used in production.
The callback URL implements both GET and POST methods (even PUT just in case).
Worked a few weeks ago using a UAT URL.
The callback URL still returns the 'Unable to reach callback URL' with http or https.
I've changed IP addresses, used a VPN and run the post script form different locations.
Tried different parts eg domain.com/instagram/subscriptions or
domain.com/instagramsubscriptions
-Tried a different sub domain and different URL.
Have deleted all subscriptions using the DELETE request
Any help or suggestions would be greatly appreciated.

Evernote webhook notification

I registered for Evernote webhook successfully with a valid end point recently. But whenever I make any changes to my evernote account, either by creating or updating a note, I am not being notified by the webhook. I am using a page created with http://requestb.in/ as an endpoint but I don't see evernote making any requests to it. I have reached out to Evernote support but haven't received a response yet.
How do you test to see if Evernote Webhook is working as expected?
The easiest way is to check the web logs of the web server you've set up to receive them.
I have a couple of web hooks set up and they seem to work. I've used a node.js app to receive the webhooks.
Double-check that you asked for the right kinds of notifications? What filter did you ask for?
Other than double-checking the URL you gave them, and double-checking the logs, and if using https ensuring you are using a valid certificate, there isn't much else other than waiting for the support response.
In the meantime you can test your code by hitting your webhook server with appropriately formatted URLs.

Receiving "Redirect_URI" Is NOT Valid Error With Outlook Contacts REST API?

I integrated the following Outlooks Contacts API with my website this way users with a hotmail.com, outlook.com, msn.com, windows live email address can easily connect to their contacts.
https://msdn.microsoft.com/office/office365/APi/contacts-rest-operations#Getcontacts
However, I keep on receiving this error when I try to log in to my hotmail email account:
The provided value for the input parameter "redirect_uri" is not valid. The expected value is "https://login.live.com/oauth20_desktop.srf" or a URL which matches the redirect URI registered for this client application.
Does anyone know what is causing this issue?
I created my app credentials again but it still doesn't work.
Thank you!
The redirect needs to match the redirect you specified when you registered your application. This should be a URL in your web app that receives auth codes.

Resources