MSP Billing
Retrieve usage data, billing information, and manage MSP tenant accounts via the Admin REST API.
Description
The MSP Billing endpoint provides programmatic access to billing data, usage metrics, and account management capabilities for Keeper Managed Service Providers (MSPs) and Distributors. This endpoint enables partners to retrieve current and historical usage data, manage trial and paid accounts, and integrate billing information with PSA (Professional Services Automation) and financial systems.
The MSP Billing API exposes billing and account lifecycle data through a RESTful interface, supporting consumption-based billing reconciliation, automated account provisioning, and financial reporting integration.
Overview
The Admin REST API MSP Billing endpoint delivers comprehensive billing and account management capabilities for the Keeper MSP ecosystem. This functionality supports critical partner operations:
Billing Reconciliation Retrieve current and monthly usage data for all Managed Companies. Integrate with PSA platforms like ConnectWise, Datto, or Gradient MSP for automated billing reconciliation and invoice generation.
Account Lifecycle Management Programmatically create trial accounts, convert trials to paid subscriptions, activate expired accounts, and cancel paid accounts. Automate the full customer lifecycle without manual intervention in the Admin Console.
Usage Analytics Track license consumption across all Managed Companies. Monitor product utilization, Secure Add-On adoption, and storage consumption for capacity planning and upsell identification.
Financial Reporting Export billing data for integration with accounting systems. Generate reports on revenue by customer, product mix analysis, and monthly recurring revenue (MRR) tracking.
Prerequisites
Active Keeper MSP or Distributor account
Advanced Reporting and Alerts Module (ARAM) add-on enabled
API key provided by Keeper (contact your support representative)
Pre-shared secret for JWT generation
Vendor name assigned by Keeper
Configuration
Generate an API token
For Billing APIs please use BILLING read role when generating an API token.
Example:
MSP Billing Usage API
Endpoint
Purpose Retrieve monthly billing usage details for the authenticated MSP and its linked Managed Companies (MCs), including unit pricing, base licenses and add-ons consumption, quantities, and associated costs for a specified month and year.
Authentication
Send your API token in the x-api-token header:
x-api-token: Bearer <API_TOKEN>
Query parameters
month
Integer
Yes
Single digit from 1 to 12, without a leading zero (e.g. 1 or 11).
year
Integer
Yes
Four-digit year (e.g. 2025 or 2023).
Headers
x-api-token
Bearer <API_TOKEN>
Example of requests
Request with no pagination
Example success response (200)
Error codes
400
Missing/Invalid month
Month is invalid.
400
Missing/Invalid year
Year is invalid.
403
Forbidden
MC trying to access api.
401
Unauthorized
Invalid or missing token.
500
Internal Server Error
Unexpected error occurred.
Security Notes
Treat API tokens like passwords; rotate them on a schedule.
Restrict permissions to the minimum required roles and actions.
Prefer short expirations; use
neveronly for special automation cases.Store tokens in a secure location (e.g., Keeper Vault).
MSP Current Usage API
Endpoint
Purpose Retrieve snapshot of current usage (base licenses and add-ons) for the authenticated MSP and linked Managed Companies (MCs).
Authentication
Send your API token in the x-api-token header:
x-api-token: Bearer <API_TOKEN>
Headers
x-api-token
Bearer <API_TOKEN>
Example of requests
Request with no pagination
Example success response (200)
Error codes
403
Forbidden
MC trying to access api.
401
Unauthorized
Invalid or missing token.
500
Internal Server Error
Unexpected error occurred.
Last updated
Was this helpful?

