Skip to main content

Use Custom API and event webhooks

Create dedicated API credentials and deliver selected Moxie events to secure HTTPS endpoints.

Written by Geoff Mina

Custom API provides credentials for a purpose-built integration and outbound webhooks that notify your HTTPS endpoints when selected business events occur.

Create a dedicated API key

Choose Enable to generate an API key and the workspace-specific API base URL. Use separate keys for separate apps or environments. This limits the impact of rotation or deletion and makes ownership easier to understand.

Moxie Custom API panel ready to generate credentials without exposing a secret key

The key is not created or exposed until you deliberately enable the integration.

Handle credentials safely

  • Send API requests from a trusted server, not public browser code.

  • Keep the key in a secret manager or protected environment variable.

  • Do not include keys in screenshots, tickets, chat messages, or source control.

  • Delete a key if it may have been exposed; apps using it lose access immediately.

Add an event webhook

Expand the API-key connection, then choose Add webhook. Select the Moxie event and enter an HTTPS endpoint. Available events cover important changes across clients, invoices, payments, agreements, projects, tickets, time entries, forms, meetings, tasks, and opportunities.

Authenticate webhook deliveries

Choose the authentication method your receiver expects: none, Basic, Bearer, or a custom header. Save the authentication settings, then enable the webhook. Use a secret dedicated to webhook delivery rather than reusing a user password or the Moxie API key.

Operate webhooks safely

Build the receiver to tolerate duplicate delivery, validate authentication, return a successful response quickly, and process longer work asynchronously. Disable a webhook while troubleshooting; delete it only when the endpoint is permanently retired.

Plan availability

Custom API and automation connections are available on Pro and Teams plans.

Choose the native workflow builder when it fits

If the automation can be expressed with Moxie's pipeline triggers, decisions, messages, documents, projects, forms, and invoices, start with Build and test workflow automations. Use Custom API and webhooks when the process must cross into another application.


Continue exploring Integrations & developer tools

Did this answer your question?