API reference · Tools

Credential hint

Confirms which credential is stored, without returning it.

get/api/tools/{tool_id}/credential
Authentication
Bearer token
Retries
Safe to repeat
Body
None
Version
2026-09-03

At most four trailing characters, which is enough to tell "the key I rotated last week" from "the key I rotated today" and not enough to be worth anything to anyone who obtains it.

Path parameters

  • tool_idstring (uuid)required

Responses

  • 200OKapplication/json

    Message

    • messagestringrequired
    • okboolean

      Default: true

    5 response headers
    RateLimit-Limit

    Requests permitted in the current window.

    RateLimit-Remaining

    Requests left in the current window. Back off before it reaches 0.

    RateLimit-Reset

    Seconds until the current window resets.

    X-API-Version

    The dated version of the API contract that served this response, e.g. 2026-09-03. Pin against it; it changes only when a response shape changes incompatibly.

    X-Request-ID

    Quote this in a support request to identify the call.

  • 422Validation error

    The shared error envelope, served as application/problem+json with error.code set to validation_error. Its details name each field that failed and why.

Example request

curl
curl "https://api.integrable.cloud/api/tools/$TOOL_ID/credential" \
  -H "Authorization: Bearer $INTEGRABLE_API_KEY"

Set INTEGRABLE_API_KEY and the path variables first. The same call from the TypeScript or Python SDK takes the same fields.

Example response

200 OK · application/json
{
  "message": "string",
  "ok": true
}

Generated from the schema above — the shape is exact, the values are placeholders.

Errors

Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:

  • validation_error · 422The payload was well-formed JSON but failed schema validation.
  • unauthenticated · 401The request carried no API key, or one the API could not verify.
  • forbidden · 403The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.
  • rate_limited · 429Too many requests in the current window. The limit is per workspace, and some endpoints add a per-bot limit on top.

More Tools endpoints

Something here wrong or missing? Tell us — the documentation and the API are maintained by the same person, so a correction is a fix rather than a ticket.

Building on it? Start on the free plan — no card — and call the same API the dashboard uses.

Start free