> ## Documentation Index > Fetch the complete documentation index at: https://entendre.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # List integrations > Shows the connection status of every supported provider, connected or not. Each entry is one provider, such as Stripe, Slack, Plaid or QuickBooks. A provider without a connection is returned with `connected: false` and `count: 0`. A provider with `unavailable: true` could not be read, so its state is unknown. The status comes from the stored connection record, not a live check of the provider. To manage one connection by its ID, use [List connections](/docs/api-reference/integrations/connections/list-connections). ## OpenAPI ````yaml openapi-public-preview.json GET /v1/integrations openapi: 3.1.0 info: title: Entendre API version: 1.0.0 description: Programmatic access to crypto-native accounting and treasury operations. servers: - url: https://api.entendre.finance description: Production API. security: - ApiKey: [] tags: - name: Organization description: Read your organization profile and find members for agent assignments. - name: Transactions description: Find transactions, inspect their details and create manual records. - name: Sources description: >- Manage wallets, exchange accounts, bank accounts and other transaction sources. - name: Assets description: Inspect asset acquisitions, remaining quantities and cost basis. - name: Journals description: >- Create and post journal entries, correct eligible entries and sync posted journals to a connected general ledger. - name: Documents description: >- Upload documents, check processing status and link supporting evidence to transactions. - name: Legal Entities description: Manage the legal entities used in your accounting records. - name: Ledger Accounts description: Manage your chart of accounts and find accounts for journal entries. - name: Tags description: Create and manage tags to classify your records. - name: Accruals description: >- Create and post accruals, inspect their status and reverse eligible entries. - name: Cash Application description: Match deposits to invoices and manage the resulting cash applications. - name: Classification description: >- Classify transactions in a batch, post eligible entries and inspect the results. - name: Revaluation description: Run asset revaluations for an accounting period and check their results. - name: Accounting Periods description: Check whether a period is ready to close, then close or reopen it. - name: Income Statement description: View revenue, expenses and net income for a reporting period. - name: Balance Sheet description: View assets, liabilities and equity as of a reporting date. - name: Trial Balance description: Review ledger account balances and debit and credit totals. - name: Closing Positions description: View asset positions at the end of a reporting period. - name: Treasury Balances description: Review treasury balances by asset and source. - name: Realized Gains & Losses description: Review realized gains and losses from asset dispositions. - name: Asset Tax Lots description: Inspect asset tax lots, remaining quantities and cost basis. - name: Schedule of Dispositions description: >- Review asset dispositions and their proceeds, cost basis and gains or losses. - name: Financial Insights description: Review financial insights for your selected reporting context. - name: Agents description: Create agents, schedule their work and inspect their runs. - name: Memory description: Read, search and maintain the memory files your agents use. - name: Connections description: Connect providers, manage authorization and disconnect. - name: GL Mapping description: >- Map ledger accounts and legal entities to your ERP. Import legal entities, tags and chart of accounts. - name: Request description: Request information, documents or connections from a client. - name: Client description: Manage your firm’s client relationships. - name: Team description: Invite team members and manage their access to your firm. - name: Settings description: Read and update your firm settings. paths: /v1/integrations: get: tags: - Connections summary: List integrations description: >- Returns one entry for each supported provider, connected or not: accounting (QuickBooks, Xero, NetSuite, DualEntry, Campfire, Intuit vendor login), cards (Ramp, Rain), receivables (Stripe, Request Finance), banking (Plaid), payroll (Finch), custody (Fireblocks) and communication (Gmail, Slack). Each entry has `connected`, the number of connections and each connection with its status and legal entity. A provider whose status could not be read has `unavailable: true`; its state is unknown, not disconnected. The status comes from the stored connection record. It is not a live check of the provider. The list is not paginated: `has_more` is always false. operationId: list_integrations parameters: - name: provider in: query required: false description: >- Providers to return, separated by commas, for example `stripe,slack`: quickbooks, xero, netsuite, dualentry, campfire, intuit, ramp, raincards, stripe, requestfinance, plaid, finch, fireblocks, gmail or slack. An unknown value returns 400. schema: type: string example: stripe,slack - name: category in: query required: false description: >- Categories to return, separated by commas: accounting, cards, banking, payroll, receivables, custody or communication. With `provider`, a provider must match both filters. An unknown value returns 400. schema: type: string example: accounting - name: connected in: query required: false description: >- When true, return only providers with an active connection. When false, only providers without one. Providers with `unavailable: true` are not returned by either value. schema: type: boolean - name: legal_entity_id in: query required: false description: >- Return only connections of this legal entity. An ID that is not in your organization returns 404. Providers whose connections have no legal entity return no connections. schema: type: string example: le_507f1f77bcf86cd799439012 - name: limit in: query required: false description: >- Accepted for a uniform list call and ignored: this list has no pagination. schema: type: integer minimum: 1 maximum: 100 default: 25 - name: cursor in: query required: false description: >- Accepted for a uniform list call and ignored: this list has no pagination. schema: type: string responses: '200': description: The request succeeded. headers: X-Request-Id: description: Support correlation ID. schema: type: string content: application/json: schema: type: object properties: data: type: array items: $ref: '#/components/schemas/Integration' description: One entry per provider. has_more: type: boolean description: Always false. The list is not paginated. next_cursor: type: - string - 'null' description: Always null. The list is not paginated. total_count: type: integer description: Number of providers returned. required: - data - has_more - next_cursor - total_count additionalProperties: false example: data: - provider: stripe category: receivables connected: true count: 1 connections: - id: sar_507f1f77bcf86cd799439011 status: active legal_entity_id: le_507f1f77bcf86cd799439012 legal_entity_name: Acme Inc external_id: acct_1Nxyz external_name: Acme Inc connected_at: '2026-03-02T10:15:00.000Z' last_activity_at: '2026-09-20T08:00:00.000Z' - provider: slack category: communication connected: false count: 0 connections: [] has_more: false next_cursor: null total_count: 2 '400': description: >- The request is invalid. `error.fields` lists the fields to correct. Nothing was changed. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: VALIDATION_ERROR message: Invalid path, query or request body. request_id: req_example '401': description: The API key is missing, invalid or expired. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: UNAUTHORIZED message: Authentication is required. request_id: req_example '403': description: >- The API key does not have the required scope or is not associated with a user, or the action needs a review in the dashboard. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: FORBIDDEN message: Insufficient access to organization request_id: req_example '404': description: The resource does not exist, or your organization cannot access it. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: RESOURCE_NOT_FOUND message: Resource not found request_id: req_example '429': description: >- Too many requests. If the response has a `Retry-After` header, wait that many seconds before you retry. Otherwise, read `error.message`. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: RATE_LIMITED message: Rate limit exceeded. Retry after 30s. request_id: req_example '500': description: >- An unexpected error occurred. A write can still have taken effect; check the resource before you retry. Give the `request_id` to support. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: INTERNAL_ERROR message: Internal server error request_id: req_example '503': description: >- A service that this operation needs is unavailable. If the response has a `Retry-After` header, wait that many seconds. Check for earlier accepted work before you send the request again. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: SERVICE_UNAVAILABLE message: Service unavailable. request_id: req_example components: schemas: Integration: type: object description: The connection status of one provider. properties: provider: type: string description: Provider key. example: stripe category: type: string enum: - accounting - cards - banking - payroll - receivables - custody - communication connected: type: boolean description: True when at least one connection is `active`. count: type: integer description: Number of connection records for this provider. unavailable: type: boolean description: >- Present and true when the status could not be read. The state is unknown, not disconnected. connections: type: array items: $ref: '#/components/schemas/IntegrationConnection' required: - provider - category - connected - count - connections additionalProperties: false ErrorResponse: type: object required: - error properties: error: type: object required: - code - message - request_id properties: code: type: string description: Machine-readable error code. message: type: string description: Technical description for developers. fields: type: object additionalProperties: type: string description: >- Present only on VALIDATION_ERROR. Maps failing field paths to reason strings. details: type: object additionalProperties: true description: >- Optional redacted diagnostic details. Request validation uses fields or field_errors. suggested_action: type: string description: A suggested next step. documentation_url: type: string format: uri description: Link to documentation about this error. request_id: type: string description: Unique request ID for support escalation. description: Error details. IntegrationConnection: type: object description: One stored connection of a provider. properties: id: type: - string - 'null' description: Connection ID, or null when the provider has no connection ID. status: type: string enum: - active - expired - error - disconnected - inactive - pending description: >- Status of the stored connection record. It is not a live check of the provider. legal_entity_id: type: - string - 'null' description: >- Legal entity of the connection, or null for providers that connect at organization level. legal_entity_name: type: - string - 'null' external_id: type: - string - 'null' description: Provider-side ID. For a GL provider, the realm or tenant ID. external_name: type: - string - 'null' connected_at: type: - string - 'null' format: date-time last_activity_at: type: - string - 'null' format: date-time required: - id - status - legal_entity_id - legal_entity_name - external_id - external_name - connected_at - last_activity_at additionalProperties: false securitySchemes: ApiKey: type: apiKey in: header name: X-API-Key description: >- Your organization API key. Some operations also need a key that is associated with a user; their pages say so. ````