POST/api/publication/start
Authentication: Hussteer session (cookie)
Response200 OK
No need to reinvent your stack.
HTTP, JSON and an OpenAPI specification. Hussteer builds on the technologies your teams already use.
REST
AvailableSimple by design.
Standard HTTP requests, structured JSON responses and explicit error codes.
OpenAPI 3.1
AvailableThe specification is published.
The API contract is served at /openapi.json and /openapi.yaml, ready for your tooling.
Publishing
AvailableThe first domain opened.
Start a distribution, follow its status, read its history, retry a failing channel.
Access keys
ComingControlled access.
Key-based authentication, tied to an agency and revocable, is still to be delivered. Calls today use a Hussteer session.
Hussteer becomes the crossing point.
Your data can move between Hussteer, your website, your internal tools and the services connected to your agency.
The Publishing domain is open today. Other resources will be exposed step by step.
One API. Many possibilities.
Connect your own services without rebuilding your business around a new tool.
Follow your listings
AvailableKeep an eye on distribution.
Use the statuses — queued, running, success, error — to track how your listings are doing.
Retry a channel
AvailableFix without going back to the screen.
Resume a failed distribution from your own tools, channel by channel or all at once.
Check before sending
AvailableValidate the record before publishing.
Check that a property meets the publishing conditions and get the list of what is missing.
Build automations
AvailableTrigger actions without manual steps.
Chain publishing calls from your own workflows.
Connect your website
ComingYour portfolio feeds your shop window.
Read access to properties and mandates is among the domains still to open.
Use your data
ComingTurn activity into insight.
Exporting to your dashboards currently goes through the CSV files in the settings.
A preview of a capability to come — this screen does not exist in the product yet.
A key will be tied to a single agency and open only its resources.
One key. One agency. One scope.
Calls are currently authenticated with a Hussteer session: the API sees exactly what the signed-in user sees, within their agency's scope.
Key-based authentication — creating, using and revoking from the settings — is the next step.
Create: generate a key from the agency settings.
Use: authenticate the connected service's calls.
Revoke: cut off an access that is no longer needed.Capability to come: these events exist internally but are not delivered yet.
Payload
Stop asking. Hussteer tells you.
Webhooks will let your applications react when something happens in Hussteer, instead of polling the API.
The Mandates domain events already exist internally.
Delivering them to your services is still to be built.
In the meantime, the status endpoint reports where a distribution stands.Documentation should follow the product.
Hussteer's technical reference is built on OpenAPI 3.1, so the documentation stays aligned with what the API actually accepts and returns.
API reference
Endpoints, parameters, responses and errors.
OpenAPI
A description your tooling can read directly, served at /openapi.json.
Examples
Ready-to-copy calls in cURL, JavaScript and Python.
Connected does not mean open to everything.
API access follows the same partitioning and control principles as the rest of the platform.
Limited access
A call only sees its own agency's resources: the rule is enforced by the database, not by the API.
Revocation
A session cuts off immediately, and future keys will follow the same principle.
Traceability
Sensitive actions are logged and available from the agency settings.