Changelog: Public API

Added support for POST /conversation/{id}/message via the API. This endpoint allows users to send an internal note to an existing conversation. Support for public replies is not available at this time.

Public API clients can now update existing client records with PATCH /v1/client/{id}.

New list endpoints are now available in the Public API, which expands the practical read surface for partners and integrators. These endpoints support pagination, sorting, search, and allowlisted filters, and the docs have been updated to reflect the new surface area.

• New list endpoints now available:
  • conversation/list
  • conversation/{id}/message/list
  • site/list
  • user/list
  • client/list
• This makes it possible to browse core records through the API instead of relying on one-by-one fetch patterns.
• The list behavior is standardized across these endpoints, with shared support for pagination, sorting, search, and filtering.
• conversation/{id}/message/list also extends the API deeper into conversation history, not just top-level records.
• The developer docs have been updated alongside the release.

The public API now supports POST conversation/submit

Added POST /v1/site so integrators can create sites with core details like address, monitoring, notes, client links, terms acceptance, SLA, and owner assignments.

Added PATCH /v1/site/{id} so integrators can update those same core site details on existing sites.

ProVision Public API

The new ProVision Public API gives partners a faster way to connect ProVision data to their own tools and workflows.

Partners can now generate API keys in Settings → Integrations → Developer and get started with the API docs.

The first release includes endpoints for reading conversation details and context, updating conversation fields, looking up clients, sites, and users, creating clients, and linking clients to sites.

Available endpoints at launch:

• GET /v1/conversation/{id}
• GET /v1/conversation/{id}/context
• PATCH /v1/conversation/{id}
• GET /v1/client/{id}
• POST /v1/client
• GET /v1/site/{id}
• PUT /v1/client/{clientId}/site/{siteId}
• GET /v1/user/{id}

Partners can now link an existing client to an existing site through the Public API.

Partners can now create clients through the public API, including email addresses and phone numbers.