> ## Documentation Index > Fetch the complete documentation index at: https://docs.lightdash.com/llms.txt > Use this file to discover all available pages before exploring further. # Invalidate explores results cache > Invalidate the cached query results of the listed explores. The next run of each query against them executes against the warehouse, and results from other explores stay cached. Queries that share a cache key are invalidated too. Query history and existing result files are kept. Requires project admin access. Only the listed explores are cleared by default. Set includeJoinedExplores to also clear every explore that reads the base table of a listed explore, for example by joining it. The response lists every explore that was cleared. Pre-aggregates are not rebuilt: refresh them as well, or queries routed to them keep returning the same data. Call this from a data pipeline once a load finishes, e.g. `curl -X POST -H "Authorization: ApiKey $LIGHTDASH_API_KEY" -H "Content-Type: application/json" -d '{"exploreNames":["orders","payments"]}' "$LIGHTDASH_URL/api/v1/projects/$PROJECT_UUID/results-cache/invalidate/explores"` ## OpenAPI ````yaml https://raw.githubusercontent.com/lightdash/lightdash/refs/heads/main/packages/backend/src/generated/swagger.json post /api/v1/projects/{projectUuid}/results-cache/invalidate/explores openapi: 3.0.0 info: title: Lightdash API version: 3.145.0 description: > Open API documentation for all public Lightdash API endpoints. # Authentication Authenticate using the Authorization header with either 'ApiKey ' or 'Bearer '. Create a Personal Access Token by following this guide: https://docs.lightdash.com/references/personal_tokens Self-hosted provisioning can use the admin token configured with LD_SETUP_SERVICE_ACCOUNT_TOKEN to create scoped service accounts through the Service Accounts API. license: name: MIT contact: name: Lightdash Support email: support@lightdash.com url: https://docs.lightdash.com/help-and-contact/contact/contact_info/ servers: - url: / security: [] tags: - name: My Account description: These routes allow users to manage their own user account. - name: Organizations description: >- Each user is a member of a single organization. These routes allow users to manage their organization. Most actions are only available to admin users. - name: Projects description: >- Projects belong to a single organization. These routes allow users to manage their projects, browse content, and execute queries. Users inside an organization might have access to a project from an organization-level role or they might be granted access to a project directly. - name: Spaces description: >- Spaces allow you to organize charts and dashboards within a project. They also allow granular access to content by allowing you to create private spaces, which are only accessible to the creator and admins. - name: Roles & Permissions description: >- These routes allow users to manage roles and permissions for their organization. externalDocs: url: https://docs.lightdash.com/references/roles - name: Service Accounts description: >- Create and manage machine credentials for your organization. Requires organization administration permission. Use predefined organization scopes, a custom organization role, or grants to selected projects. Credentials cannot grant more access than the caller holds. - name: Query description: >- These routes allow users to execute and manage queries against their data warehouse. This includes metric queries, SQL queries, and retrieving query results. paths: /api/v1/projects/{projectUuid}/results-cache/invalidate/explores: post: tags: - Projects summary: Invalidate explores results cache description: >- Invalidate the cached query results of the listed explores. The next run of each query against them executes against the warehouse, and results from other explores stay cached. Queries that share a cache key are invalidated too. Query history and existing result files are kept. Requires project admin access. Only the listed explores are cleared by default. Set includeJoinedExplores to also clear every explore that reads the base table of a listed explore, for example by joining it. The response lists every explore that was cleared. Pre-aggregates are not rebuilt: refresh them as well, or queries routed to them keep returning the same data. Call this from a data pipeline once a load finishes, e.g. `curl -X POST -H "Authorization: ApiKey $LIGHTDASH_API_KEY" -H "Content-Type: application/json" -d '{"exploreNames":["orders","payments"]}' "$LIGHTDASH_URL/api/v1/projects/$PROJECT_UUID/results-cache/invalidate/explores"` operationId: invalidateExploresResultsCache parameters: - in: path name: projectUuid required: true schema: $ref: '#/components/schemas/UUID' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/InvalidateExploresResultsCache' responses: '200': description: Invalidated content: application/json: schema: $ref: >- #/components/schemas/ApiExploresResultsCacheInvalidationResponse default: description: Error content: application/json: schema: $ref: '#/components/schemas/ApiErrorPayload' security: [] components: schemas: UUID: type: string format: uuid description: |- Stringified UUIDv4. See [RFC 4112](https://tools.ietf.org/html/rfc4122) pattern: >- [0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12} InvalidateExploresResultsCache: properties: includeJoinedExplores: type: boolean description: |- Also invalidate every explore that reads the base table of a listed explore, for example by joining it. Defaults to false. exploreNames: items: type: string type: array required: - exploreNames type: object ApiExploresResultsCacheInvalidationResponse: $ref: '#/components/schemas/ApiSuccess_ExploresResultsCacheInvalidation_' ApiErrorPayload: properties: error: properties: data: $ref: '#/components/schemas/AnyType' description: Optional data containing details of the error message: type: string description: A friendly message summarising the error name: type: string description: Unique name for the type of error statusCode: type: number format: integer description: HTTP status code required: - name - statusCode type: object status: type: string enum: - error nullable: false required: - error - status type: object description: |- The Error object is returned from the api any time there is an error. The message contains ApiSuccess_ExploresResultsCacheInvalidation_: properties: results: $ref: '#/components/schemas/ExploresResultsCacheInvalidation' status: type: string enum: - ok nullable: false required: - results - status type: object AnyType: description: |- This AnyType is an alias for any The goal is to make it easier to identify any type in the codebase without having to eslint-disable all the time These are only used on legacy `any` types, don't use it for new types. This is added on a separate file to avoid circular dependencies. ExploresResultsCacheInvalidation: allOf: - $ref: '#/components/schemas/ResultsCacheInvalidation' - properties: exploreNames: items: type: string type: array required: - exploreNames type: object ResultsCacheInvalidation: properties: invalidatedAt: type: string format: date-time projectUuid: type: string required: - invalidatedAt - projectUuid type: object ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.