SMAO API Documentation
Public APITools

Get a tool

GET
/tools/{tool_id}

Authorization

bearerAuth
AuthorizationBearer <token>

API key in the Authorization: Bearer <key> header. Keys are created in the SMAO dashboard (Settings → API Keys).

In: header

Path Parameters

tool_id*string
Match^[a-f0-9]{24}$

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/tools/65f8fa6f1a9d8e0012ab34cd"
{  "data": {    "id": "string",    "tool_key": "string",    "display_name": "string",    "description": "string",    "parameters": {},    "execution_type": "webhook",    "source": "custom",    "webhook": {      "url": "http://example.com",      "method": "GET",      "headers": {},      "body_template": "string",      "timeout_ms": 500,      "retry_count": 0    },    "integration": null,    "auth": {      "type": "apiKey",      "header_name": "string",      "username": "string",      "has_secret": true    },    "created_at": "2019-08-24T14:15:22Z",    "updated_at": "2019-08-24T14:15:22Z"  }}

Create a tool POST

Creates a new webhook-type tool. `tool_key` must be unique within your organization; reuse returns 409. Auth secrets are stored AES-256-GCM encrypted and are never returned — submit them on create / PATCH to set or rotate. Integration-type tools must be created via the dashboard (OAuth flow) and cannot be created through the public API in v1.

Update a tool PATCH

Partial update — only included fields are changed. `tool_key` and `execution_type` are immutable (create a new tool instead). To rotate an auth secret, submit a full `auth` object with the new value; the previous secret is overwritten in place.