Forum Discussion
sending API requests from Power Query
Hi misaki ,
Workaround to handle this scearion :
Use query parameters or headers instead of Content
If the API supports authentication via headers (e.g., Authorization: Bearer <token>) or query string, you can safely store credentials in the credential store and still send requests.
m
Web.Contents("https://api.example.com/data",
[
Headers = [Authorization="Bearer " & AccessToken]
])
Use relative path with Web.ContentsPower BI allows Content bodies only when the base URL is fixed and the dynamic part is passed via RelativePath or Query.
This way, the credential store knows exactly which domain is being authenticated.
:
m
Web.Contents("https://api.example.com",
[
RelativePath = "endpoint",
Content = Text.ToBinary("{""param"":""value""}")
])
Use OAuth2 authenticationIf the API supports OAuth2, Power BI has built-in support.
You authenticate once, and Power BI manages tokens securely.
This avoids embedding secrets in your query.
Store secrets in Azure Key Vault or parameterize them
Instead of hardcoding credentials, you can store them in Azure Key Vault or as Power BI parameters.
Then reference them in your query, keeping sensitive values out of the M code.
Thanks,
Lakshmi.
Community SupportHi misaki
Thanks for reaching out to the Fabric Community.
To better understand your scenario, could you kindly provide more details on the following points:
- What type of content are you trying to send in the request body?
- Are there specific authentication methods supported by the API (like OAuth or API keys)?
- What is the expected structure of your data that needs to be sent?
Thanks,
Lakshmi.
Hi v-lgarikapat
I’m sharing the full text of the request.
The authentication method supported by the API is Basic authentication.
let
url = "https://secure.p01.eloqua.com/",
body = "{
""name"": ""EmailSendActivitiesExport"",
""fields"": {
""ActivityId"": ""{{Activity.Id}}"",
""ActivityType"": ""{{Activity.Type}}"",
""ActivityDate"": ""{{Activity.CreatedAt}}"",
},
""filter"": ""'{{Activity.Type}}' = 'EmailSend'"",
""areSystemTimestampsInUTC"": true
}",
Source = Web.Contents(
url,
[
RelativePath = "api/bulk/2.0/activities/exports",
Headers = [
#"Content-Type"="application/json",
Authorization="Basic " & Authorization
],
Content = Text.ToBinary(body)
]
),
JsonResponse = Json.Document(Source)
in
JsonResponse
- v-lgarikapat
Hi misaki ,
Workaround to handle this scearion :
Use query parameters or headers instead of Content
If the API supports authentication via headers (e.g., Authorization: Bearer <token>) or query string, you can safely store credentials in the credential store and still send requests.
m
Web.Contents("https://api.example.com/data",
[
Headers = [Authorization="Bearer " & AccessToken]
])
Use relative path with Web.ContentsPower BI allows Content bodies only when the base URL is fixed and the dynamic part is passed via RelativePath or Query.
This way, the credential store knows exactly which domain is being authenticated.
:
m
Web.Contents("https://api.example.com",
[
RelativePath = "endpoint",
Content = Text.ToBinary("{""param"":""value""}")
])
Use OAuth2 authenticationIf the API supports OAuth2, Power BI has built-in support.
You authenticate once, and Power BI manages tokens securely.
This avoids embedding secrets in your query.
Store secrets in Azure Key Vault or parameterize them
Instead of hardcoding credentials, you can store them in Azure Key Vault or as Power BI parameters.
Then reference them in your query, keeping sensitive values out of the M code.
Thanks,
Lakshmi.
- v-lgarikapat
Hi misaki ,
Thank you for reaching out to the Fabric Community Forum.
I wanted to follow up to check if you had a chance to review the information provided by us . If you are still facing issues, please don’t hesitate to reach out we’ll be more than happy to assist you.
Best Regards,
Lakshmi.
- v-lgarikapat
Hi misaki ,
I wanted to follow up to check if you had a chance to review the information provided by us . If you are still facing issues, please don’t hesitate to reach out we’ll be more than happy to assist you.
Best Regards,
Lakshmi.