> ## 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. # Export a month's line items as CSV > Every charge of the month as a CSV download: one row per trader-month, the same rows as `GET /billing/summary?month=` without paging. Months follow America/Chicago. **Format:** UTF-8 with a byte order mark, comma-separated, `\n` line endings, a header row, then one row per charge in the order it started. Columns: | Column | Content | |---|---| | `Trader` | The trader's email (their trader ID if no email is on file) | | `Started` | Date the charge started, `YYYY-MM-DD` | | `Trigger` | `market data activated` (the trader's first billing cycle) or `monthly charge` (a renewal) | | `Platform (USD)` | Platform fee, 2 decimals | | `Market data (USD)` | Market data fee, 2 decimals | | `Total (USD)` | Platform + market data | The currency in the headers is the month's billing currency. Cells that a spreadsheet would run as a formula are prefixed with `'`. The response has `Content-Disposition: attachment; filename="billing-line-items-YYYY-MM.csv"`. At most 10 exports a minute per organization. **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/line-items/export 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/line-items/export: get: tags: - Billing and invoices summary: Export a month's line items as CSV description: >- Every charge of the month as a CSV download: one row per trader-month, the same rows as `GET /billing/summary?month=` without paging. Months follow America/Chicago. **Format:** UTF-8 with a byte order mark, comma-separated, `\n` line endings, a header row, then one row per charge in the order it started. Columns: | Column | Content | |---|---| | `Trader` | The trader's email (their trader ID if no email is on file) | | `Started` | Date the charge started, `YYYY-MM-DD` | | `Trigger` | `market data activated` (the trader's first billing cycle) or `monthly charge` (a renewal) | | `Platform (USD)` | Platform fee, 2 decimals | | `Market data (USD)` | Market data fee, 2 decimals | | `Total (USD)` | Platform + market data | The currency in the headers is the month's billing currency. Cells that a spreadsheet would run as a formula are prefixed with `'`. The response has `Content-Disposition: attachment; filename="billing-line-items-YYYY-MM.csv"`. At most 10 exports a minute per organization. **Access:** read-only and full-access API keys. Dashboard members need view access to Billing & purchases revenue. operationId: getV1OrganizationBillingLineitemsExport parameters: - description: YYYY-MM; defaults to this month name: month in: query required: false example: 2026-10 schema: type: string pattern: ^\d{4}-(0[1-9]|1[0-2])$ responses: '200': description: |- CSV file. Example: ```csv Trader,Started,Trigger,Platform (USD),Market data (USD),Total (USD) trader@example.com,2026-10-03,market data activated,22.00,0.00,22.00 ``` content: text/csv: schema: type: string '400': description: Validation failed content: text/csv: schema: $ref: '#/components/schemas/Model25' '401': description: Authentication required content: text/csv: schema: $ref: '#/components/schemas/Model11' '403': description: The credentials may not make this request content: text/csv: schema: $ref: '#/components/schemas/OrganizationAccessError' '429': description: >- Too many requests (limit: 10 a minute per organization). Retry after `Retry-After` seconds headers: Retry-After: description: Seconds to wait before retrying schema: type: integer content: text/csv: schema: $ref: '#/components/schemas/Model726' '500': description: An unexpected error occurred content: text/csv: 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: text/csv: schema: $ref: '#/components/schemas/Model727' security: - X-API-Key: [] components: schemas: Model25: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 400 error: type: string example: Bad Request message: type: string example: Validation failed code: type: string description: Machine-readable error code — switch on this, not on message text example: VALIDATION_ERROR 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 OrganizationAccessError: 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: Your role does not have view access to "Billing & purchases revenue" code: $ref: '#/components/schemas/Model409' Model726: type: object properties: success: type: boolean description: Always false on errors example: false statusCode: type: number example: 429 error: type: string example: Too Many Requests message: type: string example: >- Too many requests (limit: 10 a minute per organization). Retry after `Retry-After` seconds code: type: string description: Machine-readable error code — switch on this, not on message text example: RATE_LIMITED 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 Model727: 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 Model409: type: string description: >- `INSUFFICIENT_PERMISSIONS` = the role or key lacks the permission this endpoint needs; `READ_ONLY_KEY` = a read-only API key sent a request that changes data; `IP_NOT_ALLOWED` = the request came from an address outside the key's IP allowlist; `ORG_INACTIVE` = the organization is not active example: INSUFFICIENT_PERMISSIONS enum: - INSUFFICIENT_PERMISSIONS - READ_ONLY_KEY - IP_NOT_ALLOWED - ORG_INACTIVE 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 - [Export a bulk job's items as CSV](https://docs.hyperprop.com/platform-api/mass-credit/export-a-bulk-jobs-items-as-csv.md) - [Billing and invoices](https://docs.hyperprop.com/guides/billing-and-invoices.md) - [Get all-months billing aggregates](https://docs.hyperprop.com/platform-api/billing-and-invoices/get-all-months-billing-aggregates.md) - [Build your own CRM on Hyperprop](https://docs.hyperprop.com/guides/build-a-crm.md) - [Get monthly billing summary](https://docs.hyperprop.com/platform-api/billing-and-invoices/get-monthly-billing-summary.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.