You shared API documentation with a staffing partner in March, as a PDF, and in June you renamed a field. Their developer's first live request for a new starter comes back 422, and two teams spend the afternoon comparing a PDF with what your API now accepts. EchoRelay writes that documentation from the configuration it serves, so you share one link and stop keeping a second copy.
Nobody on your team has to remember the docs when an endpoint changes, and a partner who opens the link sees today's fields instead of March's.
Your endpoint rules are already the documentation
In EchoRelay, an endpoint is the address your callers send a request to, together with the rules for that request. A line groups endpoints into one API version. The documentation is built from those rules: each endpoint's method and path, the query, header, path and body fields it takes, which of them are required, and the limits you set, such as allowed values, formats and lengths.
The result is a readable reference and an OpenAPI document, the standard machine-readable description of an API. For the staffing partner, POST /new-starters on line v1 might list work_email as a required email address and contract_type as one of permanent or fixed_term. Write a Description on a field in the endpoint form and it appears beside that field in the docs, which is the right place to say that start_date means the first paid day.
Partners read what is live, never what you are still editing
The docs come from what you have published. Edit an endpoint and the change waits in a draft, out of the docs, until you publish it. Then the docs change with it, and there is nothing to export or send. An inactive line lists no endpoints, so nobody gets instructions for an address that would refuse them.
To build v2 beside a live v1, duplicate the line. The copy starts inactive and not shared, and each line has its own docs and its own address, so partners on v1 keep a page that still describes v1.
The docs stop at your front door
The page describes what a caller sends you and nothing behind it. Which targets receive the request, where they are and the credentials used to reach them all stay out. The staffing partner learns how to send a new starter. They do not learn which payroll provider it reaches, or how.
Reading the page also gives nobody the means to call your API. It says a request needs an API key and contains none, so you still decide who can send.
Share it with one partner, or with everyone
Inside your project, the Docs button on an endpoint opens the documentation for its line. There is nothing to set up.
For someone outside the project, open the line and pick a level under Documentation sharing. A line starts at Not shared, where only people in the project can read its docs. Anyone with the link gives you a private address that opens without an account and asks search engines and AI crawlers to stay out. Public gives the line an address that anyone can read, and search engines and AI assistants can find.
The staffing partner needs the link, so send them the address the panel shows. Add /openapi.json to it for the machine-readable document, which their developer can load into an API client or code generator. If the link ends up somewhere it should not be, Replace link gives you a new address and the old one stops working at once. Publishing a change to the line keeps the address, so your partner never needs a new link because a field changed.
The management tools can set the level too, so an agent that publishes a change can share it. An agent asked to share a line should use the link, and it cannot make a line public unless you have explicitly approved that.
The same link saves the same afternoon when a helpdesk vendor starts sending you tickets. Your next partner starts from the fields your API accepts today, and your engineers keep the time they would have spent answering questions about an old PDF. The guide to lines shows where the setting is.