Proxy (passthrough)

When the operation you need isn't a catalog action, use the proxy: a governed passthrough to the provider's own REST API. Nolixan injects the connection's credentials, applies policy, and audits the call — you just specify the provider endpoint.

POST /api/v1/proxy/repos/acme/widgets/issues
provider-config-key: github
connection-id: acme
 
{ "title": "Found by an agent", "body": "..." }

• The path after /proxy/ is the provider's endpoint; the HTTP method is the method you use.
• provider-config-key (required) and connection-id (optional — auto-resolved if you have one connection for the provider) are sent as headers.
• Query params and the body are forwarded to the provider; the provider's status, body, and headers are passed back.

You can also address the connection in the path:

POST /api/v1/proxy/connection/{connection_id}/repos/acme/widgets/issues

Governance on passthrough

Proxy calls are gated too. Each is evaluated under a synthetic action name {method}_proxy (e.g. post_proxy, delete_proxy), and writes (POST/PUT/PATCH/DELETE) are treated as write risk — so default-deny on writes and approvals apply to passthrough exactly as they do to catalog actions. A denied proxy call returns 403; an approval-required one returns 202.