> ## 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 accounts likely the same company > List the other accounts likely to be the same company as this one, to merge either way round, by fixed rules: the same LinkedIn company page, the same name once case, punctuation and a legal form like Inc go, or a domain registered under the same name (acme.com and acme.io). Strongest rule first, then most people; at most 5. Nothing is merged. ## OpenAPI ````yaml /openapi.json get /accounts/{account_key}/merge-suggestions/ 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/{account_key}/merge-suggestions/: get: tags: - accounts summary: List accounts likely the same company description: >- List the other accounts likely to be the same company as this one, to merge either way round, by fixed rules: the same LinkedIn company page, the same name once case, punctuation and a legal form like Inc go, or a domain registered under the same name (acme.com and acme.io). Strongest rule first, then most people; at most 5. Nothing is merged. operationId: list_account_merge_suggestions parameters: - in: path name: account_key required: true schema: $ref: '#/components/schemas/AccountKeyPath' responses: '200': content: application/json: schema: $ref: '#/components/schemas/AccountMergeSuggestionsReadSchema' 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 '404': content: application/json: schema: $ref: '#/components/schemas/NotFoundResponse' description: No account by that key in this workspace. '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: AccountKeyPath: description: >- The account's key: its domain (acme.com), or its LinkedIn page (li-co:acme). maxLength: 320 minLength: 1 pattern: ^(?:[^/.][^/]*|\.[^/.][^/]*|\.\.[^/]+)$ type: string AccountMergeSuggestionsReadSchema: description: >- The accounts likely the same company as one, strongest rule first (review AC-18). properties: suggestions: description: At most 5, strongest rule first, then most people. items: $ref: '#/components/schemas/AccountMergeSuggestionReadSchema' title: Suggestions type: array required: - suggestions title: AccountMergeSuggestionsReadSchema 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 NotFoundResponse: properties: detail: description: The detail of why the resource was not found. title: Detail type: string required: - detail title: NotFoundResponse 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 AccountMergeSuggestionReadSchema: description: Another account likely the same company, offered to merge, and why. properties: account: $ref: '#/components/schemas/AccountReadSchema' reason: $ref: '#/components/schemas/AccountMergeSuggestionReason' description: >- Why: same_linkedin_page (both name one LinkedIn company page), same_name (the names match once case, punctuation and a legal form like Inc go) or same_domain_name (acme.com and acme.io). required: - account - reason title: AccountMergeSuggestionReadSchema 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 AccountReadSchema: description: >- One account: a company, keyed by its domain, with every linked row that names it. properties: bounced_count: description: People here an email bounced from. title: Bounced Count type: integer company_row_count: description: How many company rows sit on it. title: Company Row Count type: integer domain: anyOf: - type: string - type: 'null' title: Domain employee_count: anyOf: - type: integer - type: 'null' description: 'The headcount as a number the list sorts by: a range''s low end.' title: Employee Count employees: anyOf: - type: string - type: 'null' description: >- The company's headcount as its page shows it: 35,000, or a range like 51-200. title: Employees has_activity: description: >- Whether anybody here was enrolled in a sequence or has a conversation. title: Has Activity type: boolean id: description: The account's id, stable while its key stays the same. format: uuid title: Id type: string in_sequence_count: description: People here live in a sequence now. title: In Sequence Count type: integer industry: anyOf: - type: string - type: 'null' description: The company's industry, as its page shows it. title: Industry key: description: >- The account's key: its domain (acme.com), or its LinkedIn page (li-co:acme) until a row ties that page to a domain. title: Key type: string last_touch_at: anyOf: - format: date-time type: string - type: 'null' description: >- When outreach last reached anybody here: the newest sequence step that went out or was done on a profile, or a reply, whichever is later. None when nobody was. title: Last Touch At linkedin_page: anyOf: - type: string - type: 'null' description: The company's LinkedIn page key, if known. title: Linkedin Page logo_path: anyOf: - type: string - type: 'null' description: >- The company's logo, a path under this API's address that needs no credentials (`/accounts/logos/{name}/`). Null until one is found for its website: opening Accounts looks for the logos due in the background. title: Logo Path name: title: Name type: string newest_row_at: description: When the newest row on it was made. format: date-time title: Newest Row At type: string owner_email: anyOf: - type: string - type: 'null' description: The owner's email, if known. title: Owner Email owner_name: anyOf: - type: string - type: 'null' description: >- Who owns its company record in a connected CRM, as the CRM names them; null when no CRM record names an owner, or the CRM has not said who that is. title: Owner Name owner_tool: anyOf: - type: string - type: 'null' description: >- The CRM its owner comes from (Salesforce); set whenever a record names one. title: Owner Tool people_count: description: How many people sit on it, each counted once. title: People Count type: integer replied_count: description: People here who replied, each counted once. title: Replied Count type: integer search_match: anyOf: - $ref: '#/components/schemas/AccountSearchMatchReadSchema' - type: 'null' description: >- Why a search found it when its name and domain do not hold the search; null otherwise, and with no search. table_count: description: How many linked tables hold a row on it. title: Table Count type: integer required: - id - key - name - domain - linkedin_page - table_count - company_row_count - people_count - has_activity - newest_row_at - last_touch_at - replied_count - bounced_count - in_sequence_count - industry - employees - employee_count title: AccountReadSchema type: object AccountMergeSuggestionReason: description: Why another account is offered as the same company, strongest first. enum: - same_linkedin_page - same_name - same_domain_name title: AccountMergeSuggestionReason type: string AccountSearchMatchReadSchema: description: >- Why the list's search found an account its own name and key do not hold (review AC-26). properties: kind: $ref: '#/components/schemas/AccountSearchMatchKind' description: >- `person`: a person on it is named so; `merged_account`: an account merged into it has this website or LinkedIn page; `row_name`: another row names the company so. value: description: The person's name, the merged account's website, or the name. title: Value type: string required: - kind - value title: AccountSearchMatchReadSchema type: object AccountSearchMatchKind: description: >- Why the list's search found an account its own name and key do not hold (review AC-26). enum: - person - merged_account - row_name title: AccountSearchMatchKind 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.