Billie Connect Converse API Prerequisites
Technical Requirements
- OAuth 2.0 Implementation
- Client must implement OAuth 2.0 client credential flow
- Support for JWT token handling
- Token caching mechanisms
- API Client Configuration
- HTTPS support for secure communication
- JSON request/response handling
- Bearer token authentication headers
- Webhook Support (v3 only)
- Public HTTPS endpoint for receiving webhook callbacks
- SSL/TLS certificate validation
- Request signature verification (recommended)
- Client Registration
- Valid client number (clientNo) assigned by Aria
- OAuth 2.0 credentials (client_id, client_secret) configured through a service account
1. Configure Client Parameters
You must set the following client parameters in your Aria instance:
| Parameter ID | Description |
|---|---|
| ENABLE_BILL_SHOCK_ANALYZER_PENDING_INVOICE | Enable/disable pending invoice analysis |
| BILL_SHOCK_ANALYZE_PENDING_INVOICE_PERCENTAGE_THRESHOLD | Bill shock detection threshold (%) |
| BILL_SHOCK_ANALYZE_PENDING_INVOICE_NOTIFICATION_URL | Webhook callback URL for analysis result |
| PLAN_RECOMMENDER_PLAN_EXCLUSION_PERCENTAGE_THRESHOLD | Plan exclusion threshold for recommendations (%) |
2. Create a Billie Service Account
- Create a service account with a unique name.
- Once the Service account is saved, access that, return to the update screen, and generate a key.
3. Subscribe to Pending Invoice Event in Aria
Getting here: Configuration > Notifications > Events > Financial Transactions
Subscribe to the Pending Invoice Created event. Learn more about Financial Transactions events, or how to enable and subscribe to events.
- On the Financial Transactions events page, on the Events Fired tab, check the Pending Invoice Created event.

- Click the Add another step button.

- Choose "Transaction Data via Secure HTTP (XML Document)" from the Method dropdown.

- Type the Billie Connect URL in the Destination text box. This may vary, depending on where you plan to deploy Billie.
- In the Server Response text box, type {"message": "Event processed successfully"}.
- Click the Add header button and, in the Name text box, type x-api-key.
- In the Value text box, type your API key.
Note: You can obtain the API key from Aria DevOps.
- Click the Save button.
4. Validation & Testing
- Trigger Test Event: Generate a test pending invoice in Aria for the client instance.
- Monitor CloudWatch Logs:
- Pre-filter function: aria-billie-{stage}-aria-events-bill-shock-pre-filter
- Agent invocation logs: aria-billie-{stage}-bill-shock-*
- Verify Webhook Delivery: Check the client's notification URL receives the analysis result.
Troubleshooting
| Issue | Check |
|---|---|
| No event receive | Verify Aria event subscription is active and API key is correct |
| Pre-filter skipping event | Check ENABLE_BILL_SHOCK_ANALYZER_PENDING_INVOICE = "true" |
| Agent not triggering | Verify the bill shock threshold is exceeded, and the previous invoice exists |
| Webhook not delivered | Validate BILL_SHOCK_ANALYZE_PENDING_INVOICE_NOTIFICATION_URL is accessible |
| Authentication error | Confirm OAuth2 service account credentials in Parameter Store |
| <TBA> |