> ## 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. # Create a table from a signal search > Run a signal search and land its companies in a new table, one row per company with the newest matching signal on it. The row count is capped per run and further clamped by the plan's rows-per-table limit. ## OpenAPI ````yaml /openapi.json post /find-signals/tables/ 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: Sender profiles, connected mailboxes, tags, and the Google connect flow. name: senders - description: The workspace do-not-contact list, enforced before every send. name: suppression - description: 'Sequence authoring: the graph, the table-backed audience, previews.' name: sequences - 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 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 creating and managing integrations. name: integrations - 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: Endpoints for managing billing and subscription information. name: billing - 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 teaching a saved agent from example rows: training sessions, per-row feedback, and the proposed prompt to approve. name: agent-training - 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: >- The per-table AI Assistant: named conversations, the column suggestions a build turn produces, and the questions an analyze turn answers. name: table-assistant - 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 — and from buying intent on a topic, each with its own catalogue endpoint behind the picker that builds it. 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 sourcing companies by buying signal — who is hiring, in the news, adopting a technology, newly listed as a portfolio company, raising money or shipping a product — plus two firmographic searches. Preview a signal, land it in a table one row per company, and re-run it later to refresh what those companies have done since. name: find-signals - 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 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 and interest signals — plus domain-based generation. name: ai-context paths: /find-signals/tables/: post: tags: - find-signals summary: Create a table from a signal search description: >- Run a signal search and land its companies in a new table, one row per company with the newest matching signal on it. The row count is capped per run and further clamped by the plan's rows-per-table limit. operationId: create_table_from_signal_search requestBody: content: application/json: schema: $ref: '#/components/schemas/CreateTableFromSignalSearchRequestSchema' required: true responses: '201': content: application/json: schema: $ref: '#/components/schemas/CreateTableFromSignalSearchResponseSchema' description: Successful Response '401': content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' description: Unauthorized '402': content: application/json: schema: $ref: '#/components/schemas/PaymentRequiredResponse' description: >- The plan does not include signal search, or does not allow a table this size. '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: CreateTableFromSignalSearchRequestSchema: description: Run a signal search and land it in a new table. properties: query: $ref: '#/components/schemas/SignalQuerySchema' row_limit: anyOf: - minimum: 1 type: integer - type: 'null' description: >- Company rows to land. Clamped by the product's own ceiling and by the plan's rows-per-table limit; null uses the product default. title: Row Limit signal_type: $ref: '#/components/schemas/SignalType' table_name: maxLength: 255 minLength: 1 title: Table Name type: string required: - signal_type - table_name title: CreateTableFromSignalSearchRequestSchema type: object CreateTableFromSignalSearchResponseSchema: description: The table a signal search was turned into. properties: rows_created: title: Rows Created type: integer rows_matched: description: >- Companies the search returned. Larger than rows_created when some of them were already in the table. title: Rows Matched type: integer table_id: format: uuid title: Table Id type: string table_name: title: Table Name type: string technology: anyOf: - $ref: '#/components/schemas/ResolvedTechnologySchema' - type: 'null' required: - table_id - table_name - rows_created - rows_matched - technology title: CreateTableFromSignalSearchResponseSchema type: object UnauthorizedResponse: properties: detail: description: The detail of why the request is unauthorized. title: Detail type: string required: - detail title: UnauthorizedResponse type: object PaymentRequiredResponse: properties: detail: description: The detail of why payment is required. title: Detail type: string required: - detail title: PaymentRequiredResponse 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 SignalQuerySchema: description: >- Every filter any signal type can take. ONE schema for all eight types, mirroring the domain's single query dataclass. Which of these a given signal type actually accepts is decided by the domain's per-type allow-list, and a filter the type cannot use is REJECTED with a 422 naming it — never quietly dropped. An empty query is valid here. Discovery is bounded by the row cap rather than by the filters, so "the companies that most recently raised" is a legitimate search. properties: categories: description: Event categories — job function, news category, product category. items: maxLength: 255 minLength: 1 type: string maxItems: 25 title: Categories type: array countries: description: Company countries. items: maxLength: 255 minLength: 1 type: string maxItems: 25 title: Countries type: array employees_max: anyOf: - minimum: 0 type: integer - type: 'null' description: Largest headcount. title: Employees Max employees_min: anyOf: - minimum: 0 type: integer - type: 'null' description: Smallest headcount. title: Employees Min financing_types: description: Funding round types. items: maxLength: 255 minLength: 1 type: string maxItems: 25 title: Financing Types type: array found_at_from: anyOf: - format: date type: string - type: 'null' description: Only events first seen on or after this date. title: Found At From found_at_until: anyOf: - format: date type: string - type: 'null' description: Only events first seen on or before this date. title: Found At Until founded_year_max: anyOf: - maximum: 2200 minimum: 1800 type: integer - type: 'null' description: Latest founding year. title: Founded Year Max founded_year_min: anyOf: - maximum: 2200 minimum: 1800 type: integer - type: 'null' description: Earliest founding year. title: Founded Year Min industries: description: Company industries. items: maxLength: 255 minLength: 1 type: string maxItems: 25 title: Industries type: array job_locations: description: Locations to match against open roles. items: maxLength: 255 minLength: 1 type: string maxItems: 25 title: Job Locations type: array job_titles: description: Job titles to match against open roles. items: maxLength: 255 minLength: 1 type: string maxItems: 25 title: Job Titles type: array revenue_max: anyOf: - minimum: 0 type: integer - type: 'null' description: Largest annual revenue. title: Revenue Max revenue_min: anyOf: - minimum: 0 type: integer - type: 'null' description: Smallest annual revenue. title: Revenue Min tags: description: Company tags. items: maxLength: 255 minLength: 1 type: string maxItems: 25 title: Tags type: array technology: anyOf: - maxLength: 255 minLength: 1 type: string - type: 'null' description: >- Technology to look for adoption of. Resolved to the provider's own entry, which comes back on the response so a wrong match is visible. title: Technology title: SignalQuerySchema type: object SignalType: description: >- Which buying signal a search is looking for. Each member names one discovery question the provider can answer, and each maps to exactly one upstream endpoint. The last two are firmographic rather than event-shaped — they find companies by what they ARE rather than by what they DID — and are kept in the same enum because they land the same company rows through the same machinery. enum: - hiring - news - technology - portfolio_companies - financing - products - firmographics - extended_firmographics title: SignalType type: string ResolvedTechnologySchema: description: The provider's own entry for the technology that was searched. properties: id: title: Id type: string name: description: >- The technology as the provider names it. Compare it with what you typed: a fuzzy match can land somewhere unexpected. title: Name type: string required: - id - name title: ResolvedTechnologySchema 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 securitySchemes: APIKeyHeader: in: header name: X-API-Key type: apiKey HTTPBearer: scheme: bearer type: http ````