In our code we are using the below REST API Endpoint https://outlook.office365.com/api/{version}/{user_context}
There was a mention in this link(https://msdn.microsoft.com/en-us/office/office365/api/use-outlook-rest-api) that the above REST API Endpoint will work for a while and that we will need to change to the new REST API. Please can you confirm the until when https://outlook.office365.com/api/{version}/{user_context} URL will be valid.
Thank you
I don't have a specific date to share. Is there some reason you cannot switch to the https://outlook.office.com endpoint immediately? The API is exactly the same, so it should be a simple matter to change.
Related
My company uses DocuSign API to automate document-related tasks.
Via the API, I need to retrieve all envelopes that are expiring soon. Similar to what the DocuSign UI has in the screen below but for all users:
Can somebody point me in the right direction -- which API endpoint/method I need to use to get all envelopes that are about to expire? Is there any way to use DocuSign Connect to trigger a callback from DocuSign for each document that is about to expire?
Thank you!
Add the following to your API call (GET to /envelopes endpoint)
folder_ids=expiring_soon&folder_types=normal,inbox,sentitems&include=recipients,powerform,folders,delegations,workflow&include_purge_information=true&query_budget=10
Remember to also have from_date and to_date parameters
https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/liststatuschanges/
Also, the way I found this out for you was by trying it from the web app and recording API logs, Suggest you try that too as it will mean you can find it yourself. https://www.youtube.com/watch?v=YJYTDcc7cZw
I'm attempting to use the new Constant Contact V3 API to add a new email contact. I've been reading the docs: https://v3.developer.constantcontact.com/api_guide/client_flow.html, and trying it out and it seems like the only way to do this now is to make an authentication request, approve the request and then retrieve and access token that is valid for only 2 hours.
I need to have access from my server only and just send an add contact request to Constant Contact. I don't understand why I require to have a redirect uri now and an access token to use the V3 api instead of just using the api key.
With the V2 api I was able to make these types of requests directly from the server without hassle and that's exactly what I need now. The V2 documentation seems to be taken down so I can no longer do that so I'm stuck.
Any help is appreciated.
Based on this link: https://community.constantcontact.com/t5/Developer-Support-ask-questions/v2-or-v3-API-for-very-basic-integration/m-p/324777#M11434, it seems like server-to-server auth is not available still. For those of you who have the same issue, use Mail Chimp or another service that has basic api requirements.
You can get INITIAL Access Token without any code - just use your browser and curl. The Access Token is valid for 24 h, but you can automatically renew it using Refresh Token. You can renew it automatically every time it expires and never need to proceed through INITIAL flow over again. You can read about it here. If you are using C#, I have templates and instructions exactly for your scenario here: https://github.com/mikeks/constantcontact-v3.
I'm trying to use this route https://developers.docusign.com/esign-rest-api/reference/Envelopes/Envelopes/get to get information on a specific Envelope in DocuSign, and I wanted to add the ?include=recipients parameter so as to get individual signers status too, but the parameter does not seem to do anything
Trying other values to include (documents, tags, etc). Doesn't change the response either.
Same result whether I try from my own code or from DS' "API explorer" tool
Am I using it wrong or is it a bug in the API?
This parameter (?include=recipients) is a new addition in the v2.1 API. You should ensure that the API endpoint you are calling has the v2.1 in the URL and not v2. You cannot use this feature with the v2.0 API. There are other reasons to use latest API 2.1 and it's supported by all SDKs.
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.
So here is what i am trying to do :
I built a bot with api.ai for my business that is hosted on my webpage and my Facebook page right now. Bot works well.
I want to push it to the next step by allowing my customers to make querys on my calendar, ask to book a specific time, see if available, if not offer other time similar, then make a booking.
I have been reading this thread and the great answer attached to it but i think my case is a bit different.
I was wondering if the bot could always have a token so every guests won't have to Auth to query the calendar ?
Obviously i am new to this, i have been reading the guide of google calendar api and api.ai but i don't really see how to do that yet. I guess there is a way to store a token somewhere and then just trigger the query with some specific intents but not to sure how.
I have also done the node.js quickstart guide of the G-calendar api, and it works fine if that helps.
Thanks for your help !
You will probably want to use a Service Account that is permitted to the calendar in question. Service Accounts are similar to regular accounts, but they are expected to do server-to-server communication only, so the method to create an auth token is a little different to keep it secure.
See https://developers.google.com/identity/protocols/OAuth2ServiceAccount for more information about using Service Accounts.
In general, you'll be using a shared secret to create and sign a JSON Web Token (JWT) you send to Google's servers. You'll get back an access token which you'll then use to call the Calendar API. The access token expires in about an hour, at which point you'll need to repeat the process.
There are libraries available to do much of this for you. For example, if you're using the node.js library https://github.com/google/google-api-nodejs-client, then it will take care of this for you (although you need to modify the key file - see the documentation for details).