> ## Documentation Index > Fetch the complete documentation index at: https://docs.lead.bank/llms.txt > Use this file to discover all available pages before exploring further. # List Application Entity Relationships > List the account holders, authorized signers, and authorized users on an Application, with their relationship type. Read-only; Entities cannot change after creation. ## OpenAPI ````yaml GET /v2/applications/{id}/entity_relationships openapi: 3.0.1 info: title: Lead Bank description: Lead Bank's APIs version: v1.0 servers: - url: https://api.sandbox.lead.bank - url: https://api.lead.bank security: - bearerAuth: [] tags: - name: ACH - name: Account Number - name: OAuth - name: Events - name: Instant Payments - name: Lending - name: Simulation - name: Internal Transfer - name: Disbursement - name: Entity - name: Wire - name: Originator - name: Funding - name: Receivable Sale - name: Balances - name: Compliance - name: Application - name: User Account - name: Blockchain Payment - name: Core Account - name: Core Balance - name: Core Transaction - name: Event Subscription - name: Receivable - name: User Credit Transaction - name: Files paths: /v2/applications/{id}/entity_relationships: get: tags: - Application summary: List application entity relationships description: >- List the account holders, authorized signers, and authorized users on an Application, with their relationship type. Read-only; Entities cannot change after creation. operationId: list-application-entity-relationships-v2 parameters: - name: id in: path required: true description: Application ID, prefixed `application_`. schema: $ref: '#/components/schemas/ApplicationID' - name: limit in: query required: false description: Maximum number of results to return. Defaults to 25, maximum 100. schema: type: integer minimum: 1 maximum: 100 default: 25 - name: starting_after in: query required: false description: The `cursor` from the previous page. Returns results after it. schema: type: string responses: '200': description: A page of entity relationships. content: application/json: schema: $ref: >- #/components/schemas/ListApplicationEntityRelationshipsSuccessResponseV2 '400': description: The request could not be parsed. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: request_malformed message: The request is invalid and cannot be parsed by the server. errors: - code: url_malformed message: The request URL could not be parsed. '403': description: >- `code` is one of: `authentication_missing` (the request has no credentials), `token_invalid` (the bearer token is missing, expired, or invalid, or does not grant `application/read` or `application/read_write`), `source_ip_not_allowed` (the request came from an IP address that is not on your program's allowlist). content: application/json: schema: $ref: '#/components/schemas/Error' example: code: token_invalid message: The bearer token is missing, expired, malformed, or invalid. '404': description: >- No application exists with this ID, or it is not visible to your program. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: object_not_found message: >- No object exists at the requested ID, or it is not visible to this caller. '422': description: >- `code` is one of: `parameters_invalid` (`limit` is outside 1 to 100 (`schema_violation`), or the `starting_after` cursor cannot be decoded (`value_malformed`)), `lead_control_restricted` (your program is not enabled for Applications v2; `errors[].code` is `feature_not_enabled`). content: application/json: schema: $ref: '#/components/schemas/Error' example: code: parameters_invalid message: One or more parameters are invalid. errors: - code: schema_violation message: limit must be between 1 and 100. parameters: - limit '429': description: Rate limit exceeded. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: rate_limit_exceeded message: >- You have exceeded the rate limit for this endpoint. Retry with backoff. '500': description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: internal_server_error message: >- Something went wrong on our end. Contact Lead with the Request-Id if this persists. '503': description: >- The service or endpoint is temporarily unavailable. Retry after a delay. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: service_unavailable message: >- The service is temporarily unavailable. Retry after the indicated delay. '504': description: An upstream system did not respond in time. Retry with backoff. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: gateway_timeout message: An upstream system timed out. Retry with backoff. components: schemas: ApplicationID: type: string description: Unique identifier for the application. Prefixed with `application_`. example: application_xyz123 pattern: ^application_\w+$ ListApplicationEntityRelationshipsSuccessResponseV2: type: object description: A page of the entities on an application, with their relationship type. properties: has_more: type: boolean description: Whether more results are available after this page. cursor: type: string description: >- Pass as `starting_after` to get the next page. Present only when `has_more` is `true`. objects: type: array items: $ref: '#/components/schemas/ApplicationEntityRelationshipV2' required: - has_more - objects Error: type: object required: - code - message properties: code: $ref: '#/components/schemas/ErrorCode' message: type: string description: >- A human-readable description of the error family. Identical for every occurrence of a given `code`; carries no request-specific detail. example: One or more parameters are invalid. errors: type: array description: >- Zero or more specific errors within this family. Always present for validation errors, one entry per failing field. items: $ref: '#/components/schemas/ErrorItem' ApplicationEntityRelationshipV2: type: object description: One entity on the application and its relationship type. properties: entity_id: $ref: '#/components/schemas/EntityID' relationship_type: type: string description: How the entity relates to the application. enum: - account_holder - authorized_signer - authorized_user example: account_holder required: - entity_id - relationship_type ErrorCode: type: string description: >- A snake_case code identifying the error family — the stable, machine-readable value partners branch on, together with the HTTP status. example: parameters_invalid enum: - request_malformed - content_too_large - idempotency_key_missing - authentication_missing - token_invalid - source_ip_not_allowed - url_invalid - object_not_found - method_not_allowed - idempotency_key_in_use - idempotency_request_inconsistent - rate_limit_exceeded - internal_server_error - service_unavailable - endpoint_disabled - gateway_timeout - unclassified - parameters_invalid - related_object_invalid - related_object_not_ready - related_object_conflict - limit_exceeded - client_control_restricted - lead_control_restricted - object_state_conflict - object_modified_concurrently - operation_invalid ErrorItem: type: object required: - code - message properties: code: type: string description: A snake_case code naming the specific error or sub-category. example: required message: type: string description: >- A human-readable description of this specific error, with interpolated values where relevant. example: account_number_id is required. parameters: type: array description: >- The request fields this error implicates, in dot notation for nested fields. Present for validation errors. items: type: string example: - account_number_id EntityID: type: string description: The ID of your entity. example: entity_xyz123 pattern: ^entity_[^\s]{1,33}$ securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.