> ## Documentation Index > Fetch the complete documentation index at: https://docs.paygentic.io/llms.txt > Use this file to discover all available pages before exploring further. # Get Line Items > Get paginated line items for an invoice from the analytics service ## OpenAPI ````yaml /openapi.json get /v2/invoices/{id}/lineItems openapi: 3.1.0 info: title: Paygentic API version: 0.1.0 description: > The Paygentic API provides a comprehensive platform for building and scaling monetization infrastructure. ## Authentication All API requests require authentication using an API key passed in the `Authorization` header: ``` Authorization: Bearer YOUR_API_KEY ``` ## Base URL All API requests should be made to: ``` https://api.paygentic.io/v0 ``` contact: name: Paygentic Support email: support@paygentic.io license: name: Proprietary servers: - url: https://api.paygentic.io description: Production API - url: https://api.sandbox.paygentic.io description: Sandbox API security: - BearerAuth: [] tags: - name: Customers description: >- A `Customer` is an entity connected to a `Merchant` via a `Subscription`. This represents the merchant-facing perspective of `Consumers` who purchase their `Products`. - name: Billable Metrics description: >- A `Billable Metric` defines a measurable quantity tied to a `Product`'s consumption. Each metric stores details including its label, an explanatory description, and measurement units. - name: Grants description: >- Grants credit a customer's metered entitlement balance. Merchants can create grants directly or void existing ones. Use `GET /v1/entitlements?customerId={id}` or `GET /v1/entitlements?subscriptionId={id}` to find the metered entitlement `id` needed for these endpoints. - name: Features description: >- A `Feature` represents a specific capability or functionality provided by a `Product`. Features can be metered (usage-based), static (fixed allocation), or boolean (enabled/disabled). - name: Fees description: >- A `Fee` defines a recurring or one-time charge tied to a `Product`. Fees are linked to prices, and cadence is defined on the Price. - name: Plans description: >- A `Plan` links a collection of `Prices` to a `Product`. It functions as a pricing structure document for a particular feature set or service offering. - name: Prices description: >- A `Price` determines the monetary value for a single unit of a `Billable Metric`. Prices are exclusively grouped within a `Plan`. - name: Products description: >- A `Product` is an offering sold by a `Merchant`. It includes product metadata like title, summary, and pricing details. `Plans`, `Prices`, and `Subscriptions` are all associated with products. - name: Sources description: >- A `Source` is an external data provider capable of automatically creating usage events. Configuration occurs at the plan level, enabling data retrieval from third-party platforms such as Stripe to produce billable events. - name: Subscriptions description: >- A `Subscription` is a customer's commitment to purchase a `Product` following the terms of a `Plan` and its linked `Prices`. - name: Users description: >- A `User` is an entity granted access to an Organization's resources. All operations are performed by users. - name: Invoices V2 description: >- Invoice V2 operations supporting billing cycles organized by time periods. Warning: v0 invoice endpoints are no longer supported. - name: Revenue description: Revenue data from invoices and payments - name: Profitability description: Per-customer profitability summaries - name: Test Clocks description: >- Test clocks provide programmable time control to simulate subscription and billing scenarios during testing. - name: Events description: Ingest raw metering events that are processed by the meters service. - name: Payments description: >- Create and manage one-off payments. A payment represents a single charge that a merchant wants to collect from a customer. - name: Payment Sessions description: >- Handle payment session lifecycle and processing across various entity types including invoices and subscriptions - name: Costs description: >- A Cost represents the operational or infrastructure expense of serving customers for a given product. Costs are metered (driven by event-based usage) and are tracked in parallel with billable metrics to give merchants visibility into both revenue and cost per customer. - name: ExternalReferences description: >- An `ExternalReference` links a Paygentic entity (e.g. an `Item`) to a record in an external system such as Salesforce or NetSuite. Multiple external records may map to the same Paygentic entity, but each external id is the *primary* reference of at most one entity per merchant. - name: Items description: >- An `Item` is the canonical "thing you sell" that external-system mappings point at. It is fully decoupled from the billing `Product` and holds no pricing/plan/metering, and it is CRM/ERP agnostic — which providers map to it lives entirely in its `ExternalReference` rows. - name: MerchantIntegrations description: >- A `MerchantIntegration` records a merchant's connection to an external provider. One connection per `(merchant, provider)` — re-connecting upserts in place. - name: Approvals description: Submit, decide, cancel, and read maker-checker approvals. - name: Orders description: Manage Orders, their line items, and billing schedules. - name: Billing Schedules description: >- Owner-polymorphic billing schedules with intervals and staged invoice projections. A BillingSchedule belongs to exactly one Order or one Subscription (XOR). Cadence lives on ScheduleIntervals (cadence-on-the-line). paths: /v2/invoices/{id}/lineItems: get: tags: - Invoices V2 summary: Get Line Items description: Get paginated line items for an invoice from the analytics service operationId: getInvoiceLineItems parameters: - in: path name: id required: true schema: type: string description: The invoice ID - in: query name: limit schema: type: integer default: 100 minimum: 1 maximum: 1000 description: Maximum number of line items to return - in: query name: pageToken schema: type: string description: Token for pagination to fetch the next page of results responses: '200': description: Paginated list of invoice line items content: application/json: schema: $ref: '#/components/schemas/InvoiceLineItemsResponse' example: invoiceId: inv_r1s2t3u4v5w6x7y8 lineItems: - eventType: usage eventId: usg_a1b2c3d4e5f6g7h8 eventSourceId: bm_l5m6n7o8p9q0r1s2 invoiceDisplayName: Claude Token Consumption lineItemType: charge meterEventId: me_x9y0z1a2b3c4d5e6 metricDescription: Language model token consumption metricName: Token Usage metricUnit: tokens quantity: 2500 taxRate: 0.085 totalAmount: '0.05425' totalPrice: '0.05' totalTax: '0.00425' unitPrice: '0.00002' - eventType: fee eventId: fee_b2c3d4e5f6g7h8i9 eventSourceId: fee_h3i4j5k6l7m8n9o0 invoiceDisplayName: Platform Fee meterEventId: '' metricDescription: Monthly platform fee metricName: Platform Fee metricUnit: charge quantity: 1 taxRate: 0.1 totalAmount: '5.50' totalPrice: '5.00' totalTax: '0.50' unitPrice: '5.00' nextPageToken: null totalCount: 3 '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' components: schemas: InvoiceLineItemsResponse: type: object required: - invoiceId - lineItems - totalCount properties: invoiceId: type: string description: The invoice ID lineItems: type: array description: Array of line items for this page items: $ref: '#/components/schemas/InvoiceLineItem' nextPageToken: type: string nullable: true description: Token for fetching the next page, null if no more pages totalCount: type: integer description: Total number of line items across all pages InvoiceLineItem: type: object required: - eventType - eventId - eventSourceId - billableMetricId - quantity - unitPrice - totalPrice - taxRate - totalTax - totalAmount - meterEventId - metricName - metricDescription - metricUnit - invoiceDisplayName - lineItemType properties: eventType: type: string enum: - usage - fee - discount description: >- Type of event: 'usage' for billable metric events, 'fee' for fee events, 'discount' for grant discount line items (subtotal/total are negative, representing a credit) eventId: type: string description: The event ID (usage_event_id or fee_event_id) eventSourceId: type: string description: >- Source ID: billable_metric_id for usage events, fee_id for fee events billableMetricId: type: string description: 'HOTFIX: Mirrors eventSourceId for backward compatibility' invoiceDisplayName: type: string description: Display name for this line item on invoices lineItemType: type: string enum: - charge - refund description: >- Type of line item: 'charge' for regular billing, 'refund' for refunded items (amounts are negated) meterEventId: type: string description: The meter event ID (usage events only) metricDescription: type: string description: Description of what this metric or fee measures metricName: type: string description: Human-readable name of the billable metric or fee metricUnit: type: string description: >- Measurement unit label. Sample values: 'calls' for API calls, 'GB' for storage, 'hours' for compute time, 'tokens' for LLM tokens, 'charge' for fees quantity: type: number description: Quantity of usage. Negative for refunds. taxRate: type: number description: Tax rate as decimal (0.10 = 10%) totalAmount: type: string description: >- Total amount (totalPrice + totalTax) in decimal dollars. Negative for refunds. totalPrice: type: string description: >- Total price (tax-exclusive) in decimal dollars. Negative for refunds. totalTax: type: string description: Total tax in decimal dollars. Negative for refunds. unitPrice: type: string description: Unit price in decimal dollars Error: type: object required: - message properties: error: type: string description: >- Coarse HTTP error category (e.g. 'bad_request', 'forbidden'). Maps to the HTTP status code. message: type: string description: >- Human-readable error message. Clients must not parse this field programmatically. code: type: string examples: - TAX_NOT_ENABLED - PAYMENT_SESSION_EXPIRED description: >- Optional semantic business error code for machine-readable discrimination (e.g. 'TAX_NOT_ENABLED'). UPPER_SNAKE_CASE. Clients should check this field, not message. details: type: object description: Additional error details additionalProperties: true example: message: The requested resource was not found error: not_found responses: Forbidden: description: Forbidden - Request is understood but refused content: application/json: schema: $ref: '#/components/schemas/Error' NotFound: description: Not Found - The requested resource could not be found content: application/json: schema: $ref: '#/components/schemas/Error' InternalServerError: description: Internal Server Error - Something went wrong on the server side content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: BearerAuth: type: http scheme: bearer description: API key authentication ````