Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
CarolineVA
Regular Visitor

SmartSurvey connection with API

I'm trying to use API connectors to pull through data from SmartSurvey. I have multiple SmartSurvey accounts which are used across my organisation, which I am the admin of.

 

I set up a GET API infrom Account A PowerBi which works perfectly. I don't know if this is relevant, but the email address for the Account A and my PowerBi are the same.

 

I'm now trying to set up another API from SmartSurvey Account B, but it seems to be defaulting to Account A, even when I use the token key from Account B. If I use an online API checker, it gets surveys from Account B no problem, so the API itself is set up correctly. I'm not sure how to make PowerBi connect to the correct SmartSurvey account.

 

I'm using Get Data from Web, then entering

 

 

 

 

 

https://api.smartsurvey.io/v1/surveys/{survey_id}/exports/latest/download?api_tokenXXX?api_token_secret=YYY

 

 

 

 

 

but getting Error 404 data not found - because the survey_id doesn't exist in Account A, where PowerBi is looking. If I do a general request for all surveys, it gives me the list of Account A's surveys, even when Account B's tokens are used.

 

ETA: 

I figured that the API tokens are stored in Data Source settings, and they're linking to Account A. So I guess what I'm asking now is can I have 2 sets of API tokens to link to 2 accounts, where the API address is the same?

 

Any ideas much appreciated

TIA

1 ACCEPTED SOLUTION
Anonymous
Not applicable

HI @CarolineVA,

According to your description, the issue seems related to power bi cache data source credentials features. (power bi will cache the credentials to the local when you use data connector to get data)
When you use this data connector to get data from same data source and switch between multiple accounts, they may cause the issue. (the cached credentials conflict with new credential, you can clean up the cached data to use new credential, but it will also affect the usages)
For this scenario, current I haven't found methods to resolve this issue. Perhaps you can try to use different data connectors to get data with different accounts, these different connector cached data should not conflict each other.

Regards,

Xiaoxin Sheng

View solution in original post

1 REPLY 1
Anonymous
Not applicable

HI @CarolineVA,

According to your description, the issue seems related to power bi cache data source credentials features. (power bi will cache the credentials to the local when you use data connector to get data)
When you use this data connector to get data from same data source and switch between multiple accounts, they may cause the issue. (the cached credentials conflict with new credential, you can clean up the cached data to use new credential, but it will also affect the usages)
For this scenario, current I haven't found methods to resolve this issue. Perhaps you can try to use different data connectors to get data with different accounts, these different connector cached data should not conflict each other.

Regards,

Xiaoxin Sheng

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

Find out what's new and trending in the Fabric community.

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.