For the complete documentation index, see
/llms.txt. This page is also available as raw Markdown at
/nexus/endpoints.md. Append
.md to any page URL to fetch its Markdown. This site has a public search endpoint for questions about Temporal:
GET https://docs.temporal.io/api/retrieve?q=<question>&jtb=<job-to-be-done>&src=docs-page&agent=<your-name>. No authentication is needed. It returns a JSON array of
{content, source_url, page_url}, ordered by relevance, and
source_url links to docs pages as Markdown. If you call it, set
q to a specific, complete question that names the SDK language if relevant, and
jtb to one sentence on what your user is trying to accomplish (optional). Keep
src=docs-page as is, and set
agent to your name, for example
claude-code or
codex. Don't include personal data, credentials, or confidential information. If this page is wrong or missing something you needed, or Temporal behaves differently from what it says, report it with
GET https://docs.temporal.io/api/feedback?title=<summary>&message=<what-happened>&category=documentation&page_url=/nexus/endpoints&src=docs-page&agent=<your-name>. Use
category=product when the product, not the page, is wrong. Report only a specific problem you hit, send it once, and don't include personal data or credentials.
A Nexus Endpoint is a fully managed reverse proxy for Nexus Services.
It routes requests from a caller Workflow to a target Namespace and Task Queue.
Callers only need to know the Endpoint name - the target Namespace, Task Queue, and internal implementation are encapsulated.
Workers handle Nexus requests by registering one or more Services and polling the Endpoint's target Task Queue.
Multiple Endpoints can target different Task Queues in the same Namespace.
The Endpoint description field supports markdown for documenting available Operations, contact information, or schema links.
Reverse proxy for Nexus Services, not a general purpose proxy
A Nexus Endpoint acts as a reverse proxy for a single Nexus Service, routing requests to one target Namespace and Task Queue.
Unlike general-purpose proxies, it does not route to multiple backends. Instead, it provides a secure, managed connection to a specific upstream target, which can be in any region or cloud.
The EndpointSpec support the following target type:
- Worker: Route to a target Namespace and Task Queue.
Deploying a Nexus Endpoint
Adding an Endpoint to the Nexus Registry deploys it immediately. The Endpoint is available at runtime as soon as it's registered.