GET · Support

Get the support contact channels

GET


          /api/v1/support/contact

Try it

R Read

Scope read:account

This scope is inferred from the method and the endpoint's group — the OpenAPI document does not carry one per operation. The wire is authoritative; whoami reports what your token actually holds.

Description

Returns {email, help_center_url, channels:[…]}.

Parameters

This operation takes no parameters. Authentication is the bearer token in the Authorization header.

Responses

The specification does not describe this response body; the note in the rail says what to expect. Every non-2xx response is an RFC 7807 problem with a stable code.

Commonly returned errors

The codes this operation reaches on its own path: the auth stack, its own validation and ownership checks, and the transport. Not a closed set — a shared code from the full registry can still surface. Each links to the code’s own page, the same URL its type dereferences to.

401 No token was presented, or the token is revoked, expired or unknown.

unauthorizedtoken_expiredtoken_revoked

403 The token lacks a required scope, or this account does not own the resource.

insufficient_scope

429 The rate limit for this token is exhausted. See `Retry-After`.

rate_limited

500 Something went wrong on our side. The failure is logged against `requestId`.

internal_error

GET /api/v1/support/contact

curl -X GET "https://mcp.inleed.com/api/v1/support/contact" \
  -H "Authorization: Bearer inl_live_…"

<?php
$res = Http::withToken($token)
    ->get('https://mcp.inleed.com/api/v1/support/contact');
$data = $res->json();

const res = await fetch(
  "https://mcp.inleed.com/api/v1/support/contact",
  {
    method: "GET",
    headers: {
      Authorization: "Bearer " + process.env.INLEED_TOKEN,
    },
  },
);
const data = await res.json();

Set INLEED_TOKEN to a token minted in the client area.

Open in the try-it console →