> For the complete documentation index, see [llms.txt](https://docs.ecotone.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecotone.tech/messaging/messaging-concepts/message-endpoint.md).

# Message Endpoints/Handlers

![](/files/-LwTm_VjFNev5-Ms_uDO)

Every piece of code that processes a message in Ecotone is an **Endpoint**. `Command Handlers`, `Event Handlers`, `Query Handlers` are the bus-facing flavors — wired to the Command/Event/Query buses. **Internal Handlers**, **Splitters**, and **Routers** are the lower-level flavors — they sit on a named channel and aren't reachable from a bus.

Reach for the lower-level family when:

* You're building a step inside an Orchestrator that shouldn't be invokable as a Command from outside.
* You're processing the result of an `outputChannelName` chain.
* You need a router or splitter inside a workflow.

If your code is the entry point for an HTTP request or a public domain action, use a Command/Event/Query Handler. If it's a step in a pipeline, use an Internal Handler.

You don't implement endpoints directly or build messages by hand — you write plain PHP objects, and Ecotone connects your domain code to the messaging infrastructure through declarative configuration.

All Message Handlers follows simple low level interface

```php
interface MessageHandler
{
    /**
     * Handles given message
     */
    public function handle(Message $message): void;
}
```

{% hint style="info" %}
`Command Handlers, Event Handlers, Query Handlers` are also Endpoints.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ecotone.tech/messaging/messaging-concepts/message-endpoint.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.