Required Scope(s) for /beta/platform-connectors Endpoint

[mcheek (Mark Cheek)]

Hello - I’m trying to upload a custom SaaS connector using the beta/platform-connectors endpoint which is used by the CLI, but I cannot seem to figure out what scope is needed to use this endpoint.

For uploading customizers, the cli uses beta/connector-customizers

The latter is in the beta api specs and lists sp:connector:manage as the required scope (as well as a user with ORG_ADMIN tied to that token)

The former is not listed in the API specs so there is no clear answer about what scope(s) are needed. sp:scopes:all of course works, but I do not wish to use such a broadly scoped PAT for a service user.

Has anyone figured this out?

[tyler_mairose]

Hey Mark,

I did some digging and the scope required to update connectors will be sp:connector-runtime:manage.

There are a few others that correspond to the other commands depending on what you’re trying to accomplish.

I will remind the connector team that these APIs should be documented with the specific scopes detailed as well.

[mcheek (Mark Cheek)]

I’m essentially trying to mimic the sail conn upload command the CLI does in a GitHub workflow but using APIs only instead of the CLI - so probably :manage is what I need

[mcheek (Mark Cheek)]

sp:connector-runtime:manage was the correct scope - thanks Tyler!