> ## Documentation Index > Fetch the complete documentation index at: https://docs.getoneprofile.ai/llms.txt > Use this file to discover all available pages before exploring further. # List account sources > List every table the Accounts page has looked at, and for each whether it feeds accounts, which columns its rows are read through and why, or why it does not, and the rows it leaves on no account and why (`left_off`). ## OpenAPI ````yaml /openapi.json get /accounts/sources/ openapi: 3.1.0 info: contact: email: support@getoneprofile.ai name: Oneprofile Support description: >- REST API reference for Oneprofile, the GTM data layer for your CRM. Manage tables, enrichments, and integrations. Authenticate with an API key to get started. termsOfService: https://www.getoneprofile.ai/terms title: API Reference | Oneprofile version: '0.0' servers: - url: https://api.getoneprofile.ai security: [] tags: - description: >- The docked AI Assistant: its general chat about the workspace and the product, streamed as Server-Sent Events, and the one list of a person's threads across every assistant, with pin, rename, delete and the search-to-table link. name: assistant - description: >- The messages a person keeps to send the assistant again: the ones the workspace saved and the ones that ship with the product, with save, rename, edit and delete. name: assistant-prompt - description: >- Granted workspace actions: what the AI Assistant proposed or applied in a conversation, the approve and dismiss decisions on each card, the workspace's spend threshold and default grants, and the eight verbs. name: workspace-actions - description: >- The Getting started checklist: a workspace's progress through the six steps from its first people search to its first launched sequence. name: onboarding - description: Senders, connected mailboxes, tags, and the Google connect flow. name: senders - description: The workspace do-not-contact list, enforced before every send. name: suppression - description: >- The workspace's recontact rule: how long before anyone hears from us again. name: contact_cooldown - description: 'Sequence authoring: the graph, the table-backed audience, previews.' name: sequences - description: >- The outbound agent behind a sequence: the voice it writes in, its per-message prompts, what it wrote and what people told it. name: outbound-agents - description: >- The LinkedIn channel: connecting an account to a sender, its safety limits and history, and the protocol the browser extension speaks. name: linkedin - description: >- The approval queue: everything waiting on a person across every sender and channel, and the workspace's manual or automatic modes per channel. name: outreach - description: 'The unified outreach inbox: threads, replies, labels, events.' name: inbox - description: 'The AI reply layer: workspace settings, drafts, and approval.' name: inbox-ai - description: Notification rules, per-user preferences, and the Slack connection. name: notifications - description: Endpoints for seeing all available integration types. name: integration-types - description: Endpoints for listing, checking and deleting integrations. name: integrations - description: >- Create, preview and update an integration of any type: the body's integration_type picks the config and credentials it takes. name: integration-specific - description: Endpoints for the generic OAuth install/claim app-listings engine. name: app-listings - description: Endpoints for creating and managing API keys. name: apikey - description: >- AI apps connected to the workspace: Claude, ChatGPT, Claude Code or any other MCP client a person signed in to Oneprofile's MCP server with. name: ai_apps - description: Endpoints for managing billing and subscription information. name: billing - description: >- Accounts: every company the workspace's tables name, with the people at it, its key facts, its tables, its org chart and what went to its people; the tables that feed it (Sources) and the merges a person made. name: accounts - description: Endpoints for creating and managing tables. name: tables - description: Endpoints for table columns, formula previews, and on-demand column runs. name: table-columns - description: Endpoints for table rows and manual cell edits. name: table-rows - description: Endpoints for observing and cancelling table recompute runs. name: table-runs - description: >- Endpoints for org-shared per-column display preferences: hidden, pinned, width, and colour tint. name: table-ui-prefs - description: >- Endpoints for the org-shared names given to the column tint palette: what this organisation calls each colour. Org-level, not per-table. name: table-column-color-labels - description: >- Endpoints for the enrichment action catalog, model list, presets, draft generation, and saved agents. name: table-enrichments - description: >- Endpoints for an agent's Preview: example rows run one at a time, and a Looks good on each. Needs work lives under agent-learnings. name: agent-training - description: >- An agent's learnings, the one-line rules it follows on every output, and the thumbs down that teaches them: give one with what was wrong, list the ones on a subject, Undo one, and price the redo it would run. name: agent-learnings - description: >- The durable audit trail of a table's enrichment actions: configured, edited, run, cancelled, and settled cost. name: table-enrichment-audit-logs - description: Endpoints for saving and applying column templates. name: table-templates - description: Server-sent change feed for a table's grid. name: table-events - description: 'Endpoints for org-shared saved table views: sort, filters, hidden columns.' name: table-views - description: >- Endpoints for PER-USER table preferences: favourites and recently opened. Unlike the rest of the table surface these are personal, so two members of one organisation legitimately see different answers. name: table-user-prefs - description: >- Endpoints for building a table from an uploaded CSV: upload and preview the inferred columns, commit the reviewed mapping, then poll the row load. name: table-imports - description: Endpoint for downloading a table's rows as CSV. name: table-export - description: >- Endpoints for the integration a table imports from: attach and preview it, promote imported fields into columns, and run the import on demand. name: table-sources - description: >- Endpoints for a table's recurring import cadence: set it, pause it, and read the next fire times. name: table-schedules - description: >- Endpoints for pushing a table's rows out to a connected integration: list writable destinations, derive their write capabilities, and map export columns. name: table-writeback - description: >- Endpoints backing a lookup column's setup: the connections whose records a column could read, and the identity fields one record type can be looked up by. name: table-integration-lookup - description: >- Endpoints for sourcing leads from the lead database: count and preview matches, land them in a table, and keep saved searches. Alongside people and company searches, leads can be sourced from buying signals (what a company or person just did), with a catalogue endpoint behind the picker that builds them. name: find-leads - description: >- Endpoints for discovering a domain's subdomains from public certificate logs and landing the results in a table. name: find-subdomains - description: Endpoints for the credit balance meter and usage reporting. name: credits - description: >- Endpoints for the workspace referral program: the shareable link, the friends who joined through it, and claiming a code after signup. name: referral - description: >- Endpoints for the affiliate program's own dashboard: enrolling and claiming a code, the summary, stats and activity feed, the commission ledger, and identity verification and payouts. name: affiliate - description: >- Endpoints for recording where a new workspace came from: the marketing page or campaign its signup link carried, sent once after signup. name: attribution - description: >- Endpoints for the design partner program's customer surface: whether this workspace is a design partner, the badges its feedback has earned, and sending and reading that feedback. name: design-partner - description: >- Endpoints for the org-level AI business context (company description, ideal customer profile, buyer personas, interest signals and social proof), plus domain-based generation and the reference documents whose summaries ride alongside those fields. name: ai-context - description: >- Endpoints for the signed-in user's Google Drive connection: starting and finishing the OAuth grant, checking or dropping it, and minting the short-lived token the Google Picker needs. name: google-drive paths: /accounts/sources/: get: tags: - accounts summary: List account sources description: >- List every table the Accounts page has looked at, and for each whether it feeds accounts, which columns its rows are read through and why, or why it does not, and the rows it leaves on no account and why (`left_off`). operationId: list_account_sources parameters: - description: The number of items to return. in: query name: limit required: false schema: default: 10 description: The number of items to return. maximum: 100 minimum: 1 title: Limit type: integer - in: query name: order_by required: false schema: $ref: '#/components/schemas/OrderingParametersForName' default: name enum: - name type: string - in: query name: order_direction required: false schema: default: asc enum: - asc - desc title: Order Direction type: string - description: >- Set the cursor to the next or previous page. You can get the cursor from the previous page's response. in: query name: cursor required: false schema: anyOf: - type: string - type: 'null' description: >- Set the cursor to the next or previous page. You can get the cursor from the previous page's response. title: Cursor for pagination. responses: '200': content: application/json: schema: $ref: >- #/components/schemas/PaginatedResponse_AccountSourceReadSchema_ description: Successful Response '401': content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' description: Unauthorized '403': content: application/json: schema: $ref: '#/components/schemas/ForbiddenResponse' description: Forbidden '422': content: application/json: schema: $ref: '#/components/schemas/UnprocessableEntityResponse' description: Invalid request made to the API. '500': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Internal server error. '502': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Bad gateway error. '503': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Service unavailable. security: - APIKeyHeader: [] - HTTPBearer: [] components: schemas: OrderingParametersForName: enum: - name title: OrderingParametersForName type: string PaginatedResponse_AccountSourceReadSchema_: properties: data: description: The list of ResponseItems. items: $ref: '#/components/schemas/AccountSourceReadSchema' title: Data type: array next_page_cursor: anyOf: - type: string - type: 'null' description: >- The cursor to the next page. If there are no more pages, this is None. previous_page_cursor: anyOf: - type: string - type: 'null' description: >- The cursor to the previous page. If there are no previous pages, this is None. title: PaginatedResponse[AccountSourceReadSchema] type: object UnauthorizedResponse: properties: detail: description: The detail of why the request is unauthorized. title: Detail type: string required: - detail title: UnauthorizedResponse type: object ForbiddenResponse: properties: detail: description: The detail of why the request is forbidden. title: Detail type: string required: - detail title: ForbiddenResponse type: object UnprocessableEntityResponse: properties: detail: description: >- The detail of the error. This is the error message to show to the user. You should also use the issues field to show more detailed error messages per field. Use this field for a single liner error message. title: Detail type: string issues: description: >- The issues that caused the error. There can be multiple issues. Each issue is a user-facing error message. items: $ref: '#/components/schemas/UnprocessableEntityIssue' title: Issues type: array required: - detail - issues title: UnprocessableEntityResponse type: object ServerErrorResponse: properties: detail: description: The detail of why the server returned an error. title: Detail type: string required: - detail title: ServerErrorResponse type: object AccountSourceReadSchema: description: One table's standing on the Accounts page, and why. properties: account_count: description: The accounts its rows sit on, at the last index. title: Account Count type: integer awaits_index: description: >- Whether an index of the table is on its way: it was looked at and is not indexed yet, in a workspace whose Accounts were opened. Its counts arrive when this turns false; false in a workspace that never opened Accounts, where nothing indexes it. title: Awaits Index type: boolean candidates: description: >- The columns a person may choose as the company column: the two that disagree when two website columns do, otherwise the one chosen, the columns that read as a website, a company LinkedIn page or a work email, then every other text, link or address column that is not a name, a profile, a manager or a company fact such as Industry. items: $ref: '#/components/schemas/AccountSourceCandidateReadSchema' title: Candidates type: array columns: description: The columns its rows are read through, and why each. items: $ref: '#/components/schemas/AccountSourceColumnReadSchema' title: Columns type: array company_column_id: anyOf: - format: uuid type: string - type: 'null' title: Company Column Id indexed_at: anyOf: - format: date-time type: string - type: 'null' description: When it was last indexed; None before then. title: Indexed At left_off: description: >- Its rows on no account at the last index, by what they lack (`company_name_only`: a company name but no website, company page or work address; `personal_email`: only a personal address such as Gmail; `no_company`: nothing that names a company), each with the first such row; its rows number `row_count` plus these. Empty before an index counted them. items: $ref: '#/components/schemas/AccountLeftOffReadSchema' title: Left Off type: array manager_candidates: description: >- Columns that may hold each person's manager, by their label, for a person to pick as the manager column. items: $ref: '#/components/schemas/AccountSourceCandidateReadSchema' title: Manager Candidates type: array manager_column_id: anyOf: - format: uuid type: string - type: 'null' title: Manager Column Id manager_options: description: >- Every column a person may pick as a people table's manager column: the suggested ones first, then each other column that could name a person (never the row's own name, title, profile, address or company, a website, a company fact, the Person researcher's or a column a sequence or an export writes), and the one chosen. A company table offers only the one chosen. items: $ref: '#/components/schemas/AccountSourceCandidateReadSchema' title: Manager Options type: array reason: anyOf: - $ref: '#/components/schemas/AccountLinkReason' - type: 'null' description: Why the table is not linked, if not. row_count: description: Its rows on an account, at the last index. title: Row Count type: integer row_kind: $ref: '#/components/schemas/AccountRowKind' show_on_accounts: title: Show On Accounts type: boolean sole_account_key: anyOf: - type: string - type: 'null' description: >- The one account its rows are on, when `account_count` is 1; read by `GET /accounts/sources/{table_id}/` alone, null in the list. title: Sole Account Key status: $ref: '#/components/schemas/AccountLinkStatus' table_id: format: uuid title: Table Id type: string table_name: title: Table Name type: string required: - table_id - table_name - status - reason - row_kind - columns - candidates - manager_candidates - manager_options - show_on_accounts - company_column_id - manager_column_id - row_count - account_count - left_off - indexed_at - awaits_index title: AccountSourceReadSchema type: object UnprocessableEntityIssue: properties: input: anyOf: - type: string - type: integer - type: number - type: boolean - items: {} type: array - additionalProperties: true type: object description: The user's input that caused the error. title: Input loc: description: >- The location of the error. Always contains 1 or 2 elements. The first element is the type of location (e.g. 'body', 'query', 'path', 'header'). The second element is the name of the field that caused the error. If the error is not related to a specific field, the second element is not present. items: type: string title: Loc type: array msg: description: The message of the error. The error message to show to the user. title: Msg type: string type: description: >- The type of the error. Useful for frontend code to handle different types of errors. title: Type type: string required: - loc - msg - type - input title: UnprocessableEntityIssue type: object AccountSourceCandidateReadSchema: description: A company column a person is asked to choose, when two disagree. properties: column_id: format: uuid title: Column Id type: string column_name: title: Column Name type: string required: - column_id - column_name title: AccountSourceCandidateReadSchema type: object AccountSourceColumnReadSchema: properties: column_id: format: uuid title: Column Id type: string column_name: title: Column Name type: string evidence: $ref: '#/components/schemas/AccountColumnEvidence' description: >- Why: a person chose it, a search or formula made it, an enrichment promoted it, its values read that way, or its label. role: $ref: '#/components/schemas/AccountColumnRole' required: - column_id - column_name - role - evidence title: AccountSourceColumnReadSchema type: object AccountLeftOffReadSchema: description: A linked table's rows on no account for one reason (review AC-20). properties: reason: $ref: '#/components/schemas/AccountLeftOffReason' record_id: description: The first of them, for a link to it in its table. format: uuid title: Record Id type: string row_count: description: How many rows. title: Row Count type: integer required: - reason - row_count - record_id title: AccountLeftOffReadSchema type: object AccountLinkReason: description: >- Why a table is not linked, in words the Sources panel and the table badge print. A linked table carries no reason. Archived tables stay linked (Utku, 2026-11-01): archiving tidies the Tables list, it does not retire the data. enum: - no_company_column - two_company_columns - turned_off title: AccountLinkReason type: string AccountRowKind: description: >- What one row of a linked table stands for on an account: the company, or a person there. enum: - company - person title: AccountRowKind type: string AccountLinkStatus: description: Whether a table's rows feed the Accounts page. enum: - linked - not_linked title: AccountLinkStatus type: string AccountColumnEvidence: description: >- How a column's role was known, strongest first. A lead search's own columns and a person's choice are known for certain; an enrichment's outputs are what the catalog declares; values are read from a sample of the column's cells; a label is used for display columns only. enum: - chosen - structural - enrichment - values - label title: AccountColumnEvidence type: string AccountColumnRole: description: What a column of a linked table is read as. enum: - website - company_page - email - profile - name - first_name - last_name - title - company_name - manager title: AccountColumnRole type: string AccountLeftOffReason: description: >- Why a row of a linked table is on no account, in words Sources and the table badge print. A fixed rule, read off the cells the decision reads (review AC-20: a Gmail row was dropped silently, and the badge said only "On 1 account"). enum: - company_name_only - personal_email - no_company title: AccountLeftOffReason type: string securitySchemes: APIKeyHeader: in: header name: X-API-Key type: apiKey HTTPBearer: scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.