installs_pending

GET

/consent/{request}

const url = 'https://api.canopyhq.dev/consent/example';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://api.canopyhq.dev/consent/example \
  --header 'Authorization: Bearer <token>'

Authorizations

console_token

Parameters

Path Parameters

request

required

One proposal. Minted per POST, so two proposals of one document are two requests, each with its own secret and its own key.

string

The request the proposal was minted under.

Responses

200

What the vendor proposes, and for an update the currently installed document it replaces.

application/json

The proposed document, with the currently installed document for an update.

object

description

required

string

name

required

string

tools

required

Array<object>

object

description

required

string

input_schema

required

name

required

string

output_schema

required

result_limit

One of:

null
string

null

A byte count written with an optional binary unit, such as 16KiB.

string

timeout

string | null

appdoc

required

The vendor document version, read through the same shape chain as storage.

integer format: int32

current

One of:

null
object

null

The composed document served to an install or the console.

object

install

One of:

null
string

null

tenant

required

What the tenant lands at consent. Inference must be selected; an empty policy list allows every tool and an empty extra-tools list adds nothing. The policies name tools as the model sees them and compile in policy, against the surface the resolved connections give, which is not this type’s to know.

object

extra_tools

Array<object>

A tool the tenant brings that the vendor did not state: a pre-registered remote, such as an MCP server the tenant already links to.

object

connection

required

string

tool

required

The name by which an MCP server identifies and invokes a tool.

string

inference

required

string

policies

Array<object>

The tenant’s rules for one tool, named by the name the model sees.

object

allow

The tool enable. Off, nothing else here matters.

boolean

items

Array<object>

One condition: <allow|deny> if <arg> <op> <operand>.

object

arg

required

string

effect

required

string

Allowed values: allow deny

required

string

Allowed values: is is_not in not_in lt gt

operand

required

One of:

object
object

object

value

required

posture

What a tool’s allow items do: nothing under Permissive, where only deny items bind; bind under Restrictive, where a conditioned arg must satisfy one of them.

string

Allowed values: permissive restrictive

project

Args projected for evidence alone, conditioned or not.

Array<string>

tool

required

string

vendor

required

A vendor document with its wire version beside the vendor fields.

object

description

required

string

name

required

string

tools

required

Array<object>

object

description

required

string

input_schema

required

name

required

string

output_schema

required

result_limit

One of:

null
string

null

A byte count written with an optional binary unit, such as 16KiB.

string

timeout

string | null

appdoc

required

The vendor document version, read through the same shape chain as storage.

integer format: int32

Example

{
  "current": {
    "tenant": {
      "policies": [
        {
          "items": [
            {
              "effect": "allow",
              "op": "is"
            }
          ],
          "posture": "permissive"
        }
      ]
    }
  }
}

401

No console token, or one that did not verify.

404

No such request, or it lapsed or was granted already.