Usage Based Pricing on App Markeptlace

Modified on: Fri, 14 Nov, 2025 at 9:17 AM

HighLevel’s App Marketplace supports usage‑based pricing so developers can charge per execution, per message, or per custom event—and agencies can add markups and set daily limits. This article explains what the model is, how pricing modules work, and how to configure markup, limits, and charge flow. Follow the concise, role‑based steps to launch confidently and keep client billing transparent.

TABLE OF CONTENTS

What is Marketplace Usage‑Based Pricing and Agency Rebilling?
Key Benefits of Marketplace Usage‑Based Pricing and Agency Rebilling
Usage-Based Pricing Modules
Billing Controls & Protections
How To Set Up Marketplace Usage‑Based Pricing and Agency Rebilling
Frequently Asked Questions
Related Articles

What is Marketplace Usage‑Based Pricing and Agency Rebilling?

Usage‑based pricing ties charges directly to app activity so costs scale with actual usage rather than flat subscriptions. Agency rebilling lets agencies resell those per‑use charges with their own markup so they can maintain margin while centralizing client billing.

Usage‑based pricing covers three modules: per‑execution fees for Actions/Triggers, per‑message fees for Conversation Providers (with separate inbound and outbound rates), and custom per‑usage fees for app‑defined events posted through the Marketplace billing APIs. Agency rebilling applies an agency‑set markup to these per‑use charges and bills the appropriate wallet based on your rebilling setup.

Key Benefits of Marketplace Usage‑Based Pricing and Agency Rebilling

Educational description: Knowing the advantages helps teams decide when consumption‑based billing makes sense and how to protect budgets and margins.

Aligned costs: charges track real activity instead of flat, fixed plans
Granular control: choose per‑execution, per‑message (inbound/outbound), or custom events
Agency margin: markup controls let agencies add profit on top of developer pricing
Spend protection: daily usage limits cap consumption to avoid bill shock
Clarity on billing: wallet charge flow clarifies who is billed with/without rebilling

Usage-Based Pricing Modules

App developers can now set a per-usage price on their Marketplace apps. An app can have a usage-based price for three modules:

Per‑Execution Pricing for Marketplace Actions and Triggers

Charge each time an action or trigger runs, which works well for workflow‑heavy or automation‑driven apps.

Unit: each execution of a supported action or trigger.
Typical uses: premium actions, data enrichment, sync steps.
Where to configure: App → Pricing → enable Actions & Triggers and set the per‑execution price.

Per‑Message Pricing for Conversation Providers

Messaging costs can vary by direction and channel. Separate inbound and outbound rates keep pricing aligned to the real cost of delivery and handling.

Unit: each message handled by the Conversation Provider.
Directional pricing: set distinct Inbound and Outbound prices.
Where to configure: App → Pricing → Conversation Provider pricing fields.

Custom Per‑Usage Pricing for App‑Specific Events

Bill for unique events—like minutes, tokens, or other units—by defining your own event and posting usage with the billing APIs.

Unit examples: per minute (e.g., AI voice), per token, per scanned item.
Where to configure: App → Pricing → Custom Event (API‑billed) and define price/unit; post usage via billing APIs.
Validation: post test usage and confirm charges appear before go‑live.

Billing Controls & Protections

One compact table summarizing markup, charge flow, and usage limits to speed configuration and reconciliation.

Item	What it does	Where to configure	Impact on billing	Key notes
Agency Markup	Adds margin to developer per‑use pricing	App Marketplace → App Reselling (Usage‑Based)	Increases per‑unit price billed to client (when rebilling ON)	App‑level; not client‑specific
Rebilling ON	Bills the client's sub‑account wallet	Agency billing settings (Rebilling)	Usage charges debit sub‑account wallet	Verify wallets are funded
Rebilling OFF	Bills the agency wallet	Agency billing settings (Rebilling)	Usage charges debit agency wallet	Monitor agency wallet balance
Daily Usage Limits	Caps daily billable units per app	App Marketplace → Usage Limits	Usage pauses at cap; resumes next day	Set caps to match budget/volume

How To Set Up Marketplace Usage‑Based Pricing and Agency Rebilling

Proper configuration ensures correct pricing, accurate posting of usage events, and predictable client billing.

Go to App Marketplace → open the app → App Reselling (Usage‑Based).
Select Set Usage‑Based Pricing (or equivalent) and enter your markup; Save.
Go to App Marketplace → Usage Limits and set daily caps per client/sub‑account; Save.
Ensure Rebilling is enabled so eligible charges debit the sub‑account wallet.
Where can I see the app's usage-based charges?

If an app has usage-based pricing, the pricing details are listed in the Pricing section of the app's Details page.

For Workflow Actions and Triggers, the usage pricing is also listed in the Discover tab in the Workflow builder.

Frequently Asked Questions

Q: Who is billed when rebilling is on vs. off?
With rebilling on, the sub‑account wallet is charged. With rebilling off, the agency wallet is charged.

Q: Can I set different inbound and outbound message prices?
Yes. Conversation Providers support separate inbound and outbound per‑message rates.

Q: Are markups per app or per client?
Markups are configured at the app level for usage‑based apps. Clients see only the agency price.

Q: What happens when a daily limit is reached?
Billable usage for that app pauses for the rest of the day and resumes after the daily reset.

Q: Can subscription and usage pricing be used together?
Yes. Use subscriptions for access and usage‑based pricing for consumption when supported by the app.

Q: How do I test before rolling out to clients?
Developers can post test usage via the billing APIs; agencies can verify charges and limit behavior on their markup and limits screens.

Q: Where do I view usage‑based charges?
Review charges in relevant App Marketplace views and wallets; some usage may also be visible where the app is discovered (e.g., Workflows Discover) depending on the module.