iii-http-invoked-functions

name	iii-http-invoked-functions
description	Registers external HTTP endpoints as iii functions using registerFunction(id, HttpInvocationConfig). Use when adapting legacy APIs, third-party webhooks, or immutable services into triggerable iii functions, especially when prompts ask for endpoint maps like { path, id } iterated into registerFunction calls.

HTTP-Invoked Functions

Use this pattern when iii should call external HTTP endpoints as functions.

Pattern selection rules

• If the task says "register HTTP endpoints with registerFunction", use this pattern.
• If the task asks for an endpoint list/map (for example { path, id }) and a loop over registerFunction, use this pattern.
• If the system being adapted cannot be modified, use this pattern.
• If the goal is exposing inbound routes that iii owns, use registerTrigger({ type: 'http' }) instead.

Core model

• registerFunction(id, HttpInvocationConfig, options?) registers an outbound HTTP-invoked function.
• trigger({ function_id, payload }) invokes it like any other function.
• Trigger payload is forwarded as the HTTP request body for JSON-based calls.
• Static headers from HttpInvocationConfig.headers are sent with the request.
• Auth headers are resolved at invocation time from environment variables.
• timeout_ms bounds the external call; if omitted, the worker invocation timeout applies.
• Non-2xx and network failures are treated as invocation failures.

Auth Modes

• HMAC: { type: 'hmac', secret_key: 'WEBHOOK_SECRET' }
• Bearer: { type: 'bearer', token_key: 'API_TOKEN' }
• API key: { type: 'api_key', header: 'X-API-Key', value_key: 'API_KEY' }