> ## Documentation Index > Fetch the complete documentation index at: https://docs.fintoc.com/llms.txt > Use this file to discover all available pages before exploring further. # Get an entity > Returns details for the entity with the specified `id` in your organization. ## OpenAPI ````yaml reference/core-api.json GET /v2/entities/{id} openapi: 3.1.0 info: title: Fintoc API version: v2026-02-01 servers: - url: https://api.fintoc.com security: [] paths: /v2/entities/{id}: get: tags: - Entities summary: Get an entity description: >- Returns details for the entity with the specified `id` in your organization. operationId: entities-get parameters: - name: id in: path required: true schema: type: string description: Unique identifier of the entity. responses: '200': description: The requested entity. content: application/json: examples: entity: value: id: ent_2daFu0zqqDtZGJaSi2TGI2Mm1nN object: entity holder_id: AAA010101AAA holder_name: Test Entity 1 is_root: true mode: test status: operational country_code: mx capabilities: account_holder: status: operational settlement_recipient: status: under_review schema: $ref: '#/components/schemas/entity' '401': description: Invalid or missing API key. content: application/json: examples: invalid_api_key: value: error: type: authentication_error code: invalid_api_key message: 'Invalid API Key: invalid-*oken' schema: $ref: '#/components/schemas/error_object' '404': description: No entity with the given ID exists in your organization. content: application/json: examples: not_found: value: error: type: invalid_request_error code: resource_not_found message: 'Entity not found: ent_2daFu0zqqDtZGJaSi2TGI2Mm1nN' schema: $ref: '#/components/schemas/error_object' security: - api_key: [] components: schemas: entity: type: object properties: id: type: string description: Unique identifier of the entity. example: ent_2daFu0zqqDtZGJaSi2TGI2Mm1nN object: const: entity description: Type of the object. Always `entity`. capabilities: type: object description: >- Statuses for the entity's capabilities. A capability is a role the entity can take in Fintoc, such as holding accounts or receiving settlements. Each capability has its own onboarding, so the statuses can differ. properties: account_holder: type: object description: Capability of the entity to hold accounts in Fintoc. properties: status: type: string enum: - draft - under_review - pending_signature - canceled - waiting_initialization - operational - rejected - paused description: >- Status of the `account_holder` capability. One of `draft`, `under_review`, `pending_signature`, `canceled`, `waiting_initialization`, `operational`, `rejected`, or `paused`. example: operational required: - status settlement_recipient: type: object description: Capability of the entity to receive settlements from Fintoc. properties: status: type: string enum: - draft - under_review - pending_signature - canceled - waiting_initialization - operational - rejected - paused description: >- Status of the `settlement_recipient` capability. One of `draft`, `under_review`, `pending_signature`, `canceled`, `waiting_initialization`, `operational`, `rejected`, or `paused`. example: waiting_initialization required: - status required: - account_holder - settlement_recipient country_code: type: - string - 'null' description: >- ISO 3166-1 alpha-2 country code of the entity, in lowercase, or `null` when not set. For example, `cl` or `mx`. example: mx holder_id: type: string description: >- Mexican tax ID (RFC) of the entity owner, without dots or hyphens. For a foreign entity, the value is the generic foreign RFC `XEXX010101000`. example: AAA010101AAA holder_name: type: string description: Legal name of the entity owner. example: Test Entity 1 is_root: type: boolean description: Whether this entity is your organization's root entity. example: true mode: type: string enum: - live - test description: >- Whether the entity belongs to `live` or `test` data. One of `live` or `test`. example: test status: type: string enum: - draft - under_review - pending_signature - canceled - waiting_initialization - operational - rejected - paused description: >- Overall status of the entity. The value is the most advanced status across the entity's capabilities. Statuses rank from least to most advanced: `canceled`, `rejected`, `waiting_initialization`, `draft`, `under_review`, `pending_signature`, `paused`, and `operational`. Use `capabilities` to check each capability on its own. example: operational required: - id - object - capabilities - country_code - holder_id - holder_name - is_root - mode - status error_object: type: object properties: error: type: object description: Details of the error that caused the request to fail. properties: code: type: string description: >- Machine-readable code identifying the specific error, for example `invalid_request`. example: invalid_request doc_url: type: string description: >- URL of a documentation page with more details about the error. Not returned by every error. example: https://docs.fintoc.com/reference/errors message: type: string description: Human-readable message describing the error. example: 'Missing required param: account_id' param: type: - string - 'null' description: >- Name of the request parameter that caused the error. Not returned by every error. example: account_id type: type: string description: >- Category of the error, for example `invalid_request_error` or `authentication_error`. Not returned by every error. example: invalid_request_error required: - code - message required: - error securitySchemes: api_key: type: apiKey name: Authorization in: header ````