---
title: "Developers: API, MCP server, webhooks and forms | SalexHub"
description: "The REST API and the MCP server are open, with webhooks, embeds, the form endpoint, the tracking script and a messenger bridge, all on one registry of tools."
url: "https://salexhub.com/developers"
---

# One registry for the Agent, workflows and the API.

Each of the registry's 523 tools meets your approval rules whether the Agent, a workflow or an API key calls it, and the Agent and a key are also checked against a role. Here is what you can build on today.

## Open today

- **REST API**: One operation for each of the registry's 523 tools, at app.salexhub.com/api/v1, with a key you issue in Settings as the bearer token. The OpenAPI document is served beside it. A key acts at the weaker of its role and its creator's, and calls only the tools that need no approval. [Read the docs](https://salexhub.com/docs/developers/api-keys)
- **MCP server**: The same registry for agents that speak MCP, at the same address and under the same permissions and approval rules. The compact listing lets an agent look a tool up and then call it; the flat one lists every tool the key may call. [Read the docs](https://salexhub.com/docs/developers/api-keys)
- **Webhooks**: Signed events to your HTTPS endpoint when a record is created or updated, and when a document moves, such as an accepted quote or an issued invoice. HMAC-SHA256 with a timestamp; retries after 5 minutes, 30 minutes, 2 hours and 12 hours; every attempt listed. Owners and Admins add them in Settings. [Read the docs](https://salexhub.com/docs/developers/webhooks)
- **Embeds**: A script tag and a placeholder on your page, or JSON and HTML from one address. Read-only and keyless, showing only record types an admin opened for embeds, only the fields you name, never personal data. [Read the docs](https://salexhub.com/docs/developers/embeds)
- **Form endpoint**: Your site's own form posts its fields to one address, and each submission lands in your organization as a contact. Forms come with the Marketing hub. [Read the docs](https://salexhub.com/docs/developers/forms)
- **Tracking script**: One script for cookie-free page views and your own events, and identifying a visitor who gives an email. It comes with the Marketing hub. [Read the docs](https://salexhub.com/docs/developers/tracking)
- **Messenger bridge**: Connect a messenger by running a small bridge that posts conversations to your organization with a channel key. Replies go back by signed push or by pull. [Read the docs](https://salexhub.com/docs/developers/messenger-bridge)

## Built, not published

[API keys](https://salexhub.com/docs/developers/api-keys) are issued in Settings: they act at the weaker of their role and their creator's, expire in 30, 90 or 365 days, and are accepted by the REST API and the MCP server. The AI Gateway API takes keys of its own: see [AI Gateway keys](https://salexhub.com/docs/developers/api-keys#ai-gateway-keys).

- **TypeScript SDK** (coming soon): A generated client for the 523 operations, built from the same OpenAPI document the API serves. It lives in the product's repository and is not published to a package registry yet.

## Why one registry

- **One registry for the Agent, workflows and the API**: How the Agent, workflows and API keys act through the same tools, and which checks apply to whom. [Read the post](https://salexhub.com/blog/one-registry)

## Talk to us

- **Building on SalexHub**: Tell us what you want to connect to your organization. [Write to start@salexhub.com](mailto:start@salexhub.com?subject=Developers)

---

The same page for people: https://salexhub.com/developers. Index of this site for agents: https://salexhub.com/llms.txt