Unverified50% confidenceCautionExact time
The authentication method for Custom Connectors is limited to API-key; more complex authorization mechanisms such as OAuth are not yet supported.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
9/23/2026
First Seen
Valid until: 12/22/2026
Sources
Related Entities
Related Claims
UnverifiedPure API Key direct connection mode does not trigger ZCode's upload link; the problem is concentrated in OAuth login scenarios.73% similarUnverifiedOn services that support OAuth, the OAuth authorization flow should be preferred over directly requesting static API keys.73% similarUnverifiedSupporting 9 platforms simultaneously means managing multiple sets of API keys or OAuth authorizations70% similarUnverifiedOAuth 2.0 only addresses authorization, while OIDC adds a standardized identity authentication layer on top of it, introducing an ID Token—typically in JWT format—to carry user identity information.70% similarUnverifiedThe technical foundation behind Connectors is OAuth authorization and API integration, which goes through official API channels and differs from traditional RPA's screenshot-simulated clicking, resulting in higher stability.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/942230API
curl https://kongchang.com/api/v1/knowledge/claims/942230MCP
get_claim(id=942230)