> ## 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. **Access:** read-only and full-access API keys. Dashboard members need view access to Billing & purchases revenue. ## OpenAPI ````yaml https://api.hyperprop.com/platform/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: Instruments description: >- The contracts your organization's accounts can trade, with their specifications. - 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: Mass credit description: >- Credit back losses across many accounts after an incident, as background jobs you can follow, pause, export and reverse. - name: Webhooks description: Register webhook endpoints and inspect deliveries. - name: Events description: Your organization's event history, to replay or audit what happened. - name: Real-time streams description: >- Live events and trading data over a WebSocket, for dashboards and CRMs that update as things happen. - name: Reconciliation description: Balances, end-of-day snapshots, and fills for reconciliation. - name: Analytics description: Organization performance, revenue and top traders. - name: Risk description: Firm profit and loss and plan economics. - name: Billing and invoices description: >- Your Hyperprop invoices, credits and billing details, with usage so far this month, billing cycles, forecasts and CSV exports. - name: Team and roles description: Manage dashboard access for your staff. - name: API keys description: >- Manage your organization's API keys: rotation, read-only keys and IP allowlists. - name: Logs and health description: >- API request logs, the audit log, integration health, and idempotency key recovery. - 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 and invoices 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. **Access:** read-only and full-access API keys. Dashboard members need view access to Billing & purchases revenue. operationId: getV1OrganizationBillingActivity parameters: - description: First UTC day (defaults to 29 days ago) x-format: isoDate: true name: startDate in: query required: false example: '2026-10-01' schema: type: string - description: Last UTC day, inclusive (defaults to today) x-format: isoDate: true name: endDate in: query required: false example: '2026-10-31' schema: type: string responses: '200': description: Daily billing amount and cycle counts content: application/json: schema: $ref: '#/components/schemas/Model405' '400': description: >- The request does not match the documented parameters or body; `message` names the field content: application/json: schema: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: integer example: 400 error: type: string example: Bad Request message: type: string example: '"limit" must be less than or equal to 100' code: type: string enum: - VALIDATION_ERROR example: VALIDATION_ERROR description: >- Machine-readable error code — switch on this, not on message text '401': description: Authentication required content: application/json: schema: $ref: '#/components/schemas/Model11' '403': description: Access denied content: application/json: schema: $ref: '#/components/schemas/Model74' '500': description: An unexpected error occurred content: application/json: schema: $ref: '#/components/schemas/Model6' '504': description: >- Gateway Timeout - The request did not complete within 25 seconds (`REQUEST_TIMEOUT`). Nothing was changed; retry, or narrow the request (for example a shorter date range). content: application/json: schema: $ref: '#/components/schemas/Model406' security: - X-API-Key: [] components: schemas: Model405: type: object properties: success: type: boolean example: true data: $ref: '#/components/schemas/Model404' Model11: 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 Model74: 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 Model6: 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 Model406: type: object properties: statusCode: type: number example: 504 error: type: string example: Gateway Timeout message: type: string example: >- The request did not complete within 25 seconds. Try again, or narrow it (for example a shorter date range). code: type: string description: Machine-readable error code — switch on this, not on message text example: REQUEST_TIMEOUT Model404: type: object properties: generatedAt: type: string x-format: isoDate: true filters: $ref: '#/components/schemas/Model402' activity: $ref: '#/components/schemas/activity' Model402: type: object properties: startDate: type: string endDate: type: string activity: type: array items: $ref: '#/components/schemas/Model403' Model403: 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 (`hp_live_...`), sent in the `X-API-Key` header. Create, rotate and restrict keys in the dashboard or with the API keys endpoints; an organization can have two active keys, so you can rotate without downtime. A **full-access** key can call every endpoint in this reference. A **read-only** key can call `GET` endpoints (and create a trading stream token); any other request returns `403 READ_ONLY_KEY`. A key with an IP allowlist returns `403 IP_NOT_ALLOWED` from any other address. Each endpoint lists which keys can call it under **Access**. ```` ## Related topics - [Get daily lockout activity](https://docs.hyperprop.com/platform-api/lockouts/get-daily-lockout-activity.md) - [Get daily payout activity](https://docs.hyperprop.com/platform-api/payouts/get-daily-payout-activity.md) - [Get daily webhook delivery activity](https://docs.hyperprop.com/platform-api/webhooks/get-daily-webhook-delivery-activity.md) - [Get daily account and trader activity](https://docs.hyperprop.com/platform-api/trading-accounts/get-daily-account-and-trader-activity.md) - [Get hourly activity by weekday](https://docs.hyperprop.com/platform-api/analytics/get-hourly-activity-by-weekday.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.