Show this access

The access this call is made with: account, main or sub access, authentication, expiry, what it may do.

RReadIdempotentbeta
Tool
manitu_access_geton https://mcp.manitu.de/mcp
POST
/v1/access/geton https://api.manitu.de
Try it
readOnlyHint truedestructiveHint falseidempotentHint trueopenWorldHint false

Tells which manitu customer account this connection works in, and through which access: the account id (it is also the customer number the customer knows), the access id (main or sub access), how the connection authenticated, and until when; for a key also what it may do (access_level: read only, write, or write without confirmation) and which ways in it can use (rest, mcp). Call it first when you need to know whose account you act in, before telling the customer which account a later answer refers to, or when a change is refused and you need to know whether this key may change anything at all. It returns no contact or contract data - no name, no address, no products.

Takes no arguments.

account_idintegerrequired

The customer account - its id is also its customer number.

account_user_idintegerrequired

The access on that account this call is made with.

credential_typestringrequired

What this call was made with.

One of session apikey oauth
auth_strengthstringrequired

How the access authenticated.

One of password tfa token oauth
expires_atstring | nullrequired

When the credential ends at the latest (ISO 8601), or null.

access_levelstring | nullrequired

What a key may do: read only; write, with what needs a confirmation refused; or write without confirmation. null for a session.

One of read write write_unconfirmed null
facadestring | nullrequired

The way this call came: rest or mcp; null if not known.

One of rest mcp null
usable_channel_listarray of stringrequired

The ways in this credential can use now: rest and mcp for a key; panel for a session - its sign-in to the customer panel, which also covers calls made with the session over REST (a session never works over MCP). A way not listed is closed for it - the customer sets the ways in in the customer panel.

One of X-API-Key, Authorization: Bearer … - never more than one in a request. More

No fields - send {} or no body.

account_idintegerrequired

The customer account - its id is also its customer number.

account_user_idintegerrequired

The access on that account this call is made with.

credential_typestringrequired

What this call was made with.

One of session apikey oauth
auth_strengthstringrequired

How the access authenticated.

One of password tfa token oauth
expires_atstring | nullrequired

When the credential ends at the latest (ISO 8601), or null.

access_levelstring | nullrequired

What a key may do: read only; write, with what needs a confirmation refused; or write without confirmation. null for a session.

One of read write write_unconfirmed null
facadestring | nullrequired

The way this call came: rest or mcp; null if not known.

One of rest mcp null
usable_channel_listarray of stringrequired

The ways in this credential can use now: rest and mcp for a key; panel for a session - its sign-in to the customer panel, which also covers calls made with the session over REST (a session never works over MCP). A way not listed is closed for it - the customer sets the ways in in the customer panel.

200Success.400The request does not match the declared input schema.401No credential was presented, or it was not recognised.403The credential is not permitted to use this operation.500The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.503The channel this operation forwards through is unavailable.