What is the Integration Account Callback URL for? - azure

The Azure Integration Account features a tab on its configuration blade labelled "Callback URL":
This is documented in terms of generated API documentation but this doesn't say anything about its purpose. I can't find any documentation that mentions it.
What is this URL for?

Basically the callback uri we are using for reverifying/recheck the details of our integration account that we created earlier so that we can see properties of it. Likewise, we use jwt.io to see the content of any token.
For example:-
You can generate the callback url of an integration account using the below api with post method by passing the following parameter as mentioned in this MS DOC:-
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/integrationAccounts/{integrationAccountName}/listCallbackUrl?api-version=2016-06-01

Related

Expose webhook documentation in apim

To clarify the title I am not thinking of the registering to a webhook through APIM, but to utilize APIM as my documentation for all API related information.
In our setup we wanted to also expose information about possible json objects from our webhooks and saw that this exists in OAS3.1. And azure APIM supports OAS3.1 for import. However importing a test webhook results in an error saying that it isn’t supported
This example was taken from OAS GitHub. So I know I can cheat and creat a dummy endpoint to allow people to view the documentation - but it is not ideal for our use case.
So the questions are:
how to expose the webhook documentation?
am I missing something in Microsoft documentation because I cannot see that it should not be allowed what I wanted to do?

Get Records from Salesforce using Azure Logic Apps

I am trying to use Azure Logic Apps to read data from one of the Salesforce objects which has huge number of records. The Salesforce connector fetches the record and returns the pagination link as #odata.nextLink. But when I try to use a JSON parser to read the value it’s coming as null.
I tried to access the nextlink in a browser but it requires authentication. What authentication do we pass here ?
I would like to use an until action to iterate till I get a next link . So how do I check the condition for the until loop ?
nextLink doesn't look like core Salesforce thing, it might be the OData connector preprocessing the results for you. You'd have to consult the documentation for the connector (if any).
Salesforce's REST API will return field with nextRecordsUrl if there's next page of results, you'd call that in loop until the field disappears. You'd call it like any other REST API resource available after login, by passing Authorization: Bearer <sessionId also known as accessToken here>. Again - probably the connector abstracts this away from you. Don't think you can send headers like that in browser, you'd need curl, Postman, SoapUI or similar http client.
If you don't get better answer and documentation is scarce - consider using raw REST API. Or Azure Data Factory has an almost-decent Salesforce connector?
https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_query.htm

DocuSign API "GET envelope" route not taking into account "include" parameter

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.

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.

How to access a gmail account I own using Gmail API?

I want to run a node script as a cronjob which uses Gmail's API to poll a gmail account I own.
I am following these quickstart instructions:
I'm stuck on the first step. When requesting credentials for a cron script it tells me that "User data cannot be accessed from a platform without a UI because it requires user interaction for sign-in":
The docs are confusing in general, and mention "service accounts," "OAuth," and other things -- I cannot tell which apply to my use-case and which don't. I've used many SaaS APIs, and the typical workflow is to login to your account, get an API key and secret, and use those in your script to access the API. It seems this is not the paradigm used by the Gmail API, so I'd appreciate any guidance or links to clearer instructions.
I also find that the documentation can be confusing at times, but what you want to to is actually pretty straight forward once you get it:
Register your App at Google, and say what APIs you want your App to have access to (only the Gmail API in this case). This will give you two strings, a client_id and a client_secret (which is the content of the client_secrets.json-file above).
Since you are just going to write a script for your own account only, you don't need a http-server. The Oauth Playground will suffice. Press the Settings Cog on the top right and use your own OAuth credentials.
Select the Gmail API in the list of APIs and follow the outlined steps.
Now you have an access_token and a refresh_token you can use to keep your script going indefinitely!
To fully understand the use of Gmail API, going through Gmail API Overview really will make a difference.
And you can also use these documentations to start building a Gmail app:
The client libraries are available for download in several languages and simplify making API requests.
The developer guide topics help you better understand how to implement particular use cases.
The API reference gives you details on every resource and method in the Gmail API.
I hope these help.

Resources