diff --git a/website/docs/docs/dbt-cloud-apis/discovery-use-cases-and-examples.md b/website/docs/docs/dbt-cloud-apis/discovery-use-cases-and-examples.md
index 68e829b310a..edf51cf556c 100644
--- a/website/docs/docs/dbt-cloud-apis/discovery-use-cases-and-examples.md
+++ b/website/docs/docs/dbt-cloud-apis/discovery-use-cases-and-examples.md
@@ -212,10 +212,6 @@ query ($environmentId: BigInt!, $first: Int!) {
 
 You can query the metadata at the job level to review results for specific runs. This is helpful for historical analysis of deployment performance or optimizing particular jobs.
 
-import DiscoveryApiJobDeprecationNotice from '/snippets/_discovery_api_job_deprecation_notice.md';
-
-<DiscoveryApiJobDeprecationNotice />
-
 <details>
 <summary>Example query</summary>
 
diff --git a/website/snippets/_discovery_api_job_deprecation_notice.md b/website/snippets/_discovery_api_job_deprecation_notice.md
deleted file mode 100644
index 71e80a958b4..00000000000
--- a/website/snippets/_discovery_api_job_deprecation_notice.md
+++ /dev/null
@@ -1,7 +0,0 @@
-:::caution
-dbt Labs is making changes to the Discovery API. These changes will take effect on September 7, 2023.
-
-The data type `Int` for `id` is being deprecated and will be replaced with `BigInt`. Currently, both data types are supported.
-
-To perform job-based queries, you must do it within the `job` schema object, and move the `jobId` and `runId` arguments to `job(...)`. This is now supported so you can update your API calls accordingly. For details, refer to [Job object schema](/docs/dbt-cloud-apis/discovery-schema-job).
-:::