Open API and webhooks

Provides API access and outbound webhooks for connecting AllQuote to external tools and automations.

Use documented API endpoints and outbound webhooks to connect supported AllQuote records with another system.

Before you start

Availability: Team plan and above. Enabled business features, role permissions, connected providers and supported devices may add requirements.

Documented roles: Owner, Office. A role name alone does not override the permissions set by your business.

Where to find it: Developers > API and webhooks.

Review the current Developers documentation, credential requirements and exact endpoint or event needed. Keep integration credentials out of customer documents and shared screenshots.

Using this guide in New Zealand

  • Set your business country in Business settings before entering customer addresses or preparing documents. The country selected on the public website does not change an existing business.
  • Check the business currency (NZD), time zone and document tax settings. Only enable tax collection if your business is registered and the settings match your requirements. Your customer invoice tax settings are separate from tax on your AllQuote subscription.
  • Screenshots use demonstration records. Their sample currency, addresses and tax amounts do not override your business settings.
The API documentation describes authentication and integration entry points. Create scoped credentials only for the intended integration; this screenshot contains no live API key.
Demo screenshot. The API documentation describes authentication and integration entry points. Create scoped credentials only for the intended integration; this screenshot contains no live API key. Select the image to view it at full size.

Step by step

  1. Open Developers at /developers to review available API endpoints and webhook behaviour.
  2. Create or use the integration credentials for the external system.
  3. Connect the API client or webhook receiver to the AllQuote records it needs.
  4. Test against a small workflow before depending on the integration in production.

Worked example

For a small approved integration, test one supported read or event with a controlled record, inspect the payload and build explicit handling for errors before expanding the workflow.

This is an illustrative scenario. Use your own approved scope, quantities, rates and business rules.

Check the result

Confirm authentication, record scope, event handling and failure behavior against the published API contract. Keep a traceable record of external processing.

Limits and troubleshooting

API access does not mean every screen action has an endpoint or that every business process can run unattended. Do not infer unsupported events, payroll providers or financial write behavior.

Check current plans and feature availability · Browse every guide