> ## Documentation Index > Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get a single company > Retrieve a single company by ID. Responses include direct Enginy app URLs when available. The returned company includes an `appUrl` field. MCP agents should return those URLs to users whenever they are present in the response. > **Required scope:** `COMPANIES_READ` > > **Rate limit:** 100 requests per minute ## OpenAPI ````yaml https://openapi.enginy.ai/definitions.json get /v1/company/{companyId} openapi: 3.1.0 info: title: Enginy API version: 1.0.0 description: Public API for Enginy platform servers: - url: https://openapi.enginy.ai description: Configured server security: [] tags: - name: AI Variables description: >- Manage AI variables and discover the entity fields you can reference in prompts and entity requests. - name: Inbox description: >- Inbox endpoints for listing contact threads, reading thread messages, managing tags, and sending manual replies. - name: Workflows description: >- Build, validate, publish, run, and inspect advanced (graph) workflows, plus the block/condition catalog needed to author a workflow plan. paths: /v1/company/{companyId}: get: tags: - Companies summary: Get a single company description: >- Retrieve a single company by ID. Responses include direct Enginy app URLs when available. The returned company includes an `appUrl` field. MCP agents should return those URLs to users whenever they are present in the response. > **Required scope:** `COMPANIES_READ` > > **Rate limit:** 100 requests per minute parameters: - schema: type: string description: The company ID required: true description: The company ID name: companyId in: path - schema: anyOf: - type: string - type: array items: type: string description: >- Specific company fields to include in the response (comma-separated or array). Use `GET /v1/companies/fields` (MCP tool `get_company_field_metadata`) to discover valid company field names. required: false description: >- Specific company fields to include in the response (comma-separated or array). Use `GET /v1/companies/fields` (MCP tool `get_company_field_metadata`) to discover valid company field names. name: fields in: query responses: '200': description: Successful response with company details content: application/json: schema: type: object properties: status: type: string enum: - success message: type: string data: type: object properties: id: type: number description: Unique identifier for the company appUrl: type: string format: uri description: Direct Enginy app URL for opening this company. name: type: - string - 'null' description: Company name domain: type: - string - 'null' description: Company website domain website: type: - string - 'null' description: Company website URL companyLinkedInUrl: type: - string - 'null' description: Company LinkedIn URL industry: type: - string - 'null' description: Industry sector rangeOfEmployees: type: - string - 'null' description: Range of employees (e.g., "11-50") numberOfEmployees: type: - number - 'null' description: Exact number of employees yearfounded: type: - string - 'null' description: Year the company was founded description: type: - string - 'null' description: Company description country: type: - string - 'null' description: Company country city: type: - string - 'null' description: Company city streetAddress: type: - string - 'null' description: Company street address phoneNumber: type: - string - 'null' description: Company phone number companyEmail: type: - string - 'null' description: Company email address revenueRange: type: - string - 'null' description: Company revenue range hiringOnLinkedIn: type: boolean description: Whether the company is actively hiring on LinkedIn openJobPositions: type: - number - 'null' description: Number of open job positions companyCRMId: type: - string - 'null' description: CRM company ID isCompanyInCRM: type: boolean description: Whether the company is synced with CRM contactsCount: type: number description: >- Number of contacts (leads) associated with this company. lastContactedAt: type: - string - 'null' format: date-time description: >- Date and time of the most recent outbound message sent to any contact at this company across all campaigns. Null when no contacts have been messaged. smartFieldExplanations: type: object additionalProperties: type: string description: >- Map of smart field names to their explanation (returned when smart fields are requested). createdAt: type: string format: date-time description: Date and time when the company was created updatedAt: type: string format: date-time description: Date and time when the company was last updated companyHeadcount: type: array items: type: object properties: employeeCount: type: - number - 'null' description: Number of employees in this department. threeMonthGrowth: type: - number - 'null' description: Three-month headcount growth percentage. sixMonthGrowth: type: - number - 'null' description: Six-month headcount growth percentage. oneYearGrowth: type: - number - 'null' description: One-year headcount growth percentage. department: type: string description: Department name. createdAt: type: string format: date-time description: >- Timestamp when this headcount snapshot was created. required: - employeeCount - threeMonthGrowth - sixMonthGrowth - oneYearGrowth - department - createdAt description: Employee headcount by department. required: - id - appUrl - name - domain - website - companyLinkedInUrl - industry - rangeOfEmployees - numberOfEmployees - yearfounded - description - country - city - streetAddress - phoneNumber - companyEmail - revenueRange - hiringOnLinkedIn - openJobPositions - companyCRMId - isCompanyInCRM - contactsCount - lastContactedAt - createdAt - updatedAt required: - status - message - data '400': description: Bad request - invalid company ID '404': description: Company not found security: - apiKey: [] components: securitySchemes: apiKey: type: apiKey in: header name: x-api-key ````