Public API, Webhooks, and Zapier — What We Support Today

Honest answer on Biller Genie's integration surface: Connect REST API endpoints (customers, sales-receipts, tax-rates), how to request an API key, why webhooks and Zapier aren't supported today, and practical workarounds.

Written by Thomas Aronica (Super Administrator)

Updated

A common question, especially from larger merchants and partners evaluating Biller Genie: can I integrate Biller Genie with my own systems using an API, webhooks, or Zapier? Here's the honest current state.

Capability Status
Public REST API (Connect API) Yes, with limited scope. Keys are issued by Biller Genie, not self-serve.
Outbound webhooks No — not supported today.
Zapier integration No — not supported today.

Connect API — public REST endpoints

Biller Genie has a versioned public REST API called the Connect API. It's intended for purpose-built integrations where another product needs to push data into Biller Genie — for example, a vertical CRM that creates customers and invoices in Biller Genie as part of its own workflow.

What endpoints exist today

Endpoint Purpose
POST v1/customers Create a customer in your Biller Genie account.
GET v1/customers/{id} Look up a customer by ID.
POST v1/sales-receipts Record a sales receipt (paid transaction not tied to an invoice).
GET v1/sales-receipts/{id} Retrieve a sales receipt by ID.
GET v1/tax-rates List the tax rates configured on your account, so your integration can apply the right rate when creating customers or receipts.
POST v1/auth/validate Validate that a Connect API key is still active. Used by the API gateway, not by integration code directly.

What's NOT in the Connect API today: invoices, payments against existing invoices, refunds, voids, customer balances/A-R reports, autopay enrollment, payment-method storage, sync controls. If your integration needs any of those, contact support@billergenie.com and describe your use case — we prioritize Connect API expansion based on customer demand.

Authentication

The Connect API uses API key authentication. Each call passes the key as a header. Keys are tied to your Biller Genie merchant account and identify your account when calls land. There is no OAuth or per-user authorization — every call acts as the merchant account, not as an individual user, which is the right model for system-to-system integrations.

Getting an API key

Connect API keys are issued by Biller Genie support on request. They are not self-serve from the merchant portal today. To request a key:

  1. Email support@billergenie.com.
  2. Tell us your Biller Genie ID, the name of the integration you're building or buying, and the use case (e.g. "creating customers and sales receipts from our practice management system").
  3. Our team will issue a key, share it with you via a secure channel, and provide the current Connect API base URL and endpoint specs.

Key rotation, revocation, and audit are also handled by support. If a key is compromised, tell us immediately and we'll rotate it.

Outbound webhooks — not supported today

Biller Genie does not currently send outbound webhooks for events that happen in your account (a payment is processed, an invoice is paid, a sync fails, etc.). If your integration needs to know when something happens in Biller Genie, the current options are:

  • Pull instead of push. Have your integration call the relevant Connect API endpoint on a schedule. Not as efficient as webhooks but works for most low-frequency uses (a few times an hour).
  • Use your accounting software's webhooks. If you primarily want to know "did this invoice get paid?", QuickBooks Online has Payment webhooks that fire after Biller Genie syncs the payment back to QuickBooks. This works well for integrations whose data of record is the accounting software, not Biller Genie.
  • Email parsing as a last resort. Merchant receipts are sent in real-time when a payment is processed — some integrations parse those receipt emails. Not recommended long-term but works in a pinch.

Outbound webhooks are tracked as a customer-requested feature. If your integration design depends on them, tell us — every request is logged and shapes our roadmap.

Zapier — not supported today

Biller Genie does not have a Zapier app today. You can't directly trigger Zaps from Biller Genie events or use Biller Genie as a Zap action.

Practical workarounds:

  • Trigger from QuickBooks Online or Xero — both have first-class Zapier apps. Because Biller Genie syncs invoices and payments to and from your accounting software, you can build Zaps that react to QuickBooks/Xero events that originated in Biller Genie.
  • Connect API + Zapier "Webhooks by Zapier" — a custom Zap can call the Biller Genie Connect API directly using the Webhooks by Zapier action. This requires having a Connect API key from support.