Developer API

Connect approved business workflows to Uchiha-AI

The Uchiha-AI API enables eligible customers to submit requests, start configured workflows, retrieve results, and review usage from their own business applications.

Getting access

API access is available only to approved business customers on supported subscription plans. The applicable API features, endpoint availability, usage limits, and service scope are confirmed before activation.

Approved customers receive an API key and the current base URL through their Uchiha-AI workspace. API keys must be stored securely and must never be included in public client-side code.

API availability

This public documentation is an integration overview. The customer workspace contains the current base URL, enabled resources, identifiers, and plan-specific limits.

Authentication

Bearer API keys

Send the assigned API key in the Authorization header over HTTPS. Requests and responses use JSON.

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Accept: application/json

Core resources

Common integration operations

POST/v1/assistant-responses

Submit approved input to a configured AI assistant and receive a response.

POST/v1/workflow-runs

Start an enabled workflow using the supplied business data.

GET/v1/workflow-runs/{run_id}

Retrieve the current status and available result for a workflow run.

GET/v1/usage

Review available usage information for the current subscription period.

Example request

POST /v1/workflow-runs
{
  "workflow_id": "wf_example",
  "input": {
    "request": "Classify and route this inquiry"
  },
  "metadata": {
    "reference": "customer-reference"
  }
}

Example response

{
  "id": "run_example",
  "status": "queued",
  "workflow_id": "wf_example",
  "created_at": "2026-07-13T12:00:00Z"
}

Errors and limits

The API uses standard HTTP status codes. Typical responses include 400 for an invalid request, 401 for failed authentication, 403 for unavailable resources, 404 for unknown records, 429 for a plan limit, and 500 for a service error.

Rate and usage limits depend on the active subscription. Where available, response headers indicate remaining capacity and reset information.

Security requirements

Use HTTPS for every request.
Store keys only in secure server-side systems.
Rotate or revoke exposed credentials immediately.
Submit only information the customer is authorized to process.
Review AI-generated output before taking important action.

Developer support

Request API access

Contact Uchiha Itachi LTD to confirm your intended integration, plan eligibility, and expected usage.

Request API access Email developer support