Skip to content
GitmoapAPIBeta
Integrateprovider-catalog
GET/marketplace/categories

List the marketplace category taxonomy with live provider counts.

list_marketplace_categories
  • provider_catalog:read
    A token needs the provider_catalog:read scope: Browse the provider catalog and marketplaceGranted by read_api, write_api.Every operation this scope unlocks
  • Single-resource

    x-gitmoap-isolation: {"kind":"single_or_self_scoped"}

Returns every marketplace category with its display label and the number of providers you can see in it. Every category is listed, including empty ones, and a provider with several categories counts in each. Private providers are counted only for members of the organization that owns them. Open to any signed-in caller.

Responses

200Every category with its label and provider countapplication/json
  • itemsarray of CategoryCount
    • The CategoryCount schema
    • categoryCategorysource-controlbuildtestqualitysecurityreleasedeployinfrastructurenotifyotherA marketplace discovery category a provider is listed under. A provider declares one to three, and they describe where it appears when browsing, not what its capabilities do — a provider in infrastructure may still offer build and deploy capabilities.
    • labelstring
    • provider_countinteger · int640–∞
200 exampleSynthesized example
{
"items": [
{
"category": "source-control",
"label": "label-2919",
"provider_count": 1
},
{
"category": "source-control",
"label": "label-7738",
"provider_count": 7
}
]
}
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 reason or code.
    • fieldstring or nulloptionalOn a 400 that 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 on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): 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-65c6",
"message": "Inline scalar newtypes but keep their brand"
}
}
403Forbidden — the caller's access level or token scope is insufficientapplication/json
Error codes
  • FORBIDDENYou are signed in but may not do this here; reason names the permission or the rule that refused it
  • INSUFFICIENT_SCOPEThe access token lacks the scope this operation needs; required_scope names 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 reason or code.
    • fieldstring or nulloptionalOn a 400 that 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 on code otherwise.
    • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
    • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): 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-94ea",
"message": "Inline scalar newtypes but keep their brand"
}
}

CLI

gitmoap provider-catalog list-marketplace-categories

Used in these guides