Ahotel doesn't run on one system. There's the PMS, the booking engine, the channel manager, the accounting package, and — if you're reading this — a CRM. Each one is good at its job, and each one is a little island. The bridges between them are usually a person: someone retyping a won deal into the PMS, exporting a CSV for the Monday report, copying a phone number from one tab to another.
As of this month, Avero has a public API — so those bridges can be actual bridges. Everything you see in Avero — deals, contacts, organizations, activities, notes — can now be read and written by the other systems you run, over a plain REST interface at /api/v1. The full reference lives at averocrm.com/developers, and it's written so the person who builds your website can use it in an afternoon.
Webhooks: your stack finds out first
The piece we're most excited about is webhooks. Instead of another system asking Avero “anything new?” every few minutes, Avero tells it — the moment something happens. Fifteen events cover every create, update and delete across your records, and each delivery is signed and retried, so nothing arrives forged and nothing gets lost to a flaky connection.
What that looks like in practice: a group deal moves to Won and a provisional block appears in your PMS before anyone switches tabs. A new inquiry lands and your team's Slack channel pings with the deal link. A proposal value changes and tomorrow's revenue forecast is already right. None of it depends on someone remembering to re-enter anything.
Sync only what changed
For the systems that would rather pull on their own schedule — a nightly report, a data warehouse, a booking-engine sync — every list endpoint now takes an updated_since timestamp. Ask for “everything that moved since last night” and that's exactly what you get.
It sounds like a small thing. It isn't: incremental sync is the difference between an integration that hammers full exports and one that runs quietly for years. It also keeps you comfortably inside your plan's daily API allowance, since you stop paying tokens to re-fetch records that haven't changed since March.
“The best integration is one your team never notices — the data is simply where they look, already correct.”
One search across everything
The third addition is a single /search endpoint that looks across deals, people, organizations, activities and notes at once, ranked by relevance. It exists for the moments other tools need to answer “who is this?” — a caller-ID lookup for your phone system, a guest panel inside your front-desk tool, a quick “do we know this company?” check on your website's inquiry form. One request, one ranked answer, instead of five queries stitched together.
Where to start
API access is included in every plan, metered by a daily token budget that scales with your tier — and if you run something hungry, top-ups are a click in billing. Keys are minted in Settings, webhooks are configured right next to them, and the developer docs cover every endpoint with copy-paste examples, including signature verification for webhooks.
If you're not sure what to connect first, start where the retyping hurts most. For most properties that's the won-deal handoff to the PMS — the five minutes of duplicate entry that occasionally becomes a double-booked suite. Wire that one webhook, and your CRM stops being an island the same day.
Connect Avero to the rest of your stack.
The full reference — endpoints, webhooks, search — lives at averocrm.com/developers. API access is included in every plan.
Book a demo