Integrateprovider-settings
GET/groups/{group_id}/providers/{provider_id}
Get the setting in effect for one provider at a group
get_group_provider
provider_settings:read
A token needs theprovider_settings:readscope: View effective provider settingsGranted byread_api,write_api.Every operation this scope unlocks
The entry the group's listing gives for this provider: whether it is enabled, the version pinned
and the versions allowed, whether it follows the latest version and a newer one is published,
and whether the organization's policy accepts its tier. Each entry says where it was set; for a
setting made at a group you cannot see, who made it and where are withheld. Answers 404 when
neither this group nor any group above it has a setting for the provider. Anyone who can see the
group; on a public group that includes callers who are not signed in.
Parameters
Path
- group_idGroupId (string · uuid)Group id
- provider_idProviderId (string)Provider slug
Responses
200application/json
- allowed_versionsVersionPolicy
- enabledboolean
- inheritedboolean
- override_parentboolean
- provider_idProviderId (string)
- provider_tierProviderTierplatformverifiedcommunityprivateHow a pipeline provider is distributed and how much it is vouched for.
- publisher_verifiedbooleanWhether the owning publisher's namespace is verified.
- source_scope_idstring
- source_scope_typeScopeTypegrouprepository
- tier_acceptedbooleanWhether the provider's tier is accepted by the resolved per-org policy.
- track_latestbooleanWhether this install tracks the provider's latest published version. When
true, an unpinned node resolves tolatest_versionat trigger. - update_availablebooleanWhether a newer version than the install's
default_versionis published — a pure semver compare that never mutates the install (D5 K6). - default_versionProviderVersion (string) or nulloptional
- installed_atstring or nulloptional
installed_byActorSummary or nulloptional
- The ActorSummary schema
- emailstring
- idstring
- usernamestring
- avatar_urlstring or nulloptional
- latest_lifecycle_stateVersionLifecycleactivedeprecatedsunsetor nulloptionalLifecycle of
latest_version, so the UI can warn on a deprecated latest.Nonewhen not resolved (the trigger-validator path leaves itNone). - latest_versionProviderVersion (string) or nulloptionalThe provider's catalog
latest_version(excludes sunset; D3). - owning_group_idGroupId (string · uuid) or nulloptionalThe owning org (root group) of a Private provider;
Nonefor public tiers. Used by the trigger-time tier gate (own-org vs foreign-org private).
200 exampleSynthesized example
{
"allowed_versions": {
"kind": "any_published"
},
"enabled": true,
"inherited": false,
"override_parent": false,
"provider_id": "bac23080-3601-48b6-9316-0318a2fe289b",
"provider_tier": "platform",
"publisher_verified": false,
"source_scope_id": "ef947a2e-a9a6-4d51-8bd9-cf9c0a91af96",
"source_scope_type": "group",
"tier_accepted": false,
"track_latest": false,
"update_available": false,
"default_version": "default-version-13cc",
"installed_at": "2026-10-13T05:58:28Z",
"installed_by": {
"email": "mara@acme.example",
"id": "id-6cf5",
"username": "lin",
"avatar_url": "https://gitmoap.example/acme/7ec34619"
},
"latest_lifecycle_state": "active",
"latest_version": "latest-version-605a",
"owning_group_id": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69"
}
400Bad request — a path parameter is not a well-formed value of its typeapplication/json
Error codes
- BAD_REQUESTThe request is malformed: a parameter or a body field is not a well-formed value of its type
errorErrorBody
- The ErrorBody schema
- codestringThe coarse category, tied to the status:
NOT_FOUND,CONFLICT,INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all. - messagestringWhat went wrong, for a person. Written to be read, not parsed: match on
reasonorcode. - fieldstring or nulloptionalOn a
400that refused one field's value, the field, as its JSON path:email,items[0].name. Put the message under that input. Absent on every other error. - reasonstring or nulloptionalThe specific code, when the error has one:
LAST_ORGANIZATION_OWNER,BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and oncodeotherwise. - required_scopestring or nulloptionalThe scope the access token was missing, on
INSUFFICIENT_SCOPE. - violationsanyoptionalPresent on the structured-validation errors (
PROVIDER_VALIDATION_FAILEDper-node,PIPELINE_VALIDATION_FAILEDDAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
400 exampleSynthesized example
{
"error": {
"code": "code-6d80",
"message": "Pin a page's payload to the build that rendered it"
}
}
401application/json
Error codes
- UNAUTHORIZEDNo credential was sent, or the one sent is invalid, expired or revoked
errorErrorBody
- The ErrorBody schema
- codestringThe coarse category, tied to the status:
NOT_FOUND,CONFLICT,INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all. - messagestringWhat went wrong, for a person. Written to be read, not parsed: match on
reasonorcode. - fieldstring or nulloptionalOn a
400that refused one field's value, the field, as its JSON path:email,items[0].name. Put the message under that input. Absent on every other error. - reasonstring or nulloptionalThe specific code, when the error has one:
LAST_ORGANIZATION_OWNER,BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and oncodeotherwise. - required_scopestring or nulloptionalThe scope the access token was missing, on
INSUFFICIENT_SCOPE. - violationsanyoptionalPresent on the structured-validation errors (
PROVIDER_VALIDATION_FAILEDper-node,PIPELINE_VALIDATION_FAILEDDAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
401 exampleSynthesized example
{
"error": {
"code": "code-d85a",
"message": "Inline scalar newtypes but keep their brand"
}
}
403application/json
Error codes
- FORBIDDENYou are signed in but may not do this here;
reasonnames the permission or the rule that refused it - INSUFFICIENT_SCOPEThe access token lacks the scope this operation needs;
required_scopenames it - PERMISSION_REQUIREDYou need a permission you do not hold here; the message names it
errorErrorBody
- The ErrorBody schema
- codestringThe coarse category, tied to the status:
NOT_FOUND,CONFLICT,INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all. - messagestringWhat went wrong, for a person. Written to be read, not parsed: match on
reasonorcode. - fieldstring or nulloptionalOn a
400that refused one field's value, the field, as its JSON path:email,items[0].name. Put the message under that input. Absent on every other error. - reasonstring or nulloptionalThe specific code, when the error has one:
LAST_ORGANIZATION_OWNER,BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and oncodeotherwise. - required_scopestring or nulloptionalThe scope the access token was missing, on
INSUFFICIENT_SCOPE. - violationsanyoptionalPresent on the structured-validation errors (
PROVIDER_VALIDATION_FAILEDper-node,PIPELINE_VALIDATION_FAILEDDAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
403 exampleSynthesized example
{
"error": {
"code": "code-7864",
"message": "Pin a page's payload to the build that rendered it"
}
}
404application/json
Error codes
- NOT_FOUNDThe resource does not exist — or exists and you cannot see it: a private resource you have no access to answers exactly as an absent one does
errorErrorBody
- The ErrorBody schema
- codestringThe coarse category, tied to the status:
NOT_FOUND,CONFLICT,INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all. - messagestringWhat went wrong, for a person. Written to be read, not parsed: match on
reasonorcode. - fieldstring or nulloptionalOn a
400that refused one field's value, the field, as its JSON path:email,items[0].name. Put the message under that input. Absent on every other error. - reasonstring or nulloptionalThe specific code, when the error has one:
LAST_ORGANIZATION_OWNER,BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and oncodeotherwise. - required_scopestring or nulloptionalThe scope the access token was missing, on
INSUFFICIENT_SCOPE. - violationsanyoptionalPresent on the structured-validation errors (
PROVIDER_VALIDATION_FAILEDper-node,PIPELINE_VALIDATION_FAILEDDAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.
404 exampleSynthesized example
{
"error": {
"code": "code-9466",
"message": "Stream pipeline status into the run header"
}
}
CLI
gitmoap provider-settings get-group-provider
- --group-ididGroup id (id or group path)
- --provider-ididProvider slug