From 3bff5b454330a0997f0f142b2eaff1c03806840d Mon Sep 17 00:00:00 2001 From: Docs Agent Date: Wed, 27 May 2026 15:47:48 +0000 Subject: [PATCH 1/3] Document all_experiments option for bulk exports --- src/langsmith/data-export.mdx | 27 +++++++++++++++++++++++++-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git a/src/langsmith/data-export.mdx b/src/langsmith/data-export.mdx index 0a49b4b2bb..210b61d503 100644 --- a/src/langsmith/data-export.mdx +++ b/src/langsmith/data-export.mdx @@ -59,10 +59,10 @@ Refer to [Manage bulk export destinations](/langsmith/data-export-destinations) ## 2. Create an export job -An export job targets a specific project and date range. You will need: +An export job targets a project (or all experiments in a workspace) and a date range. You will need: - The destination `id` from the [previous step](#1-create-a-destination). -- The project ID (`session_id`)—copy this from the individual project view in the [**Tracing Projects** list](https://smith.langchain.com). +- Either a project ID (`session_id`) or `"all_experiments": true`—copy the project ID from the individual project view in the [**Tracing Projects** list](https://smith.langchain.com). - A `start_time` and `end_time` in UTC ISO 8601 format. ```bash @@ -86,6 +86,29 @@ Save the `id` from the response to monitor the export's progress. You can optionally add a `filter` expression to narrow the set of runs exported. Refer to our [filter query language](/langsmith/trace-query-syntax#filter-query-language) and [examples](/langsmith/export-traces#use-filter-query-language) for syntax. Not setting the `filter` field will export all runs. +### Export all experiments + +Instead of targeting a single project with `session_id`, you can export every experiment in the workspace at once by setting `all_experiments: true`. An experiment is any tracing project that was created by running an evaluation against a dataset (its `reference_dataset_id` is set). + +`all_experiments` and `session_id` are mutually exclusive—set exactly one. + +```bash +curl --request POST \ + --url 'https://api.smith.langchain.com/api/v1/bulk-exports' \ + --header 'Content-Type: application/json' \ + --header 'X-API-Key: YOUR_API_KEY' \ + --header 'X-Tenant-Id: YOUR_WORKSPACE_ID' \ + --data '{ + "bulk_export_destination_id": "your_destination_id", + "all_experiments": true, + "start_time": "2024-01-01T00:00:00Z", + "end_time": "2024-02-01T00:00:00Z", + "format_version": "v2_beta" + }' +``` + +The set of experiment sessions is resolved at run time, so any experiments created after the export job is submitted but before the orchestrator starts processing will be included automatically. + ### Schedule recurring exports From 7979b80e62a548b1aeca2b52dd95fedbaf72175e Mon Sep 17 00:00:00 2001 From: Kathryn May Date: Thu, 28 May 2026 11:05:26 -0400 Subject: [PATCH 2/3] edits --- src/langsmith/data-export.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/langsmith/data-export.mdx b/src/langsmith/data-export.mdx index 210b61d503..3bfad5219b 100644 --- a/src/langsmith/data-export.mdx +++ b/src/langsmith/data-export.mdx @@ -88,7 +88,7 @@ You can optionally add a `filter` expression to narrow the set of runs exported. ### Export all experiments -Instead of targeting a single project with `session_id`, you can export every experiment in the workspace at once by setting `all_experiments: true`. An experiment is any tracing project that was created by running an evaluation against a dataset (its `reference_dataset_id` is set). +To export every experiment in the workspace instead of targeting a single project with `session_id`, set `all_experiments: true`. LangSmith creates an experiment whenever you run an evaluation against a dataset, any tracing project with `reference_dataset_id` set qualifies. `all_experiments` and `session_id` are mutually exclusive—set exactly one. @@ -107,7 +107,7 @@ curl --request POST \ }' ``` -The set of experiment sessions is resolved at run time, so any experiments created after the export job is submitted but before the orchestrator starts processing will be included automatically. +The orchestrator resolves the set of experiment sessions at run time, so the export picks up any experiments you create after submitting the job but before the orchestrator starts processing. ### Schedule recurring exports From bbed224c0466fd69e855de07bf606393be95f0c3 Mon Sep 17 00:00:00 2001 From: Kathryn May <44557882+katmayb@users.noreply.github.com> Date: Thu, 28 May 2026 11:06:15 -0400 Subject: [PATCH 3/3] Apply suggestion from @katmayb --- src/langsmith/data-export.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/langsmith/data-export.mdx b/src/langsmith/data-export.mdx index 3bfad5219b..7e4c9c740d 100644 --- a/src/langsmith/data-export.mdx +++ b/src/langsmith/data-export.mdx @@ -107,7 +107,7 @@ curl --request POST \ }' ``` -The orchestrator resolves the set of experiment sessions at run time, so the export picks up any experiments you create after submitting the job but before the orchestrator starts processing. +LangSmith resolves the set of experiment sessions at run time, so the export picks up any experiments you create after submitting the job but before the orchestrator starts processing. ### Schedule recurring exports