> 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/modelling/command-handling/business-interface.md).

# Business Interface

Business Interfaces for type-safe messaging in Ecotone PHP

You inject `CommandBus` into a controller. Three controllers later, every call site has the magic-string `'ticket.create'` and a `new CreateTicket(...)`. The bus signature is `mixed → mixed`. There's no single place that documents what your domain can do, no IDE help, and refactoring the `CreateTicket` class is a search-and-replace across the codebase.

A **Business Interface** is your domain's typed API: `interface TicketApi { public function create(CreateTicket $cmd): TicketId; public function close(#[Identifier] string $id): void; }`. Ecotone delivers the implementation. Your controllers, console commands, and subscribers all depend on `TicketApi` — and onboarding a new developer becomes a one-file question: "what can the Ticket module do?".

This works for sending commands, executing queries, and operating on databases — keeping your application code focused on intent rather than wiring.

{% content-ref url="/pages/pQmOc5Wucm8dkY9ZQaej" %}
[Introduction](/modelling/command-handling/business-interface/introduction.md)
{% endcontent-ref %}

{% content-ref url="/pages/1ZR8RZrEnX447XWYz39m" %}
[Database Business Interface](/modelling/command-handling/business-interface/working-with-database.md)
{% endcontent-ref %}

## Materials

### Demo implementation

* [Business Interface — Service Activator, Routing and Asynchronous](https://github.com/ecotoneframework/quickstart-examples/tree/main/BusinessInterface)

### Links

* [Message Based — Business Oriented Interfaces](https://blog.ecotone.tech/message-based-business-oriented-interfaces/) \[Article]
* [Working with Databases using DDD Mindset](https://blog.ecotone.tech/working-with-databases-using-ddd-mindset/) \[Article]


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ecotone.tech/modelling/command-handling/business-interface.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.