> ## Documentation Index > Fetch the complete documentation index at: https://developers.logicgate.ai/llms.txt > Use this file to discover all available pages before exploring further. # Find every context a field is used in > Given a fieldId, return a list of every context the field is used in. ## OpenAPI ````yaml GET /api/v1/fields/{fieldId}/contexts openapi: 3.1.0 info: title: Risk Cloud API description: >- The Risk Cloud API is a collection of RESTful API endpoints that empower you and your team to directly integrate, automate, and build with the Risk Cloud. Risk Cloud API endpoint payloads are JSON based, with some endpoints supporting exports in CSV and XSLX formats for flexible integration. This API documentation showcases our Risk Cloud API v1, containing a variety of endpoints with continued support for enabling integrations with the Risk Cloud. Visit the [LogicGate Risk Cloud Developer Portal](https://www.logicgate.com/developer/) to get started with building your custom integration with quick start guides, usage guides, release notes, and more. Or download the [v1 OpenAPI specification](/legacy-openapi.json). Explore our [Risk Cloud API v2](https://docs.logicgate.com/v2/index.html) endpoints and documentation as well. [Risk Cloud API v2](https://docs.logicgate.com/v2/index.html) is our collection of API-First endpoints that are tailor made for our developer users, offer concise and highly documented details, are supported by a [Postman collection](https://www.postman.com/logicgate-postman/workspace/logicgate-risk-cloud-api/collection/29257227-de8d264b-6eeb-4177-bea6-2da0a8cabffc) and [v2 OpenAPI specification](https://github.com/LogicGateTech/openapi), and contain our latest API endpoint releases. contact: name: developer-relations@logicgate.com email: developer-relations@logicgate.com version: v2026.11.0 servers: - url: https://{subdomain}.logicgate.com description: Your Risk Cloud environment. variables: subdomain: description: Your Risk Cloud environment's subdomain (e.g. `qa`). default: your-instance security: - ApiToken: [] - basic: [] tags: - name: Authentication description: >- Getting Started: How to create an [API Access Token](https://www.logicgate.com/developer/risk-cloud-api-authentication/) to begin integrating with the Risk Cloud API - name: Attachment description: Endpoints for uploading, downloading, and retrieving record attachments. - name: Field description: Endpoints for creating, updating, and querying fields. - name: Principal description: >- Endpoints for the authenticated principal to view and manage their own details. - name: Record Audit description: Endpoints for retrieving record audit history and productivity data. - name: Step description: Endpoints for retrieving steps and the steps a user can access. - name: Table Report description: Endpoints for retrieving and managing table reports. - name: User Group description: Endpoints for managing user groups and their membership. externalDocs: description: Developer Portal url: https://www.logicgate.com/developer/ paths: /api/v1/fields/{fieldId}/contexts: get: tags: - Field summary: Find every context a field is used in. description: Given a fieldId, return a list of every context the field is used in. operationId: getFieldContexts parameters: - name: fieldId in: path description: ID of the field to look up contexts for. required: true schema: type: string responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/FieldContexts' '401': description: Unauthorized '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/AppBadRequestResponse' '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/AppStatusResponse' components: schemas: FieldContexts: type: object properties: Field: type: string Steps: type: array items: type: string uniqueItems: true Sections: type: array items: type: string uniqueItems: true Sub Sections: type: array items: type: string uniqueItems: true Layouts: type: array items: type: string uniqueItems: true TableReports: type: array items: type: string uniqueItems: true TableReport Filters: type: array items: type: string uniqueItems: true VisualReports: type: array items: type: string uniqueItems: true Jobs: type: array items: type: string uniqueItems: true Messages: type: array items: type: string uniqueItems: true Job Message Recipient: type: array items: type: string uniqueItems: true Calculation Fields: type: array items: type: string uniqueItems: true Conditional Edge Paths: type: array items: type: string uniqueItems: true Form Conditions: type: object additionalProperties: type: array items: type: string uniqueItems: true AppBadRequestResponse: type: object additionalProperties: true description: >- An RFC 9457 problem detail. Extension members are written as top-level fields rather than under `properties`, and `status` is a string, to stay compatible with pre-RFC 9457 clients. Empty fields are omitted. properties: type: type: string format: uri title: type: string status: type: string example: '400' detail: type: string instance: type: string format: uri message: type: string description: Legacy alias of `detail`. property: type: string description: The request property that failed validation. value: type: string description: The rejected value, as a string. AppStatusResponse: type: object additionalProperties: true description: >- An RFC 9457 problem detail. Extension members are written as top-level fields rather than under `properties`, and `status` is a string, to stay compatible with pre-RFC 9457 clients. Empty fields are omitted. properties: type: type: string format: uri title: type: string status: type: string example: '400' detail: type: string instance: type: string format: uri message: type: string description: Legacy alias of `detail`. securitySchemes: ApiToken: type: http scheme: bearer bearerFormat: API Token basic: type: http scheme: basic ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.