Skip to main content
The iii-http worker exposes your functions as HTTP endpoints, turning a function into a REST route without standing up a separate web server.
This page is a quick tour. For path patterns, methods, headers, and response handling, see the iii-http worker docs.

Create endpoints

The http worker exposes an http trigger type that binds a function to an HTTP method and path; the function then runs on every matching request. Here is the full path from a running engine to a live endpoint.
  1. Start the engine, if it isn’t already running:
  1. In a worker, register the function you want to expose and bind an http trigger to it. If you do not have a worker yet, scaffold one with iii worker init, then edit its source. The handler receives the request (body, headers, method) and its return value becomes the response:
  1. Add the worker to start it, pointing at its directory:
For path patterns, request and response shapes, and the other configuration options, see the iii-http worker docs.

Calling the endpoint

Once the trigger is registered, call the path on the engine’s HTTP port (3111 by default):