Unanswered

Certifying custom connector and the API key

(0) Share

Report

Posted on by ishraqiyun77

166

I've been working on a connector for a web app that we use that didn't already exist. I want to get it certified by Microsoft so that it is available for others to use. A couple questions I have, as I haven't done this before:

Currently it uses my API key for the other web app: what I submit wouldn't utilizing that API key, correct?
Whoever uses the connector would need to supply their own API key: at what point do they have to provide theirs?

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

v-yamao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @ishraqiyun77 ,

About #1, please check the following doc:

https://docs.microsoft.com/en-us/connectors/custom-connectors/create-web-api-connector

About #2, please check the following doc:

https://docs.microsoft.com/en-us/connectors/custom-connectors/share

Hope this would be helpful.

Best regards,

Mabel

Was this reply helpful? Yes No
ishraqiyun77 166 on at

Like (0)

Report
Copy link

Link copied!

Yep, have read both of those and neither answers my question. In playing around, it looks like when someone goes to use the custom connector I make (in a Flow or what not), they will be prompted to enter their own API key. Is this the case? At least when I added a Twitter connector, for experimiting, it prompted me for my credentials. I assume if someone adds my custom connector, they will be prompted to enter their own API key. Really isn't clear from the documentation.

Was this reply helpful? Yes No