> ## Documentation Index > Fetch the complete documentation index at: https://docs.hyperprop.com/llms.txt > Use this file to discover all available pages before exploring further. # Get daily billing activity > Returns billing cycle charges grouped by UTC day for a compact activity chart. Each point includes the total amount, its split into `platformAmount` (the Hyperprop platform fee) and `marketDataAmount` (the CME Group market data bundle), and the number of cycle line items started on that day — so `platformAmount + marketDataAmount = amount` always holds. Aggregation runs server-side and returns one row per active day, so response size stays bounded even for organizations with 100K+ users. **Example:** ```http GET /platform/v1/organization/billing/activity?startDate=2026-07-01&endDate=2026-07-31 X-API-Key: hp_live_... ``` **Permissions:** requires view access to Billing. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/organization/billing/activity openapi: 3.0.0 info: title: Hyperprop Platform API version: 1.0.0 description: >- REST API for the Hyperprop Trading Platform — provision evaluation and funded trading accounts, manage traders and plans, react to account lifecycle events via signed webhooks, and reconcile billing. Built for prop firms integrating from their own backend. Authentication, quick start, error handling, idempotency, pagination, custom metadata, webhooks, and the MCP connector are documented at https://docs.hyperprop.com. x-logo: url: https://app.hyperprop.com/logo-icon.svg altText: Hyperprop href: https://hyperprop.com servers: - url: https://api.hyperprop.com/platform description: Production security: [] tags: - name: Trading accounts description: Create, update, and inspect trading accounts. - name: Traders description: Look up and update the traders in your organization. - name: Trading plans description: Define the plans you sell. - name: Trading rules description: Define how accounts are evaluated. - name: Lockouts description: Pause and resume trading on an account. - name: Payouts description: Check payout eligibility and record payouts. - name: Purchases description: Purchases recorded for your organization. - name: Time Machine description: Restore accounts to an earlier trading day or instant. - name: Webhooks description: Register webhook endpoints and inspect deliveries. - name: Events description: Your organization's event history and real-time event stream. - name: Reconciliation description: Balances, end-of-day snapshots, and fills for reconciliation. - name: Analytics description: Organization performance and plan economics. - name: Billing description: 'Your Hyperprop bill: activity, billing cycles, and forecasts.' - name: Team and roles description: Manage dashboard access for your staff. - name: API keys description: Manage your organization's API key. - name: Logs and health description: API request logs, the audit log, and integration health. - name: Organization profile description: Your organization's profile and logo. - name: Support description: Open and follow up on support tickets. - name: Partner access description: >- Read a trader's journal as an approved partner app, with the trader's own key. paths: /v1/organization/billing/activity: get: tags: - Billing summary: Get daily billing activity description: >- Returns billing cycle charges grouped by UTC day for a compact activity chart. Each point includes the total amount, its split into `platformAmount` (the Hyperprop platform fee) and `marketDataAmount` (the CME Group market data bundle), and the number of cycle line items started on that day — so `platformAmount + marketDataAmount = amount` always holds. Aggregation runs server-side and returns one row per active day, so response size stays bounded even for organizations with 100K+ users. **Example:** ```http GET /platform/v1/organization/billing/activity?startDate=2026-07-01&endDate=2026-07-31 X-API-Key: hp_live_... ``` **Permissions:** requires view access to Billing. operationId: getV1OrganizationBillingActivity parameters: - description: First UTC day (defaults to 29 days ago) x-format: isoDate: true name: startDate in: query required: false schema: type: string - description: Last UTC day, inclusive (defaults to today) x-format: isoDate: true name: endDate in: query required: false schema: type: string responses: '200': description: Daily billing amount and cycle counts content: '*/*': schema: $ref: '#/components/schemas/Model225' '401': description: Authentication required content: '*/*': schema: $ref: '#/components/schemas/Model9' '403': description: Access denied content: '*/*': schema: $ref: '#/components/schemas/Model47' '500': description: An unexpected error occurred content: '*/*': schema: $ref: '#/components/schemas/Model5' security: - X-API-Key: [] components: schemas: Model225: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model224' Model9: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 401 error: type: string example: Unauthorized message: type: string example: Authentication required code: type: string description: Machine-readable error code — switch on this, not on message text example: UNAUTHORIZED Model47: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 403 error: type: string example: Forbidden message: type: string example: Access denied code: type: string description: Machine-readable error code — switch on this, not on message text example: FORBIDDEN Model5: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 500 error: type: string example: Internal Server Error message: type: string example: An unexpected error occurred code: type: string description: Machine-readable error code — switch on this, not on message text example: INTERNAL_ERROR Model224: type: object properties: generatedAt: type: string x-format: isoDate: true filters: $ref: '#/components/schemas/Model222' activity: $ref: '#/components/schemas/activity' Model222: type: object properties: startDate: type: string endDate: type: string activity: type: array items: $ref: '#/components/schemas/Model223' Model223: type: object properties: date: type: string example: '2026-07-21' amount: type: number example: 850 platformAmount: type: number description: Hyperprop platform fee portion example: 700 marketDataAmount: type: number description: CME Group market data bundle portion example: 150 cycleCount: type: integer example: 50 securitySchemes: X-API-Key: type: apiKey name: X-API-Key in: header description: >- Organization API key. Format: "hp_live_{key}". Organization admins manage the key in the dashboard. ```` ## Related topics - [Get daily payout activity](/platform-api/payouts/get-daily-payout-activity.md) - [Get daily lockout activity](/platform-api/lockouts/get-daily-lockout-activity.md) - [Get daily webhook delivery activity](/platform-api/webhooks/get-daily-webhook-delivery-activity.md) - [Get daily account creation activity](/platform-api/trading-accounts/get-daily-account-creation-activity.md) - [Get webhook endpoint delivery and latency metrics](/platform-api/webhooks/get-webhook-endpoint-delivery-and-latency-metrics.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.