Service Integrations with Local Entrypoints
Use local services when the gateway and the handler should ship together in one worker project. The `services` array defines local module entrypoints that the
Last updated
Use local services when the gateway and the handler should ship together in one worker project. The `services` array defines local module entrypoints that the
Use local services when the gateway and the handler should ship together in one worker project. The services array defines local module entrypoints that the gateway imports at startup. This pattern keeps related code co-located and avoids the overhead of a separate Worker deployment.
Last reviewed: 2026-03-06
Use the service execution recipes when your routes need to call Worker code directly instead of proxying to an external HTTP endpoint. The gateway supports two patterns: local service modules bundled with the worker, and service bindings that call separately deployed Workers via Cloudflare bindings.
The service integration type imports a local JavaScript module from the worker project and calls its default export. The module ships in the same worker bundle.
The service_binding integration type calls a separately deployed Worker through a Cloudflare service binding. The target Worker must be deployed independently and bound in wrangler.toml.
Pre-process hooks run before the main integration and can short-circuit the request by returning a response. Use them for custom authorization, input validation, or request enrichment.
Post-process hooks run after the main integration returns and can modify the response. The Auth0 callback post-process hook is the most common use case.
When choosing between proxy and service execution, consider latency (service bindings avoid an external HTTP round-trip) and coupling (proxy keeps the backend independently deployable).
{
"services": [
{ "alias": "worker1", "entrypoint": "./services/endpoint1" }
],
"paths": [
{
"method": "GET",
"path": "/service",
"integration": {
"type": "service",
"binding": "worker1"
}
}
]
}This snippet defines a services array with one local entrypoint at ./services/endpoint1. The integration.binding field references the service alias, and the gateway calls the module's default export when a request matches this path.
If a service integration returns 500, confirm that the entrypoint path in the services array matches the actual file location relative to the worker root and that the module exports a default function.
If a service_binding integration returns a binding error, verify that the binding name in config matches the binding declared in wrangler.toml and that the target Worker is deployed.
If a pre-process hook does not short-circuit as expected, check that the hook function returns a Response object -- returning undefined or null lets the request continue to the main integration.
If post-process hooks are not running, confirm the hook config uses the correct binding and function field names and that the hook Worker is deployed and bound.
Last updated