Changelog
Platform behaviour and documentation on this domain, dated, with what each entry means for an integration you have already built.
This changelog covers the developer surface: endpoints, payloads, the widget, integrations and the pages documenting them. Product releases - new voices, dashboard features, pricing - are announced inside the bitpull.ai dashboard, and this page does not duplicate them. An entry appears here when it changes something a developer has already integrated against.
First release of this domain: API reference, webhook documentation, embedding, telephony, agent tools, knowledge, omnichannel architecture, an integration directory with ten in-depth guides, and four free developer tools.
What to do: Nothing. If you were relying on bitpull.ai/docs alone, the API reference here adds rate limiting, the account-API boundary and the LiveKit handover in more detail.
The product documentation lists chat as a value for data-modes. The widget runtime checks for voice and text, and treats every other value - including chat - as both. Anyone who wrote data-modes="chat" expecting text-only has been shipping the voice launcher as well.
What to do: Check your embed snippet. If you want text only, the value is text.
The outbound webhook envelope is not part of any published contract. Rather than printing a field list that would silently rot, every page here sends you to capture a real delivery first, and the webhook tester exists for exactly that.
What to do: If you wrote a consumer against field names you assumed, read a real delivery and make the mapping tolerant of both shapes.
An agent tool is a name, a description, a JSON Schema, a timeout and an enabled flag. There is no URL or method in it. Connecting a declaration to your endpoint is set up with the bitpull team, which is why live-lookup integrations on this site are marked Assisted setup rather than Available.
What to do: If you planned a self-serve rollout around custom tools, budget for that conversation.
There is no feed on this page yet, and adding one that nobody reads would be worse than not having it. If you depend on this surface, the two things worth watching are your own webhook consumer's error rate and the status page. Both tell you about a change faster than a changelog entry can.
