Get a custom tool

get a single custom tool.

GET https://api.centerfy.ai/webhooks/inbound/custom-tools/:id

Headers

Header	Required	Value	Description
`x-api-key`	Yes	your sub-account API key (cfy_…)	authenticates the request; or Authorization: Bearer `<key>`.

Path parameters

Name	Type	Required	Description
`id`	`string (uuid)`	Yes	the custom tool id.

Example

curl -X GET "https://api.centerfy.ai/webhooks/inbound/custom-tools/{id}" \
  -H "x-api-key: $CENTERFY_API_KEY"

import { CenterfyClient } from "@centerfy/sdk";

const centerfy = new CenterfyClient({ apiKey: process.env.CENTERFY_API_KEY! });

const result = await centerfy.customTools.get("<toolId>");
console.log(result);

centerfy customTools get <toolId>

MCP tool: centerfy_custom_tools_get (see MCP server)

Response

{
  "status": "success",
  "custom_tool": {
    "id": "a1b2c3d4-5555-6666-7777-888899990000",
    "name": "lookup_order",
    "description": "Look up an order by id",
    "url": "https://api.example.com/orders",
    "method": "GET",
    "auth_required": true,
    "has_api_key": true,
    "parameters": [
      {
        "name": "order_id",
        "type": "string",
        "description": "The order id",
        "required": true
      }
    ],
    "created_at": "2026-06-01T12:00:00.000Z",
    "updated_at": "2026-06-10T09:30:00.000Z"
  }
}

Errors

400 — if id is not a valid uuid.
404 — if the custom tool does not exist.
500 — on error.

Notes

The stored api_key secret is never returned — has_api_key is returned instead.