Custom Connection - API with URL - Definition - Create Connector error

[Harini]

I have a parameterized API URL:

https://api.healthyme.com/v1/groceries/{fname}/fresh/{fdesc}?user_key=1234

eg: https://api.healthyme.com/v1/groceries/fruits/fresh/apple?user_key=1234

For input = Fuji Apples. The url has to become eg: https://api.supermarket.com/v1/groceries/fruits/fresh/apple?user_key=1234

For input = Washington Apples. The url has to be same eg: https://api.supermarket.com/v1/groceries/fruits/fresh/apple?user_key=1234

For input = Oreo. The url has to be same eg: https://api.supermarket.com/v1/groceries/Biscuits/fresh/Oreo?user_key=1234

When I try to create a connector I get this this:

Specified swagger has the following errors: 'Definition is not valid. Error: 'Error : type : The property 'type' is not valid. If this property is an extension, its name must begin with "x-". ## Error : features : The property 'features' is not valid. If this property is an extension, its name must begin with "x-". ## Error : results : The property 'results' is not valid. If this property is an extension, its name must begin with "x-". '

[Carsten_Growth]

I would recommend building your custom API connection first with a tool like Postman. You can then safe the Postman collection after you´ve successfully tested your API connections and import them. This should avoid yours having issues with the swagger definition file.

[Harini]

It is an Open API, available on the internet... I did not create it... so does your suggestion still hold good?

[v-xida-msft]

Hi @Harini ,

How do you create your custom connector? Through "Import an OpenAPI  file" or "Import an OpenAPI from URL"?

Based on the screenshot that you mentioned, I think there is something wrong with your imported OpenAPI definition file.

As an alternative solution, please consider create your custom connector from Blank as below:

Then specify the Host and Base Url for your custom connector as below:

Then you may need to specify a proper authentication way for your custom connector, if this Rest API you want to access do not need any authentication, please just specify "No authentication" option within the Security Tab.

Within the Definition tab, click "New action" option to add action path within your custom connector. Configure it as below:

Then you could edit the "User_Key" query parameter and set a default value for it as below:

After that, you need to specify a proper response Body for this action path. Just click the "Default" response, then click "Import from sample" option, then type proper JSON Schema within the Body property:

Note: In order to get proper response for this HTTP request, you could test this request using Postman Tool, then copy the Response result into above Body property.

More details about creating a custom connector in PowerApps, please check and see if the following video could help in your scenario:

https://www.youtube.com/watch?v=dBCS1nPsDiE&t=1s

Best regards,

[Harini]

Thank you Kris Dai, I will try it out and update here 😄

[v-xida-msft]

Hi @Harini ,

Sure. Please take a try with it, check if the issue is solved.

If you have any questions about custom connector, please feel free to let me know here.

Best regards,

[Harini]

Hello,

The custom connector creation happened. I tried using it and I got the message as shown in the attachment. does it mean that for community powerapps users, using an open API as custom connector is not allowed?

[Harini]

Hello Team, 

The connector is now being created. I am getting this prompt though when I try to use it.

Is the usage of a custom connector with open API allowed to be used in powerApps only in premium subscription?

I have the community subscription.

[v-xida-msft · Accepted solution]

Hi @Harini ,

Currently, the Custom connector is a Premium connector in Power Apps/Power Automate, which requires standalone Power Apps license or Power Automate license to use it (PowerApps Plan 1 license at least).

But if you signed up a community plan for your account, you could create and use unlimited custom connectors within your Community Environment. Please check the following article for more details:

https://docs.microsoft.com/en-us/powerapps/maker/dev-community-plan#which-features-are-included-in-t...

If you want to use custom connectors in Production or Trial Environment, you must own standalone Power Apps license (PowerApps Plan 1 license at least) to use custom connector.

Best reagrds,

[elos]

I am getting this error and I have "Power Automate per user with attended RPA plan" and "Microsoft Power Apps Plan 2"

The error message is extremely misleading if it boils down to licenses