BILL Connect Events API
Browse all Bill APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey12 EndpointsREST
For Agents
Subscribe to BILL platform events, manage webhook subscriptions, rotate security keys, and trigger test-event delivery for verification.
Use for: I need to subscribe to bill-approved events from BILL, List the available event types in the BILL catalog, Create a webhook subscription for vendor change events, Rotate the security key on a BILL event subscription
Not supported: Does not handle bill creation, approvals, or AR customer management directly — use only for BILL event subscription, signing-key rotation, and test-event delivery.
Jentic publishes the only available OpenAPI specification for BILL Connect Events API, keeping it validated and agent-ready. Connect Events lets developers subscribe to push notifications about BILL platform activity — bill creation, approval state changes, vendor updates, and similar — through a dedicated v3 subscription model. The API exposes the event catalog, subscription lifecycle (create, read, list, update, patch, delete), security key rotation, a test-fire endpoint, and a per-subscription event delivery endpoint. It is the BILL equivalent of webhooks for downstream systems that need to react in near real time.
Install Jentic One Beta
Connect the BILL Connect Events API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BILL Connect Events API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with BILL Connect Events API.
List the event types available to subscribe to via /v3/events/catalog
Create a subscription for one or more event types with /v3/subscriptions
Read, update, patch, or delete an existing subscription
Rotate the subscription's security key via /v3/subscriptions/{subscriptionId}/security_key
Trigger a test-event delivery against a subscription endpoint with /v3/subscriptions/{subscriptionId}/test
Fetch a specific subscription detail through /v3/events/subscription/{subscriptionId}
Send an event to a subscription's endpoint via /v3/events/subscription/{subscriptionId}/event/{eventId}
Use Cases
Patterns agents use BILL Connect Events API for, with concrete tasks.
★ Real-Time Approval Notifications
Downstream systems — Slack alerters, ERP syncs, or finance dashboards — react when bills move through the BILL approval workflow. The integration creates a subscription via POST /v3/subscriptions on the relevant event types from /v3/events/catalog, then receives signed callbacks at its registered URL. /v3/subscriptions/{subscriptionId}/security_key rotates the signing key as part of routine credential hygiene.
Call POST /v3/subscriptions with the destination URL and the bill-approved eventType from /v3/events/catalog, then verify with /v3/subscriptions/{subscriptionId}/test
Subscription Lifecycle Management
Operations teams keep BILL event subscriptions in sync with downstream consumers — adding new ones, retiring old ones, and PATCHing URLs when an internal service moves. The full CRUD surface (POST, GET, PUT, PATCH, DELETE on /v3/subscriptions/{subscriptionId}) supports this without manual UI clicks. /v3/health confirms the Connect Events plane is reachable before bulk lifecycle changes.
Call /v3/health, then PATCH /v3/subscriptions/{subscriptionId} with the new destination URL when a downstream service moves
Endpoint Verification Before Go-Live
Before flipping a webhook subscription live, integrators verify the destination URL accepts BILL's payload signing and returns 2xx within the timeout. POST /v3/subscriptions/{subscriptionId}/test fires a synthetic event so engineers can inspect logs and confirm the endpoint is wired correctly. This catches bad URL config, missing TLS, and signature-verification mistakes before any real event traffic flows.
Call POST /v3/subscriptions/{subscriptionId}/test, then inspect destination logs to confirm the test event arrived signed and a 2xx was returned
Agent-Driven Webhook Setup via Jentic
An AI agent provisioning a new BILL integration searches Jentic for 'subscribe to BILL events', loads the subscription create operation, and executes it with a destination URL the user provides. The Connect Events credential sits in Jentic's vault, so the agent never sees the raw key, and the test endpoint is then loaded and executed automatically to verify the round-trip. End-to-end webhook setup becomes a single agent prompt.
Search Jentic for 'subscribe to BILL events', load POST /v3/subscriptions and execute, then load /v3/subscriptions/{subscriptionId}/test and execute to verify
Key Endpoints
12 endpoints — jentic publishes the only available openapi specification for bill connect events api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/v3/events/catalog
List available event types
POST
/v3/subscriptions
Create a new event subscription
GET
/v3/subscriptions
List all subscriptions
PATCH
/v3/subscriptions/{subscriptionId}
Patch fields on a subscription
DELETE
/v3/subscriptions/{subscriptionId}
Delete a subscription
POST
/v3/subscriptions/{subscriptionId}/security_key
Rotate the subscription security key
POST
/v3/subscriptions/{subscriptionId}/test
Trigger a test-event delivery
GET
/v3/health
Check Connect Events service health
GET
/v3/events/catalog
List available event types
POST
/v3/subscriptions
Create a new event subscription
GET
/v3/subscriptions
List all subscriptions
PATCH
/v3/subscriptions/{subscriptionId}
Patch fields on a subscription
DELETE
/v3/subscriptions/{subscriptionId}
Delete a subscription
POST
/v3/subscriptions/{subscriptionId}/security_key
Rotate the subscription security key
POST
/v3/subscriptions/{subscriptionId}/test
Trigger a test-event delivery
GET
/v3/health
Check Connect Events service health
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
BILL gateway credentials and per-subscription security keys are stored encrypted in the Jentic vault. Agents call subscription operations by name and Jentic attaches the credentials at execution time so the raw secrets never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'subscribe to BILL events', 'rotate webhook security key') and Jentic returns the matching Connect Events operation with body and path parameters typed so the agent fills only the destination URL or subscription ID.
Time to first call
Direct Connect Events integration: 1-2 days handling subscription CRUD, security-key rotation, and signature verification on the receiving side. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using BILL Connect Events API through Jentic.
Why is there no official OpenAPI spec for BILL Connect Events API?
BILL documents Connect Events in narrative form on developer.bill.com but does not publish the underlying OpenAPI document. Jentic generates and maintains a structured OpenAPI specification so AI agents and developers can call BILL Connect Events API via tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the BILL Connect Events API use?
Connect Events runs through BILL's gateway and is authenticated with a BILL developer key plus session credentials, matching the rest of the BILL platform. Inbound delivery to your webhook URL is signed with the per-subscription security key returned at create time. Through Jentic, both sides of the credential are held in the vault.
How do I subscribe to bill-approved events?
Call GET /v3/events/catalog to find the event-type identifier for bill-approved, then POST /v3/subscriptions with that event type and your destination URL. Verify with POST /v3/subscriptions/{subscriptionId}/test before going live.
What are the rate limits for the BILL Connect Events API?
Rate limits inherit from the BILL gateway and are not published per-endpoint. For high-cardinality fan-out, prefer fewer subscriptions with multiple event types over many narrowly scoped subscriptions, and consume the events asynchronously on the receiving side.
How do I rotate a subscription's security key?
POST /v3/subscriptions/{subscriptionId}/security_key returns a new signing key and immediately retires the previous one. Make sure your verification code accepts both keys for a brief overlap window if your delivery pipeline can have in-flight events when rotation runs.
How do I subscribe to BILL events through Jentic?
Run `pip install jentic`, then `await client.search('subscribe to BILL events')`, `await client.load(...)` for POST /v3/subscriptions, and `await client.execute(...)` with the event-type and destination URL. Chain into /v3/subscriptions/{subscriptionId}/test to fire a synthetic event for verification.
GET STARTED