From cbb5c19a4b8faa65b5ad5a60a34c1b913097000d Mon Sep 17 00:00:00 2001
From: Alberto Islas <albertisfu@gmail.com>
Date: Mon, 22 Jul 2024 16:23:21 -0500
Subject: [PATCH 01/19] fix(docs): Handling of V4 API templates

---
 cl/api/templates/alert-api-docs-vlatest.html  |  30 +-
 .../templates/case-law-api-docs-vlatest.html  |  42 +-
 .../templates/citation-api-docs-vlatest.html  |  36 +-
 ....html => citation-lookup-api-vlatest.html} |  22 +-
 cl/api/templates/field-help.html              |   4 +-
 ...financial-disclosure-api-docs-vlatest.html |  36 +-
 .../templates/includes/docket-endpoint.html   |  12 +-
 cl/api/templates/judge-api-docs-vlatest.html  |  22 +-
 .../oral-argument-api-docs-vlatest.html       |  10 +-
 cl/api/templates/pacer-api-docs-vlatest.html  |  52 +-
 cl/api/templates/recap-api-docs-vlatest.html  |  26 +-
 cl/api/templates/rest-docs-v3.html            | 526 ++++++++++++++++++
 cl/api/templates/rest-docs-vlatest.html       |  42 +-
 cl/api/templates/search-api-docs-v3.html      | 238 ++++++++
 cl/api/templates/search-api-docs-vlatest.html |  12 +-
 .../visualizations-api-docs-vlatest.html      |  14 +-
 cl/api/urls.py                                |  72 +--
 cl/api/views.py                               |  28 +-
 18 files changed, 1006 insertions(+), 218 deletions(-)
 rename cl/api/templates/{citation-lookup-api.html => citation-lookup-api-vlatest.html} (95%)
 create mode 100644 cl/api/templates/rest-docs-v3.html
 create mode 100644 cl/api/templates/search-api-docs-v3.html

diff --git a/cl/api/templates/alert-api-docs-vlatest.html b/cl/api/templates/alert-api-docs-vlatest.html
index de6e2dd4e9..ab0e00557c 100644
--- a/cl/api/templates/alert-api-docs-vlatest.html
+++ b/cl/api/templates/alert-api-docs-vlatest.html
@@ -17,7 +17,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -26,7 +26,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -56,7 +56,7 @@ <h1 id="about">Legal Alert&nbsp;APIs</h1>
     <a href="{% url "alert_help" %}" class="btn btn-lg btn-primary">Learn About Alerts</a>
   </p>
 
-  <h2 id="search">Search Alerts <small>— <nobr><code>{% url "alert-list" version="v3" %}</code></nobr></small></h2>
+  <h2 id="search">Search Alerts <small>— <nobr><code>{% url "alert-list" version=version %}</code></nobr></small></h2>
   <p>Search Alerts update you when there is new information in our search engine.</p>
   <p>This system scales to support thousands or even millions of alerts, allowing organizations to stay updated about numerous topics. This is a powerful system when used with <a href="{% url "webhooks_docs" %}">webhooks</a>.
   </p>
@@ -77,7 +77,7 @@ <h2 id="search">Search Alerts <small>— <nobr><code>{% url "alert-list" version
   <p>To learn more about this API, make an HTTP <code>OPTIONS</code> request:</p>
   <pre class="pre-scrollable">curl -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "alert-list" version="v3" %}" </pre>
+  "{% get_full_host %}{% url "alert-list" version=version %}" </pre>
 
   <h3 id="example">Example Usage</h3>
   <p>Let's say we want to know about case law involving Apple Inc. On the front end, we search for "Apple Inc" (in quotes) and <a href="/?q=%22Apple%20Inc%22&type=o">get query parameters</a> like:
@@ -89,10 +89,10 @@ <h3 id="example">Example Usage</h3>
   --data 'query=q=%22Apple%20Inc%22&type=o' \
   --data 'rate=rt' \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "alert-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "alert-list" version=version %}"</pre>
   <p>The response:</p>
   <pre class="pre-scrollable">{
-  "resource_uri": "https://www.courtlistener.com/api/rest/v3/alerts/4839/",
+  "resource_uri": "https://www.courtlistener.com/api/rest/{{ version }}/alerts/4839/",
   "id": 4839,
   "date_created": "2024-05-02T15:29:32.048912-07:00",
   "date_modified": "2024-05-02T15:29:32.048929-07:00",
@@ -108,18 +108,18 @@ <h3 id="example">Example Usage</h3>
   <pre class="pre-scrollable">curl -X PATCH \
   --data 'rate=dly' \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "alert-detail" version="v3" pk="4839" %}"</pre>
+  "{% get_full_host %}{% url "alert-detail" version=version pk="4839" %}"</pre>
   <p>Search Alerts can be deleted with HTTP <code>DELETE</code> requests:</p>
   <pre class="pre-scrollable">curl -X DELETE \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "alert-detail" version="v3" pk="4839" %}"</pre>
+  "{% get_full_host %}{% url "alert-detail" version=version pk="4839" %}"</pre>
   <p>To list your alerts, send an HTTP <code>GET</code> request with no filters:</p>
   <pre class="pre-scrollable">curl -X GET \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "alert-list" version="v3" %}" </pre>
+  "{% get_full_host %}{% url "alert-list" version=version %}" </pre>
 
 
-  <h2 id="dockets">Docket Alerts <small>— <nobr><code>{% url "docket-alert-list" version="v3" %}</code></nobr></small></h2>
+  <h2 id="dockets">Docket Alerts <small>— <nobr><code>{% url "docket-alert-list" version=version %}</code></nobr></small></h2>
   <p>Docket Alerts keep you updated about cases by sending notifications by email or webhook whenever there is new information in our system. Use this API to create, modify, list, and delete Docket Alerts.
   </p>
   <p>Docket Alerts are always sent as soon as an update is available. See <a href="{% url "alert_help" %}">the help page on Docket Alerts</a> to learn more about how we get updates.
@@ -138,7 +138,7 @@ <h2 id="dockets">Docket Alerts <small>— <nobr><code>{% url "docket-alert-list"
   <p>To learn more about this API, make an HTTP <code>OPTIONS</code> request:</p>
   <pre class="pre-scrollable">curl -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}'
-  "{% get_full_host %}{% url "docket-alert-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "docket-alert-list" version=version %}"</pre>
 
   <h3 id="docket-examples">Example Usage</h3>
   <p>To create a Docket Alert, send a POST request with the <code>docket</code> ID you wish to subscribe to.
@@ -147,7 +147,7 @@ <h3 id="docket-examples">Example Usage</h3>
   <pre class="pre-scrollable">curl -X POST \
   --data 'docket=1' \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-alert-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "docket-alert-list" version=version %}"</pre>
   <p>The response:</p>
   <pre class="pre-scrollable">{
   "id": 133013,
@@ -161,17 +161,17 @@ <h3 id="docket-examples">Example Usage</h3>
   <p>To unsubscribe from a docket, you can either delete the alert with an HTTP <code>DELETE</code> request:</p>
   <pre class="pre-scrollable">curl -X DELETE \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-alert-detail" version="v3" pk="133013" %}"</pre>
+  "{% get_full_host %}{% url "docket-alert-detail" version=version pk="133013" %}"</pre>
   <p>Or, if you are using @recap.email and have auto-subscribe enabled, you can send an HTTP <code>PATCH</code> request to change it from a subscription (<code>alert_type=1</code>) to an unsubscription (<code>alert_type=0</code>):
   </p>
   <pre class="pre-scrollable">curl -X PATCH \
   --data 'alert_type=0' \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-alert-detail" version="v3" pk="133013" %}"</pre>
+  "{% get_full_host %}{% url "docket-alert-detail" version=version pk="133013" %}"</pre>
   <p>To list your Docket Alerts, send an HTTP <code>GET</code> request with no filters:</p>
   <pre class="pre-scrollable">curl -X GET \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-alert-list" version="v3" %}" </pre>
+  "{% get_full_host %}{% url "docket-alert-list" version=version %}" </pre>
 
   <h2 id="coming-soon">Coming Soon</h2>
   <p>We are currently developing a scalable alert system that will update you when keywords appear in PACER documents or cases. To join the beta test for this system, please <a href="{% url "contact" %}">get in touch</a>.
diff --git a/cl/api/templates/case-law-api-docs-vlatest.html b/cl/api/templates/case-law-api-docs-vlatest.html
index 4eedcdcc6f..2c0f7c53d5 100644
--- a/cl/api/templates/case-law-api-docs-vlatest.html
+++ b/cl/api/templates/case-law-api-docs-vlatest.html
@@ -18,7 +18,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -27,7 +27,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -101,7 +101,7 @@ <h1 id="about">Case Law&nbsp;API</h1>
 
 
   <h2 id="apis">The APIs</h2>
-  <h3 id="docket-endpoint">Dockets <small> — <code>{% url "docket-list" version="v3" %}</code></small></h3>
+  <h3 id="docket-endpoint">Dockets <small> — <code>{% url "docket-list" version=version %}</code></small></h3>
   {% include "includes/docket-endpoint.html" %}
   <p>The name of a docket can change in response to the outside world, but the names of clusters do not change. Therefore, we have <code>case_name</code> fields on both the docket and the cluster.
   </p>
@@ -110,7 +110,7 @@ <h3 id="docket-endpoint">Dockets <small> — <code>{% url "docket-list" version=
   <p>For more information on case names, see the <a href="{% url "field_api_help" %}#case-names">help article on this topic</a>.</p>
 
 
-  <h3 id="cluster-endpoint">Clusters <small> — <code>{% url "opinioncluster-list" version="v3" %}</code></small></h3>
+  <h3 id="cluster-endpoint">Clusters <small> — <code>{% url "opinioncluster-list" version=version %}</code></small></h3>
   <p>This is a major API that provides the millions of <code>Opinion Clusters</code> that are available on CourtListener.
   </p>
   <p>As with all other APIs, you can look up the field descriptions, filtering, ordering, and rendering options by making an <code>OPTIONS</code> request:
@@ -118,7 +118,7 @@ <h3 id="cluster-endpoint">Clusters <small> — <code>{% url "opinioncluster-list
   <pre class="pre-scrollable">curl -v \
   -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinioncluster-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "opinioncluster-list" version=version %}"</pre>
   <p>A few notes:</p>
   <ul>
     <li>
@@ -136,7 +136,7 @@ <h3 id="cluster-endpoint">Clusters <small> — <code>{% url "opinioncluster-list
   </ul>
 
 
-  <h3 id="opinion-endpoint">Opinions <small> — <code>{% url "opinion-list" version="v3" %}</code></small></h3>
+  <h3 id="opinion-endpoint">Opinions <small> — <code>{% url "opinion-list" version=version %}</code></small></h3>
   <p>This API contains the text and other metadata about specific decisions.
   </p>
   <p>As with all other APIs, you can look up the field descriptions, filtering, ordering, and rendering options by making an <code>OPTIONS</code> request:
@@ -144,7 +144,7 @@ <h3 id="opinion-endpoint">Opinions <small> — <code>{% url "opinion-list" versi
   <pre class="pre-scrollable">curl -v \
   -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinion-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "opinion-list" version=version %}"</pre>
   <p>A few notes:</p>
   <ul>
     <li>
@@ -195,7 +195,7 @@ <h3 id="opinion-endpoint">Opinions <small> — <code>{% url "opinion-list" versi
   </ul>
 
 
-  <h3 id="court-endpoint">Courts <small> — <code>{% url "court-list" version="v3" %}</code></small></h3>
+  <h3 id="court-endpoint">Courts <small> — <code>{% url "court-list" version=version %}</code></small></h3>
   {% include "includes/court-endpoint.html" %}
 
 
@@ -205,15 +205,15 @@ <h3 id="filtering-court">Filtering to Opinions in a Court</h3>
   </p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinion-list" version="v3" %}?cluster__docket__court=scotus"</pre>
+  "{% get_full_host %}{% url "opinion-list" version=version %}?cluster__docket__court=scotus"</pre>
   <p>That returns:</p>
   <pre class="pre-scrollable">{
   "count": 521329,
-  "next": "https://www.courtlistener.com/api/rest/v3/opinions/?cluster__docket__court=scotus&page=2",
+  "next": "https://www.courtlistener.com/api/rest/{{ version }}/opinions/?cluster__docket__court=scotus&page=2",
   "previous": null,
   "results": [
       {
-          "resource_uri": "https://www.courtlistener.com/api/rest/v3/opinions/9973155/",
+          "resource_uri": "https://www.courtlistener.com/api/rest/{{ version }}/opinions/9973155/",
           "id": 9973155,
   ...</pre>
   <p>Such an approach is fine if all you want is the opinion object, but often you'll want the docket and the cluster too.
@@ -223,25 +223,25 @@ <h3 id="filtering-court">Filtering to Opinions in a Court</h3>
   <p>For example, this gets the dockets from SCOTUS:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-list" version="v3" %}?court=scotus"</pre>
+  "{% get_full_host %}{% url "docket-list" version=version %}?court=scotus"</pre>
   <p>The first result contains a <code>clusters</code> key like:</p>
   <pre class="pre-scrollable">"clusters": [
-    "{% get_full_host %}{% url "opinioncluster-detail" version="v3" pk="9502621" %}"
+    "{% get_full_host %}{% url "opinioncluster-detail" version=version pk="9502621" %}"
 ],</pre>
   <p>So we can simply get that URL:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinioncluster-detail" version="v3" pk="9502621" %}"</pre>
+  "{% get_full_host %}{% url "opinioncluster-detail" version=version pk="9502621" %}"</pre>
   <p>That returns a cluster, which has the following keys:</p>
-  <pre class="pre-scrollable">"docket": "{% get_full_host %}{% url "docket-detail" version="v3" pk="68533094" %}",
+  <pre class="pre-scrollable">"docket": "{% get_full_host %}{% url "docket-detail" version=version pk="68533094" %}",
 "sub_opinions": [
-    "{% get_full_host %}{% url "opinion-detail" version="v3" pk="9969234" %}"
+    "{% get_full_host %}{% url "opinion-detail" version=version pk="9969234" %}"
 ],</pre>
   <p>Finally, GET the links in the <code>sub_opinions</code> field to have the complete object:
   </p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinion-detail" version="v3" pk="9969234" %}"</pre>
+  "{% get_full_host %}{% url "opinion-detail" version=version pk="9969234" %}"</pre>
 
 
   <h3 id="filtering-dn">Filtering by Docket Number</h3>
@@ -250,15 +250,15 @@ <h3 id="filtering-dn">Filtering by Docket Number</h3>
   <p>A docket by docket number:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-list" version="v3" %}?docket_number=23A994"</pre>
+  "{% get_full_host %}{% url "docket-list" version=version %}?docket_number=23A994"</pre>
   <p>A cluster by docket number:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinioncluster-list" version="v3" %}?docket__docket_number=23A994"</pre>
+  "{% get_full_host %}{% url "opinioncluster-list" version=version %}?docket__docket_number=23A994"</pre>
   <p>An opinion by docket number:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinion-list" version="v3" %}?cluster__docket__docket_number=23A994"</pre>
+  "{% get_full_host %}{% url "opinion-list" version=version %}?cluster__docket__docket_number=23A994"</pre>
   <p>Docket numbers are not unique, so you'll want to add a court filter too:
   </p>
   <ul>
@@ -281,7 +281,7 @@ <h3 id="by-url">Finding a Case by URL</h3>
   <p>This case can be found in the cluster API using that same ID:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinioncluster-detail" version="v3" pk="2812209" %}"</pre>
+  "{% get_full_host %}{% url "opinioncluster-detail" version=version pk="2812209" %}"</pre>
   <p>Opinion IDs do not reliably match cluster IDs.</p>
 
 
diff --git a/cl/api/templates/citation-api-docs-vlatest.html b/cl/api/templates/citation-api-docs-vlatest.html
index 8787217ce8..0b529578eb 100644
--- a/cl/api/templates/citation-api-docs-vlatest.html
+++ b/cl/api/templates/citation-api-docs-vlatest.html
@@ -18,7 +18,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -27,7 +27,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -49,14 +49,14 @@ <h1 id="about">Legal Citation&nbsp;API</h1>
   <p>To look up specific citations, see our <a href="{% url "citation_lookup_api" %}">citation lookup and verification API</a>.</p>
 
 
-  <h2 id="cites-endpoint">Opinions Cited/Citing API<br><small><code>{% url "opinionscited-list" version="v3" %}</code></small></h2>
+  <h2 id="cites-endpoint">Opinions Cited/Citing API<br><small><code>{% url "opinionscited-list" version=version %}</code></small></h2>
   <p>This endpoint provides an interface into the citation graph that CourtListener provides between opinions in <a href="{% url "case_law_api_help" %}">our case law database</a>.
   <p>You can look up the field descriptions, filtering, ordering, and rendering options by making an <code>OPTIONS</code> request:
   </p>
   <pre class="pre-scrollable">curl -v \
   -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinionscited-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "opinionscited-list" version=version %}"</pre>
   <p>That query will return the following filter options:</p>
   <pre class="pre-scrollable tall">{
   "id": {
@@ -79,49 +79,49 @@ <h2 id="cites-endpoint">Opinions Cited/Citing API<br><small><code>{% url "opinio
     "lookup_types": "See available filters for 'Opinions'"
   }
 }</pre>
-  <p>To understand <code>RelatedFilters</code>, see our <a href="{% url "rest_docs" version="v3" %}">filtering documentation</a>.</p>
+  <p>To understand <code>RelatedFilters</code>, see our <a href="{% url "rest_docs" version=version %}">filtering documentation</a>.</p>
   <p>These filters allow you to filter to the opinions that an opinion cites (it's "Authorities") or the opinions that cite it.
   </p>
   <p>For example, opinion <code>2812209</code> is the decision in <em>Obergefell v. Hodges</em>. To see what it cites:</p>
   <pre class="pre-scrollable tall">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinionscited-list" version="v3" %}?citing_opinion=2812209"</pre>
+  "{% get_full_host %}{% url "opinionscited-list" version=version %}?citing_opinion=2812209"</pre>
   <p>Which returns (in part):</p>
   <pre class="pre-scrollable tall">{
   "count": 75,
-  "next": "https://www.courtlistener.com/api/rest/v3/opinions-cited/?citing_opinion=2812209&page=2",
+  "next": "https://www.courtlistener.com/api/rest/{{ version }}/opinions-cited/?citing_opinion=2812209&page=2",
   "previous": null,
   "results": [
     {
-      "resource_uri": "https://www.courtlistener.com/api/rest/v3/opinions-cited/167909003/",
+      "resource_uri": "https://www.courtlistener.com/api/rest/{{ version }}/opinions-cited/167909003/",
       "id": 167909003,
-      "citing_opinion": "https://www.courtlistener.com/api/rest/v3/opinions/2812209/",
-      "cited_opinion": "https://www.courtlistener.com/api/rest/v3/opinions/96405/",
+      "citing_opinion": "https://www.courtlistener.com/api/rest/{{ version }}/opinions/2812209/",
+      "cited_opinion": "https://www.courtlistener.com/api/rest/{{ version }}/opinions/96405/",
       "depth": 1
     },
     {
-      "resource_uri": "https://www.courtlistener.com/api/rest/v3/opinions-cited/167909002/",
+      "resource_uri": "https://www.courtlistener.com/api/rest/{{ version }}/opinions-cited/167909002/",
       "id": 167909002,
-      "citing_opinion": "https://www.courtlistener.com/api/rest/v3/opinions/2812209/",
-      "cited_opinion": "https://www.courtlistener.com/api/rest/v3/opinions/2264443/",
+      "citing_opinion": "https://www.courtlistener.com/api/rest/{{ version }}/opinions/2812209/",
+      "cited_opinion": "https://www.courtlistener.com/api/rest/{{ version }}/opinions/2264443/",
       "depth": 1
     },
 …</pre>
   <p>To go the other direction, and see what cites <em>Obergefell</em>, use the <code>cited_opinion</code> parameter instead:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "opinionscited-list" version="v3" %}?cited_opinion=2812209"</pre>
+  "{% get_full_host %}{% url "opinionscited-list" version=version %}?cited_opinion=2812209"</pre>
   <p>That returns (in part):</p>
   <pre class="pre-scrollable tall">{
   "count": 403,
-  "next": "https://www.courtlistener.com/api/rest/v3/opinions-cited/?cited_opinion=2812209&page=2",
+  "next": "https://www.courtlistener.com/api/rest/{{ version }}/opinions-cited/?cited_opinion=2812209&page=2",
   "previous": null,
   "results": [
     {
-      "resource_uri": "https://www.courtlistener.com/api/rest/v3/opinions-cited/213931728/",
+      "resource_uri": "https://www.courtlistener.com/api/rest/{{ version }}/opinions-cited/213931728/",
       "id": 213931728,
-      "citing_opinion": "https://www.courtlistener.com/api/rest/v3/opinions/10008139/",
-      "cited_opinion": "https://www.courtlistener.com/api/rest/v3/opinions/2812209/",
+      "citing_opinion": "https://www.courtlistener.com/api/rest/{{ version }}/opinions/10008139/",
+      "cited_opinion": "https://www.courtlistener.com/api/rest/{{ version }}/opinions/2812209/",
       "depth": 4
     },
 …</pre>
diff --git a/cl/api/templates/citation-lookup-api.html b/cl/api/templates/citation-lookup-api-vlatest.html
similarity index 95%
rename from cl/api/templates/citation-lookup-api.html
rename to cl/api/templates/citation-lookup-api-vlatest.html
index 82d6662c75..f9c4464284 100644
--- a/cl/api/templates/citation-lookup-api.html
+++ b/cl/api/templates/citation-lookup-api-vlatest.html
@@ -17,7 +17,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -26,7 +26,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -48,7 +48,7 @@ <h3>Table of Contents</h3>
 
 <div class="col-xs-12 col-md-8 col-lg-6">
   <h1 id="about">Citation Lookup and Verification&nbsp;API</h1>
-  <h2><code>{% url "citation-lookup-list" version="v3" %}</code></h2>
+  <h2><code>{% url "citation-lookup-list" version=version %}</code></h2>
   <p class="lead v-offset-above-3">Use this API to look up citations in CourtListener's database of {{ cite_count|intcomma }} citations.</p>
   <p>This API can look up either an individual citation or can parse and look up every citation in a block of text. This can be useful as a guardrail to help prevent hallucinated citations.
   </p>
@@ -60,13 +60,13 @@ <h2><code>{% url "citation-lookup-list" version="v3" %}</code></h2>
   <h2 id="usage">Usage</h2>
   <p>The simplest way to query this API is to send it a blob of text. If the text does not have any citations, it will simply return an empty JSON object:
   </p>
-  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version="v3" %}" \
+  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version=version %}" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
   --data 'text=Put some text here'\
 []</pre>
   <p>If the text contains valid citations, it will return a list of the citations, analyzing each. This example contains a single citation that is found:
   </p>
-  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version="v3" %}" \
+  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version=version %}" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
   --data 'text=Obergefell v. Hodges (576 U.S. 644) established the right to marriage among same-sex couples'
 [
@@ -84,7 +84,7 @@ <h2 id="usage">Usage</h2>
 ]</pre>
   <p>If you have the volume, reporter, and page for a citation, you can look it up as follows:
   </p>
-  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version="v3" %}" \
+  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version=version %}" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
   --data 'volume=576' \
   --data 'reporter=U.S.' \
@@ -133,7 +133,7 @@ <h2 id="limitations">Limitations &amp; Throttles</h2>
   <h2 id="examples">API Examples</h2>
   <h3 id="basic">Basic, Valid Lookup</h3>
   <p>The following is a basic lookup using the <code>text</code> parameter and a block of text:</p>
-  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version="v3" %}" \
+  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version=version %}" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
   --data 'text=Obergefell v. Hodges (576 U.S. 644) established the right to marriage among same-sex couples'
 [
@@ -151,7 +151,7 @@ <h3 id="basic">Basic, Valid Lookup</h3>
 ]</pre>
   <h3 id="failed">Failed Lookup</h3>
   <p>This query uses the volume-reporter-page triad, but fails because the citation does not exist:</p>
-  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version="v3" %}" \
+  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version=version %}" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
   --data 'volume=1' \
   --data 'reporter=U.S.' \
@@ -178,7 +178,7 @@ <h3 id="failed">Failed Lookup</h3>
   <h3 id="throttled">Throttled Citations</h3>
   <p>If your request contains more than {{max_citation_per_request}} citations, the {{max_citation_per_request|add:1}}<sup>st</sup> and subsequent citations will be returned with 429 <code>status</code> fields:
   </p>
-  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version="v3" %}" \
+  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version=version %}" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
   --data 'text=Imagine a very long blob here, with {{max_citation_per_request|add:1}} citations.'
 [
@@ -205,7 +205,7 @@ <h3 id="throttled">Throttled Citations</h3>
   <h3 id="typoed">Typoed/Non-Canonical Reporter Abbreviation</h3>
   <p>If you query the non-canonical reporter abbreviation or if your reporter contains a known typo, we will provide the corrected citation in the <code>normalized_citations</code> key. The following example looks up a citation using "US" instead of the correct "U.S.":
   </p>
-  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version="v3" %}" \
+  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version=version %}" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
   --data 'text=576 US 644'
 [
@@ -225,7 +225,7 @@ <h3 id="typoed">Typoed/Non-Canonical Reporter Abbreviation</h3>
   <h3 id="ambiguous">Ambiguous Citation</h3>
   <p>This lookup is for an ambiguous citation abbreviated as "H." This reporter abbreviation can refer to Handy's Ohio Reports, the Hawaii Reports, or Hill’s New York Reports. Only two of those reporter series have cases at the queried volume and page number, so the API returns two possible matches for the citation:
   </p>
-  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version="v3" %}" \
+  <pre class="pre-scrollable">curl -X POST "{% get_full_host %}{% url "citation-lookup-list" version=version %}" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
   --data 'text=1 H. 150'
 [
diff --git a/cl/api/templates/field-help.html b/cl/api/templates/field-help.html
index 6d67c94cee..4e0a8156b3 100644
--- a/cl/api/templates/field-help.html
+++ b/cl/api/templates/field-help.html
@@ -17,7 +17,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -26,7 +26,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
diff --git a/cl/api/templates/financial-disclosure-api-docs-vlatest.html b/cl/api/templates/financial-disclosure-api-docs-vlatest.html
index fb4ce9c00a..8be48f59ab 100644
--- a/cl/api/templates/financial-disclosure-api-docs-vlatest.html
+++ b/cl/api/templates/financial-disclosure-api-docs-vlatest.html
@@ -19,7 +19,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -28,7 +28,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -74,34 +74,34 @@ <h1 id="about">Financial Disclosures&nbsp;API</h1>
   <h2 id="apis">Available APIs</h2>
   <p>The Ethics in Government Act details the types of information required, and prescribes the general format and procedures for the reports themselves.</p>
   <p>The APIs described below mirror the Act's language, with APIs corresponding to each required disclosure type.</p>
-  <h3 id="disclosure-api">Disclosures <small>— <code>{% url "financialdisclosure-list" version="v3" %}</code></small></h3>
+  <h3 id="disclosure-api">Disclosures <small>— <code>{% url "financialdisclosure-list" version=version %}</code></small></h3>
   <p>This API contains information about the main document itself and is the link between the other financial disclosure endpoints and the judges in our system.
   </p>
-  <h3 id="investment-api">Investments <small>— <code>{% url "investment-list" version="v3" %}</code></small></h3>
+  <h3 id="investment-api">Investments <small>— <code>{% url "investment-list" version=version %}</code></small></h3>
   <p>This API lists the source and type of investment income held by a judge, including dividends, rents, interest, capital gains, or income from qualified or excepted trusts.</p>
-  <h3 id="position-api">Positions <small>— <code>{% url "disclosureposition-list" version="v3" %}</code></small></h3>
+  <h3 id="position-api">Positions <small>— <code>{% url "disclosureposition-list" version=version %}</code></small></h3>
   <p>This API lists the positions held as an officer, director, trustee, general partner, proprietor, representative, executor, employee, or consultant of any corporation, company, firm, partnership, trust, or other business enterprise, any nonprofit organization, any labor organization, or any educational or other institution other than the United States.
   </p>
-  <h3 id="agreement-api">Agreements <small>— <code>{% url "agreement-list" version="v3" %}</code></small></h3>
+  <h3 id="agreement-api">Agreements <small>— <code>{% url "agreement-list" version=version %}</code></small></h3>
   <p>This API lists any agreements or arrangements of the filer in existence at any time during the reporting period.</p>
-  <h3 id="non-investment-api">Non-Investment Income<br><small><code>{% url "noninvestmentincome-list" version="v3" %}</code></small></h3>
+  <h3 id="non-investment-api">Non-Investment Income<br><small><code>{% url "noninvestmentincome-list" version=version %}</code></small></h3>
   <p>This API lists the source, type, and the amount or value of earned or other non-investment income aggregating $200 or more from any one source that is received during the reporting period.</p>
-  <h3 id="spouse-non-investment-income-api">Non-Investment Income (Spouse)<br><small><code>{% url "spouseincome-list" version="v3" %}</code></small></h3>
+  <h3 id="spouse-non-investment-income-api">Non-Investment Income (Spouse)<br><small><code>{% url "spouseincome-list" version=version %}</code></small></h3>
   <p>This API lists the source and type earned of non-investment income from the spouse of the filer.</p>
-  <h3 id="reimbursement-api">Reimbursements <small>— <code>{% url "reimbursement-list" version="v3" %}</code></small>
+  <h3 id="reimbursement-api">Reimbursements <small>— <code>{% url "reimbursement-list" version=version %}</code></small>
 </h3>
   <p>This API lists the source identity and description (including travel locations, dates, and nature of expenses provided) of any travel-related reimbursements aggregating more than $415 in value that are received by the filer from one source during the reporting period.
   </p>
-  <h3 id="gift-api">Gifts <small>— <code>{% url "gift-list" version="v3" %}</code></small></h3>
+  <h3 id="gift-api">Gifts <small>— <code>{% url "gift-list" version=version %}</code></small></h3>
   <p>This API lists the source, a brief description, and the value of all gifts aggregating more than $415 in value that are received by the filer during the reporting period from any one source.</p>
-  <h3 id="debt-api">Debts <small>— <code>{% url "debt-list" version="v3" %}</code></small></h3>
+  <h3 id="debt-api">Debts <small>— <code>{% url "debt-list" version=version %}</code></small></h3>
   <p>All liabilities specified by that section that are owed during the period beginning on January 1 of the preceding calendar year and ending fewer than 31 days before the date on which the report is filed.</p>
 
   <h2 id="fields">Fields</h2>
   <h3 id="understanding">Understanding the Fields</h3>
   <p>Like most of our APIs, field definitions can be obtained by sending an HTTP <code>OPTIONS</code> request to any of the APIs. For example, this request, piped through <a href="https://github.com/jqlang/jq"><code>jq</code></a>, shows you the fields of the Gifts API:
   </p>
-  <pre class="pre-scrollable tall">curl -X OPTIONS "{% get_full_host %}{% url "gift-list" version="v3" %}" \
+  <pre class="pre-scrollable tall">curl -X OPTIONS "{% get_full_host %}{% url "gift-list" version=version %}" \
     | jq '.actions.POST'
 
 {
@@ -181,15 +181,15 @@ <h3 id="redactions">Redactions</h3>
   </p>
   <p>This field can be used as a filter. For example, here are all the investments with redacted information:
   </p>
-  <pre class="pre-scrollable tall">curl "{% get_full_host %}{% url "investment-list" version="v3" %}?redacted=True" \
+  <pre class="pre-scrollable tall">curl "{% get_full_host %}{% url "investment-list" version=version %}?redacted=True" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}'
 {
   "count": 27404,
-  "next": "https://www.courtlistener.com/api/rest/v3/investments/?page=2&redacted=True",
+  "next": "https://www.courtlistener.com/api/rest/{{ version }}/investments/?page=2&redacted=True",
   "previous": null,
   "results": [
     {
-      "resource_uri": "https://www.courtlistener.com/api/rest/v3/investments/5385644/",
+      "resource_uri": "https://www.courtlistener.com/api/rest/{{ version }}/investments/5385644/",
       "id": 5385644,
       "date_created": "2023-04-17T11:03:22.404170-07:00",
       "date_modified": "2023-04-17T11:03:22.404185-07:00",
@@ -207,7 +207,7 @@ <h3 id="redactions">Redactions</h3>
       "transaction_gain_code": "",
       "transaction_partner": "",
       "has_inferred_values": false,
-      "financial_disclosure": "https://www.courtlistener.com/api/rest/v3/financial-disclosures/34187/"
+      "financial_disclosure": "https://www.courtlistener.com/api/rest/{{ version }}/financial-disclosures/34187/"
     },
 ...</pre>
 
@@ -248,10 +248,10 @@ <h3 id="inferred-values">Inferred Values</h3>
   <h2 id="examples">API Examples</h2>
   <p>You can query for investments by stock name, transaction dates and even gross values. For example, the following query is for financial disclosures with individual investments valued above $50,000,000.00. Note that this uses a value code as explained in the general notes above:
   </p>
-  <pre class="pre-scrollable">curl "{% get_full_host %}{% url "investment-list" version="v3" %}?gross_value_code=P4&fields=investments" \
+  <pre class="pre-scrollable">curl "{% get_full_host %}{% url "investment-list" version=version %}?gross_value_code=P4&fields=investments" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}'</pre>
   <p>Additionally, you could pinpoint gifts of individual judges when combining the gift database with our judicial database. The following query returns all reported gifts by the late <a href="{% url "view_person" 1213 "ruth-bader-ginsberg" %}">Ruth Bader Ginsburg</a> (her ID is 1213):</p>
-  <pre class="pre-scrollable">curl "{% get_full_host %}{% url "financialdisclosure-list" version="v3" %}?person=1213&fields=gifts" \
+  <pre class="pre-scrollable">curl "{% get_full_host %}{% url "financialdisclosure-list" version=version %}?person=1213&fields=gifts" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}'</pre>
   <p>In 2024, we presented these APIs at the NICAR conference and created <a href="https://github.com/freelawproject/talks/tree/main/talks/2024/march/NICAR/cracking_the_courts_panel/examples">many more examples</a> you can explore.</p>
 
diff --git a/cl/api/templates/includes/docket-endpoint.html b/cl/api/templates/includes/docket-endpoint.html
index 1135bf3950..4d44499193 100644
--- a/cl/api/templates/includes/docket-endpoint.html
+++ b/cl/api/templates/includes/docket-endpoint.html
@@ -8,23 +8,23 @@
 <pre class="pre-scrollable">curl -v \
   -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "docket-list" version=version %}"</pre>
 <p>To look up a particular docket, use its ID:</p>
 <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-detail" version="v3" pk="4214664" %}"</pre>
+  "{% get_full_host %}{% url "docket-detail" version=version pk="4214664" %}"</pre>
 <p>The response you get will not list the docket entries, parties, or attorneys for the docket (doing so doesn't scale), but will have many other metadata fields:
 </p>
 <pre class="pre-scrollable tall">{
-  "resource_uri": "https://www.courtlistener.com/api/rest/v3/dockets/4214664/",
+  "resource_uri": "https://www.courtlistener.com/api/rest/{{ version }}/dockets/4214664/",
   "id": 4214664,
-  "court": "https://www.courtlistener.com/api/rest/v3/courts/dcd/",
+  "court": "https://www.courtlistener.com/api/rest/{{ version }}/courts/dcd/",
   "court_id": "dcd",
   "original_court_info": null,
   "idb_data": null,
   "clusters": [],
   "audio_files": [],
-  "assigned_to": "https://www.courtlistener.com/api/rest/v3/people/1124/",
+  "assigned_to": "https://www.courtlistener.com/api/rest/{{ version }}/people/1124/",
   "referred_to": null,
   "absolute_url": "/docket/4214664/national-veterans-legal-services-program-v-united-states/",
   "date_created": "2016-08-20T07:25:37.448945-07:00",
@@ -66,7 +66,7 @@
   "blocked": false,
   "appeal_from": null,
   "tags": [
-    "https://www.courtlistener.com/api/rest/v3/tag/1316/"
+    "https://www.courtlistener.com/api/rest/{{ version }}/tag/1316/"
   ],
   "panel": []
 }</pre>
diff --git a/cl/api/templates/judge-api-docs-vlatest.html b/cl/api/templates/judge-api-docs-vlatest.html
index e771b372e8..3e5c1ff90b 100644
--- a/cl/api/templates/judge-api-docs-vlatest.html
+++ b/cl/api/templates/judge-api-docs-vlatest.html
@@ -19,7 +19,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -28,7 +28,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -85,7 +85,7 @@ <h1 id="about">Judge and Justice&nbsp;API</h1>
 
 
   <h2 id="apis">The APIs</h2>
-  <h3 id="people-endpoint">People (Judges and Appointers) <br><small><nobr><code>{% url "person-list" version="v3" %}</code></nobr></small></h3>
+  <h3 id="people-endpoint">People (Judges and Appointers) <br><small><nobr><code>{% url "person-list" version=version %}</code></nobr></small></h3>
   <p>This API contains the central "person" object. As explained above, people can be judges, appointers, or both.
   </p>
   <p>This object holds the core metadata about the person, including their biographical data, positions held, educational history, ABA ratings, and political affiliations.
@@ -122,7 +122,7 @@ <h3 id="people-endpoint">People (Judges and Appointers) <br><small><nobr><code>{
 
 
   <h3 id="positions-endpoint">Positions<br>
-    <small><code>{% url "position-list" version="v3" %}</code></small></h3>
+    <small><code>{% url "position-list" version=version %}</code></small></h3>
   <p>Use this API to learn the positions held by a person, including their time as president, in private practice, as a judge, or in any number of other roles in society or the judiciary.
   </p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP <code>OPTIONS</code> request.
@@ -130,11 +130,11 @@ <h3 id="positions-endpoint">Positions<br>
   <p>To filter to positions for a particular person:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "position-list" version="v3" %}?person=20"</pre>
+  "{% get_full_host %}{% url "position-list" version=version %}?person=20"</pre>
 
 
   <h3 id="affiliations-endpoint">Political Affiliations<br>
-    <small><nobr><code>{% url "politicalaffiliation-list" version="v3" %}</code></nobr></small></h3>
+    <small><nobr><code>{% url "politicalaffiliation-list" version=version %}</code></nobr></small></h3>
   <p>Use this API to learn the political affiliations of a person. Political affiliations are gathered from a number of sources such as ballots or appointments, and have start and end dates.
   </p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP <code>OPTIONS</code> request.
@@ -142,7 +142,7 @@ <h3 id="affiliations-endpoint">Political Affiliations<br>
 
 
   <h3 id="education-history">Educations and Schools<br>
-    <small><nobr><code>{% url "education-list" version="v3" %}</code></nobr></small></h3>
+    <small><nobr><code>{% url "education-list" version=version %}</code></nobr></small></h3>
   <p>Use this API to learn about the educational history of a person, including which schools they went to, when, and what degrees they received. Each education object can include a school object based on data from the Department of Education.
   </p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP <code>OPTIONS</code> request.
@@ -151,10 +151,10 @@ <h3 id="education-history">Educations and Schools<br>
   <p>To filter for judges educated at a particular school:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "person-list" version="v3" %}?educations__school__name__contains=Rochester"</pre>
+  "{% get_full_host %}{% url "person-list" version=version %}?educations__school__name__contains=Rochester"</pre>
 
   <h3 id="aba-ratings">ABA Ratings <br>
-    <small><code>{% url "abarating-list" version="v3" %}</code></small></h3>
+    <small><code>{% url "abarating-list" version=version %}</code></small></h3>
   <p>These are the American Bar Association ratings that are given to many judges, particularly those that are nominated to federal positions.
   </p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP <code>OPTIONS</code> request.
@@ -162,7 +162,7 @@ <h3 id="aba-ratings">ABA Ratings <br>
 
 
   <h3 id="retention-events">Retention Events<br>
-    <small><nobr><code>{% url "retentionevent-list" version="v3" %}</code></nobr></small></h3>
+    <small><nobr><code>{% url "retentionevent-list" version=version %}</code></nobr></small></h3>
   <p>These are the events that keep a judge in a position, such as a retention vote, or reappointment.
   </p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP <code>OPTIONS</code> request.
@@ -170,7 +170,7 @@ <h3 id="retention-events">Retention Events<br>
 
 
   <h3 id="sources-endpoint">Sources<br>
-    <small><code>{% url "source-list" version="v3" %}</code></small></h3>
+    <small><code>{% url "source-list" version=version %}</code></small></h3>
   <p>This API keeps a list of sources that explain how we built this database.
   </p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP <code>OPTIONS</code> request.
diff --git a/cl/api/templates/oral-argument-api-docs-vlatest.html b/cl/api/templates/oral-argument-api-docs-vlatest.html
index 829b934193..8b0f0fea44 100644
--- a/cl/api/templates/oral-argument-api-docs-vlatest.html
+++ b/cl/api/templates/oral-argument-api-docs-vlatest.html
@@ -19,7 +19,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -28,7 +28,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -50,7 +50,7 @@ <h1 id="about">Oral Argument Recoding&nbsp;APIs</h1>
 
 
   <h2 id="apis">The APIs</h2>
-  <h3 id="audio-endpoint">Oral Argument Recordings <small> — <nobr><code>{% url "audio-list" version="v3" %}</code></nobr></small></h3>
+  <h3 id="audio-endpoint">Oral Argument Recordings <small> — <nobr><code>{% url "audio-list" version=version %}</code></nobr></small></h3>
   <p>Use this API to gather data about oral argument recordings. This API is linked to the docket API (below), which contains data about each case. It is also linked to the <a href="{% url "judge_api_help" %}">judge API</a>, which has information about the judges in the case.
   </p>
   <p>The audio files we gather from court websites come in many formats. After we gather the files, we convert them into optimized MP3s that have a 22050Hz sample rate and 48k bitrate. After converting the files, we set the ID3 tags to better values that we scraped. Finally, we set the cover art for the MP3 to the seal of the court, and set the publisher album art to our logo.
@@ -64,10 +64,10 @@ <h3 id="audio-endpoint">Oral Argument Recordings <small> — <nobr><code>{% url
   <pre class="pre-scrollable">curl -v \
   -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "audio-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "audio-list" version=version %}"</pre>
 
 
-  <h3 id="docket-endpoint">Dockets <small> — <code>{% url "docket-list" version="v3" %}</code></small></h3>
+  <h3 id="docket-endpoint">Dockets <small> — <code>{% url "docket-list" version=version %}</code></small></h3>
   {% include "includes/docket-endpoint.html" %}
 
   {% include "includes/donate_footer_plea.html" %}
diff --git a/cl/api/templates/pacer-api-docs-vlatest.html b/cl/api/templates/pacer-api-docs-vlatest.html
index 5a28526e03..a8b26c2ed2 100644
--- a/cl/api/templates/pacer-api-docs-vlatest.html
+++ b/cl/api/templates/pacer-api-docs-vlatest.html
@@ -18,7 +18,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -27,7 +27,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -69,18 +69,18 @@ <h2 id="apis">Dockets, Courts, Docket Entries, and&nbsp;Documents</h2>
   </p>
 
 
-  <h3 id="docket-endpoint">Dockets <small> — <code>{% url "docket-list" version="v3" %}</code></small></h3>
+  <h3 id="docket-endpoint">Dockets <small> — <code>{% url "docket-list" version=version %}</code></small></h3>
   {% include "includes/docket-endpoint.html" %}
   <p>Ideally, docket entries, parties, and attorneys would be nested within the docket object you request, but this is not possible because some dockets have a vast number of these objects. Listing so many values in a single response from the server is impractical. To access docket entries, parties, or attorneys for a specific docket, use the docket entry, party, or attorney endpoints and filter by docket ID.
   </p>
   <p>The court fields are references to our Court API, described below.</p>
 
 
-  <h3 id="court-endpoint">Courts <small> — <code>{% url "court-list" version="v3" %}</code></small></h3>
+  <h3 id="court-endpoint">Courts <small> — <code>{% url "court-list" version=version %}</code></small></h3>
   {% include "includes/court-endpoint.html" %}
 
 
-  <h3 id="docket-entry-endpoint">Docket Entries <small> — <code>{% url "docketentry-list" version="v3" %}</code></small></h3>
+  <h3 id="docket-entry-endpoint">Docket Entries <small> — <code>{% url "docketentry-list" version=version %}</code></small></h3>
   <p><code>Docket Entry</code> objects represent the rows on a PACER docket, and contain one or more nested documents. This follows the design on PACER, in which a single row on a docket represents a document with its associated attachments.
   </p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP <code>OPTIONS</code> request.
@@ -89,7 +89,7 @@ <h3 id="docket-entry-endpoint">Docket Entries <small> — <code>{% url "docketen
   </p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docketentry-list" version="v3" %}?docket=4214664"</pre>
+  "{% get_full_host %}{% url "docketentry-list" version=version %}?docket=4214664"</pre>
   <p>Such a request will return up to 20 docket entries per page. Each docket entry returned can contain a number of nested documents in the <code>recap_document</code> key, including their full extracted text (see details in the next section below). As a result, this response can be quite large.
   </p>
   <p>A few field-level notes:</p>
@@ -131,7 +131,7 @@ <h3 id="docket-entry-endpoint">Docket Entries <small> — <code>{% url "docketen
     </p>
   {% endif %}
 
-  <h3 id="recap-document-endpoint">Documents <small> — <code>{% url "recapdocument-list" version="v3" %}</code></small></h3>
+  <h3 id="recap-document-endpoint">Documents <small> — <code>{% url "recapdocument-list" version=version %}</code></small></h3>
   <p>Each docket entry contains several documents, which we call <code>RECAP Document</code> objects.
   </p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP <code>OPTIONS</code> request.
@@ -174,7 +174,7 @@ <h3 id="recap-document-endpoint">Documents <small> — <code>{% url "recapdocume
 
 
 
-  <h2 id="party-endpoint">Parties <small> — <code>{% url "party-list" version="v3" %}</code></small></h2>
+  <h2 id="party-endpoint">Parties <small> — <code>{% url "party-list" version=version %}</code></small></h2>
   <p>The <code>Party</code> endpoint provides details about parties that have been involved in federal cases in PACER, and contains nested attorney information.
   </p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP <code>OPTIONS</code> request.
@@ -186,37 +186,37 @@ <h2 id="party-endpoint">Parties <small> — <code>{% url "party-list" version="v
   <p>For example, this query returns the parties for docket number <code>123</code>:</p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "party-list" version="v3" %}?docket=123"</pre>
+  "{% get_full_host %}{% url "party-list" version=version %}?docket=123"</pre>
   <p>It returns something like:</p>
   <pre class="pre-scrollable tall">{
 ① "count": 35,
-  "next": "https://www.courtlistener.com/api/rest/v3/parties/?docket=123&page=2",
+  "next": "https://www.courtlistener.com/api/rest/{{ version }}/parties/?docket=123&page=2",
   "previous": null,
   "results": [
     {
-      "resource_uri": "https://www.courtlistener.com/api/rest/v3/parties/42/",
+      "resource_uri": "https://www.courtlistener.com/api/rest/{{ version }}/parties/42/",
       "id": 42,
 ②    "attorneys": [
         {
-          "attorney": "https://www.courtlistener.com/api/rest/v3/attorneys/1/",
+          "attorney": "https://www.courtlistener.com/api/rest/{{ version }}/attorneys/1/",
           "attorney_id": 1,
           "date_action": null,
-          "docket": "https://www.courtlistener.com/api/rest/v3/dockets/123/",
+          "docket": "https://www.courtlistener.com/api/rest/{{ version }}/dockets/123/",
           "docket_id": 123,
           "role": 10
         },
         {
-          "attorney": "https://www.courtlistener.com/api/rest/v3/attorneys/2/",
+          "attorney": "https://www.courtlistener.com/api/rest/{{ version }}/attorneys/2/",
           "attorney_id": 2,
           "date_action": null,
-          "docket": "https://www.courtlistener.com/api/rest/v3/dockets/456/",
+          "docket": "https://www.courtlistener.com/api/rest/{{ version }}/dockets/456/",
           "docket_id": 456,
           "role": 2
         }
       ],
 ③    "party_types": [
         {
-          "docket": "https://www.courtlistener.com/api/rest/v3/dockets/123/",
+          "docket": "https://www.courtlistener.com/api/rest/{{ version }}/dockets/123/",
           "docket_id": 123,
           "name": "Plaintiff",
           "date_terminated": null,
@@ -257,28 +257,28 @@ <h2 id="party-endpoint">Parties <small> — <code>{% url "party-list" version="v
   {% endif %}
 
 
-  <h2 id="attorney-endpoint">Attorneys <small> — <code>{% url "attorney-list" version="v3" %}</code></small></h2>
+  <h2 id="attorney-endpoint">Attorneys <small> — <code>{% url "attorney-list" version=version %}</code></small></h2>
   <p>Use this API to look up an attorney in our system.</p>
   <p>To look up field descriptions or options for filtering, ordering, or rendering, complete an HTTP OPTIONS request.</p>
   <p>Like docket entries and parties, attorneys can be filtered to a particular docket. For example:
   </p>
   <pre class="pre-scrollable">curl -v \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "attorney-list" version="v3" %}?docket=4214664"</pre>
+  "{% get_full_host %}{% url "attorney-list" version=version %}?docket=4214664"</pre>
   <p>Returns:</p>
   <pre class="pre-scrollable tall">{
     "count": 108,
-    "next": "https://www.courtlistener.com/api/rest/v3/attorneys/?docket=4214664&page=2",
+    "next": "https://www.courtlistener.com/api/rest/{{ version }}/attorneys/?docket=4214664&page=2",
     "previous": null,
     "results": [
         {
-            "resource_uri": "https://www.courtlistener.com/api/rest/v3/attorneys/9247906/",
+            "resource_uri": "https://www.courtlistener.com/api/rest/{{ version }}/attorneys/9247906/",
             "id": 9247906,
             "parties_represented": [
                 {
                     "role": 10,
-                    "docket": "https://www.courtlistener.com/api/rest/v3/dockets/4214664/",
-                    "party": "https://www.courtlistener.com/api/rest/v3/parties/13730908/",
+                    "docket": "https://www.courtlistener.com/api/rest/{{ version }}/dockets/4214664/",
+                    "party": "https://www.courtlistener.com/api/rest/{{ version }}/parties/13730908/",
                     "date_action": null
                 }
             ],
@@ -299,7 +299,7 @@ <h2 id="attorney-endpoint">Attorneys <small> — <code>{% url "attorney-list" ve
   {% endif %}
 
 
-  <h2 id="og-court-info-endpoint">Originating Court <small> — <code><nobr>{% url 'originatingcourtinformation-list' version="v3" %}</nobr></code></small></h2>
+  <h2 id="og-court-info-endpoint">Originating Court <small> — <code><nobr>{% url 'originatingcourtinformation-list' version=version %}</nobr></code></small></h2>
   <p><code>Originating Court Information</code> represents the information gathered at an appellate court about a case when it was in a lower court or administrative body.
   </p>
   <p>The information in this table is joined via a one-to-one relationship to the <code>Docket</code> object. Generally, this table is only completed for appellate cases that we acquire from PACER.
@@ -308,7 +308,7 @@ <h2 id="og-court-info-endpoint">Originating Court <small> — <code><nobr>{% url
   </p>
 
 
-  <h2 id="idb-data-endpoint">Integrated Database <small> — <code><nobr>{% url 'fjcintegrateddatabase-list' version='v3' %}</nobr></code></small></h2>
+  <h2 id="idb-data-endpoint">Integrated Database <small> — <code><nobr>{% url 'fjcintegrateddatabase-list' version=version %}</nobr></code></small></h2>
   <p><code>FJC Integrated Database</code> objects represent the information available in the <a href="https://www.fjc.gov/research/idb">Federal Judicial Center's Integrated Database</a>, a regularly updated source of metadata about federal court cases. You can learn more about the IDB from the following sources:
   </p>
   <ul>
@@ -322,14 +322,14 @@ <h2 id="idb-data-endpoint">Integrated Database <small> — <code><nobr>{% url 'f
   </p>
 
 
-  <h2 id="recap-query">Fast Document Lookup <small> — <code>{% url "fast-recapdocument-list" version="v3" %}</code></small></h2>
+  <h2 id="recap-query">Fast Document Lookup <small> — <code>{% url "fast-recapdocument-list" version=version %}</code></small></h2>
   <p>This API is used to check if documents with known IDs are available in our system.
   </p>
   <p>To use it, provide a court ID and a comma-separated list of <code>pacer_doc_id</code>'s:
   </p>
   <pre class="pre-scrollable">curl \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  '{% get_full_host %}{% url "fast-recapdocument-list" version="v3" %}?docket_entry__docket__court=dcd&pacer_doc_id__in=04505578698,04505578717' \
+  '{% get_full_host %}{% url "fast-recapdocument-list" version=version %}?docket_entry__docket__court=dcd&pacer_doc_id__in=04505578698,04505578717' \
   </pre>
   <p>This will return one entry for each document found, up to a maximum of 300 items:</p>
   <pre class="pre-scrollable tall">{
diff --git a/cl/api/templates/recap-api-docs-vlatest.html b/cl/api/templates/recap-api-docs-vlatest.html
index bbc495e604..7087769324 100644
--- a/cl/api/templates/recap-api-docs-vlatest.html
+++ b/cl/api/templates/recap-api-docs-vlatest.html
@@ -18,7 +18,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -27,7 +27,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -63,16 +63,16 @@ <h1 id="about">RECAP APIs for&nbsp;PACER</h1>
   <p>The endpoints for RECAP are:</p>
   <ul>
     <li>
-      <p><code>{% url "pacerfetchqueue-list" version="v3" %}</code> &mdash; Use this API to scrape PACER data, including dockets, PDFs, and more.
+      <p><code>{% url "pacerfetchqueue-list" version=version %}</code> &mdash; Use this API to scrape PACER data, including dockets, PDFs, and more.
       </p>
     </li>
     <li>
-      <p><code>{% url "processingqueue-list" version="v3" %}</code> &mdash; Use this API to upload PACER data to CourtListener and to check on the progress of an upload.
+      <p><code>{% url "processingqueue-list" version=version %}</code> &mdash; Use this API to upload PACER data to CourtListener and to check on the progress of an upload.
       </p>
     </li>
   </ul>
 
-  <h2 id="pacer-fetch">PACER Fetch <small> — <code>{% url "pacerfetchqueue-list" version="v3" %}</code></small></h2>
+  <h2 id="pacer-fetch">PACER Fetch <small> — <code>{% url "pacerfetchqueue-list" version=version %}</code></small></h2>
   <p>Use this API to buy PACER content and add it to CourtListener so that it is available via our website, APIs, <a href="{% url "webhooks_docs" %}">webhooks</a>, and <a href="{% url "replication_docs" %}">replicated database</a>. This is <a href="https://free.law/2019/11/05/pacer-fetch-api">a free API</a>, but it uses your PACER credentials to purchase and download PACER content. You'll still have to pay your PACER bill when it comes.
   </p>
   <p>Because downloading content from PACER takes time, this API is asynchronous. After you send an HTTP <code>POST</code>, it immediately responds with an ID for the request and places the request in a queue to be downloaded by our scrapers. Most requests are completed within seconds.
@@ -158,7 +158,7 @@ <h4 id="pdf"> Purchasing PDFs</h4>
   --data 'pacer_password=yyy' \
   --data 'recap_document=112' \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "pacerfetchqueue-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "pacerfetchqueue-list" version=version %}"</pre>
   <p>If you have a client code, you can provide it to the API with the <code>client_code</code> parameter.</p>
   <p>If we do not have the <code>pacer_doc_id</code> for a particular <code>recap_document</code>, we will not be able to download it. If that's the case, you'll get an error message asking you to download the docket, which will get us the <code>pacer_doc_id</code> we need. Once that is completed you can retry your PDF purchase.
   </p>
@@ -195,7 +195,7 @@ <h4 id="dockets">Purchasing Dockets</h4>
 --data 'docket_number=5:16-cv-00432' \
 --data 'court=okwd' \
 --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-"{% get_full_host %}{% url "pacerfetchqueue-list" version="v3" %}"</pre>
+"{% get_full_host %}{% url "pacerfetchqueue-list" version=version %}"</pre>
   <p>This is the same, but includes parties and counsel:</p>
   <pre class="scrollable">curl -X POST \
 --data 'request_type=1' \
@@ -205,7 +205,7 @@ <h4 id="dockets">Purchasing Dockets</h4>
 --data 'court=okwd' \
 --data 'show_parties_and_counsel=true' \
 --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-"{% get_full_host %}{% url "pacerfetchqueue-list" version="v3" %}"</pre>
+"{% get_full_host %}{% url "pacerfetchqueue-list" version=version %}"</pre>
   <p>Finally, this request updates an existing docket in CourtListener by its ID, but only gets the parties and counsel. Docket entries are excluded by requesting only ones from before 1980:
   </p>
   <pre class="scrollable">curl -X POST \
@@ -216,14 +216,14 @@ <h4 id="dockets">Purchasing Dockets</h4>
 --data 'show_parties_and_counsel=true' \
 --data 'de_date_end=1980-01-01' \
 --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-"{% get_full_host %}{% url "pacerfetchqueue-list" version="v3" %}"</pre>
+"{% get_full_host %}{% url "pacerfetchqueue-list" version=version %}"</pre>
   <p>Sometimes, we get a PDF before we get a docket, making it impossible to know what case the PDF is associated with. We call these "orphan documents" because they do not have valid parent objects in our system.
   </p>
   <p>Later, when we receive new or updated docket information, we have an opportunity to fix this problem by checking our system for orphan documents. When this happens, the orphans will automatically be associated with the new docket information, and the case will have PDFs linked to it.
   </p>
 
 
-  <h2 id="recap-upload">RECAP Upload API <small>— <code>{% url "processingqueue-list" version="v3" %}</code></small></h2>
+  <h2 id="recap-upload">RECAP Upload API <small>— <code>{% url "processingqueue-list" version=version %}</code></small></h2>
   <p>This API is used by the RECAP extension and a handful of special partners to upload PACER content to the RECAP Archive. This API is not available to the public. If you have a collection of PACER data you wish to donate to the RECAP Archive so it is permanently available to the public, please <a href="{% url "contact" %}">get in touch</a>.
   </p>
   <p>We describe the process for completing these uploads below, and you can see examples of them in <a href="https://github.com/freelawproject/courtlistener/blob/main/cl/recap/tests.py">CourtListener's automated test suite</a>. Uploads to these endpoints should be done using HTTP <code>POST</code> requests and multipart form data.
@@ -333,7 +333,7 @@ <h3 id="example">A Complete Example</h3>
   --form court=dcd \
   --form pacer_case_id=&lt;some-value&gt; \
   --form debug=true \
-  '{% get_full_host %}{% url "processingqueue-list" version="v3" %}'
+  '{% get_full_host %}{% url "processingqueue-list" version=version %}'
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}'</pre>
   <p>In response, you would receive an object like this:</p>
   <pre class="pre-scrollable tall">{
@@ -356,13 +356,13 @@ <h3 id="example">A Complete Example</h3>
 }</pre>
   <p>Then, to check the status, you can poll it with:</p>
   <pre class="pre-scrollable">curl \
-  '{% get_full_host %}{% url "processingqueue-detail" version="v3" pk="13684105" %}'
+  '{% get_full_host %}{% url "processingqueue-detail" version=version pk="13684105" %}'
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}'</pre>
   <p>Which will soon return:</p>
   <pre class="pre-scrollable tall">{
     "id": 13684105,
     "court": "dcd",
-    "docket": "https://www.courtlistener.com/api/rest/v3/dockets/8903924/",
+    "docket": "https://www.courtlistener.com/api/rest/{{ version }}/dockets/8903924/",
     "docket_entry": null,
     "recap_document": null,
     "date_created": "2024-05-18T08:01:14.457637-07:00",
diff --git a/cl/api/templates/rest-docs-v3.html b/cl/api/templates/rest-docs-v3.html
new file mode 100644
index 0000000000..fdf13b7d40
--- /dev/null
+++ b/cl/api/templates/rest-docs-v3.html
@@ -0,0 +1,526 @@
+{% extends "base.html" %}
+{% load static %}
+{% load extras %}
+
+{% block title %}REST API, v3.15 &ndash; CourtListener.com{% endblock %}
+{% block description %}REST API for federal and state case law, PACER data, the searchable RECAP Archive, oral argument recordings and more. Provided by Free Law Project, a 501(c)(3) non-profit. Please donate to support this service.{% endblock %}
+{% block og_description %}REST API for federal and state case law, PACER data, the searchable RECAP Archive, oral argument recordings and more. Provided by Free Law Project, a 501(c)(3) non-profit. Please donate to support this service.{% endblock %}
+
+{% block sidebar %}{% endblock %}
+
+{% block footer-scripts %}
+  {% include "includes/anchors.html" %}
+{% endblock %}
+
+{% block content %}
+
+  <div class="col-xs-12 hidden-md hidden-lg">
+    <h4 class="v-offset-below-2">
+      <i class="fa fa-arrow-circle-o-left gray"></i>
+      <a href="{% url "help_home" %}">Back to Help</a>
+    </h4>
+  </div>
+
+  <div id="toc-container" class="hidden-xs hidden-sm col-md-3">
+    {% include "includes/toc_sidebar.html" %}
+  </div>
+  <div class="col-xs-12 col-md-8 col-lg-6">
+    <h1 id="about">REST API &ndash; v3.15</h1>
+
+    <p class="lead">APIs for developers and researchers that need granular legal data.
+    </p>
+    <p>After more than a decade of development, these APIs are powerful. Our <a href="{% url "case_law_api_help" %}">case law API</a> was the first. Our <a href="{% url "pacer_api_help" %}">PACER</a> and <a href="{% url "oral_argument_api_help" %}">oral argument</a> APIs are the biggest. Our <a href="{% url "webhooks_getting_started" %}">webhooks</a> push data to you. Our <a href="{% url "citation_lookup_api" %}">citation lookup tool</a> can fight hallucinations in AI tools.
+    </p>
+    <p>Let's get started. To see and browse all the API URLs, click the button below:
+    </p>
+    <p><a href="{% url "api-root" version="v3" %}"
+          target="_blank"
+          class="btn btn-lg btn-primary">Show the APIs</a>
+    </p>
+    <p>We could have also pulled up that same information using curl, with a command like:</p>
+    <pre class="scrollable">curl "{% get_full_host %}{% url "api-root" version="v3" %}"</pre>
+    <p>Note that when you press the button in your browser, you get an HTML result, but when you run <code>curl</code> you get a JSON object. This is <a href="#formats">discussed in more depth below</a>.
+    </p>
+    <p class="alert alert-warning"><i class="fa fa-warning"></i> <strong>Listen Up!</strong> Something else that's curious just happened. You didn't authenticate to the API. To encourage experimentation, many of our APIs are open by default. The biggest gotcha people have is that they forget to enable authentication before deploying their code. Don't make this mistake! Remember to add <a href="#authentication">authentication</a>.
+    </p>
+    <p>The APIs listed in this response can be used to make queries against our database or search engine.
+    </p>
+    <p>To learn more about an API, you can send an <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/OPTIONS">HTTP OPTIONS</a> request to it, like so:
+    </p>
+    <pre class="scrollable">curl -X OPTIONS "{% get_full_host %}{% url "api-root" version="v3" %}"</pre>
+    <p>An <code>OPTIONS</code> request is one of the best ways to understand the API.
+    </p>
+
+
+    <h2 id="support">Support</h2>
+    <p>Questions about the APIs can be sent <a href="https://github.com/freelawproject/courtlistener/discussions" target="_blank">to our GitHub Discussions forum</a> or via our <a href="{% url "contact" %}">contact form</a>.
+    </p>
+    <p>We prefer that questions be posted in the forum so they can help others. If you are a private organization posting to that forum, we will avoid sharing details about your organization.
+    </p>
+    <p>
+      <a href="https://github.com/freelawproject/courtlistener/discussions"
+          target="_blank"
+          class="btn btn-default">Ask in GitHub Discussions</a>
+      <a href="{% url "contact" %}"
+         target="_blank"
+         class="btn btn-default">Send us a Private Message</a>
+    </p>
+
+
+    <h2 id="data-modeling">Data Models</h2>
+    <p>The two images below show how the APIs work together. The first image shows the models we use for people, and the second shows the models we use for documents and metadata about them. You can see that these models currently link together on the Docket, Person, and Court tables. (<a
+      href="{% static "png/complete-model-v3.13.png" %}"
+      target="_blank">Here's a version of this diagram that shows everything all at once</a>.)
+    </p>
+    <p>
+      <a href="{% static "png/people-model-v3.13.png" %}"
+         target="_blank"
+         title="Click to see details.">
+        <img src="{% static "png/people-model-v3.13-small.png" %}"
+             width="640"
+             height="306"
+             class="img-responsive img-rounded">
+      </a>
+    </p>
+    <p>
+      <a href="{% static "png/search-model-v3.13.png" %}"
+         target="_blank"
+         title="Click to see details.">
+        <img src="{% static "png/search-model-v3.13-small.png" %}"
+             width="640"
+             height="754"
+             class="img-responsive img-rounded">
+      </a>
+    </p>
+
+
+    <h2 id="overview">API Overview</h2>
+    <p>This section explains the general principles of the API. These principals are driven by the features supported by the <a href="https://www.django-rest-framework.org/" target="_blank">Django REST Framework</a>. To go deep on any of these sections, we encourage you to check out the documentation there.
+    </p>
+
+
+    <h3 id="permissions">Permissions</h3>
+    <p>Some of our APIs are only available to select users. If you need greater access to these APIs, <a href="{% url "contact" %}">please get in touch</a>.
+    </p>
+    <p>All other endpoints are available according to the <a href="#limitations-throttles">throttling</a> and <a href="#authentication">authentication</a> limitations listed below.
+    </p>
+
+
+    <div class="well">
+      <h3 class="top">Your Authorization Token</h3>
+      {% if user.is_authenticated %}
+        <p>Your permanent token for use with this API is:</p>
+        <h4><code>{{ user.auth_token }}</code></h4>
+        <p>Do not share your API token. Keep it private like a password.
+        </p>
+        <p class="text-right"><a class="btn btn-default" href="{% url "view_api" %}#usage">See Usage</a></p>
+      {% else %}
+        <p><a href="{% url "sign-in" %}?next={{ request.path }}"
+                class="btn btn-primary btn-lg">Sign In To See Your Token</a>
+        </p>
+      {% endif %}
+    </div>
+
+
+    <h3 id="authentication">Authentication</h3>
+    <p>Authentication is necessary to monitor and throttle usage of the system, and so we can assist with any errors that may occur.
+    </p>
+    <p>Per our <a href="{% url "terms" %}#privacy">privacy policy</a>, we do not track your queries in the API, though we do collect statistical information for system monitoring.
+    </p>
+    <p>There are currently three types of authentication available on the API:
+    </p>
+    <ol>
+      <li>
+        <a href="https://www.django-rest-framework.org/api-guide/authentication/#tokenauthentication">HTTP Token Authentication</a>
+      </li>
+      <li>
+        <a href="https://docs.djangoproject.com/en/dev/topics/auth/" target="_blank">Cookie/Session Authentication</a>
+      </li>
+      <li>
+        <a href="https://en.wikipedia.org/wiki/Basic_access_authentication">HTTP Basic Authentication</a>
+      </li>
+    </ol>
+    <p>All of these methods are secure, so the choice of which to use is generally a question of what's most convenient for the context of your work. Our recommendations are:
+    </p>
+    <ul>
+      <li>Use Token Authentication for programmatic API access.
+      </li>
+      <li>Use Cookie/Session Authentication if you already have a user's cookie or are developing a system where you can ask the user to log into CourtListener.
+      </li>
+      <li>Use Basic Authentication if that's all your client supports.</li>
+    </ul>
+
+    <h4 id="token-auth">Token Authentication</h4>
+    <p>To use token authentication, use the <code>Authorization</code> HTTP Header. The key should prefix the <code>Token</code>, with whitespace separating the two strings. For example:
+    </p>
+    <pre class="scrollable">Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}</pre>
+    <p>Using curl, this looks like:</p>
+    <pre class="scrollable">curl "{% get_full_host %}{% url "opinioncluster-list" version="v3" %}" \
+  --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}'</pre>
+    <p>Note that quotes are used to enclose the whitespace in the header.</p>
+    <p class="alert alert-warning"><i class="fa fa-warning"></i> <strong>Careful!</strong> A common mistake is to forget the word "Token" in the header.
+    </p>
+    {% if user.is_authenticated %}
+      <p>Your permanent token for use with this API is being used in the examples above and is:</p>
+      <pre class="scrollable">{{ user.auth_token }}</pre>
+      <p>Do not share this value publicly via code check ins, emails, etc. Treat this value as you would a password. Do not email it to us.
+      </p>
+    {% else %}
+      <p><a href="{% url "sign-in" %}?next={{ request.path }}#token-auth">Sign in</a> to see your authorization token in this documentation.
+      </p>
+    {% endif %}
+
+    <h4 id="session-auth">Cookie Authentication</h4>
+    <p>To use Cookie Authentication <a href="{% url 'sign-in' %}">log into Courtlistener</a> and pass the cookie value using the standard cookie headers.
+    </p>
+
+    <h4 id="basic-auth">HTTP Basic Authentication</h4>
+    <p>To do HTTP Basic Authentication using curl, you might do something like this:
+    </p>
+    <pre class="scrollable">curl --user "harvey:your-password" \
+  "{% get_full_host %}{% url "opinioncluster-list" version="v3" %}"</pre>
+    <p>You can also do it in your browser with a url like:</p>
+    <pre class="scrollable">{% get_full_host username='harvey' password='your-password' %}{% url "opinioncluster-list" version="v3" %}</pre>
+    <p>But if you're using your browser, <a href="{% url 'sign-in' %}">you might as well just log in</a>.
+    </p>
+
+
+    <h3 id="formats">Serialization Formats</h3>
+    <p>Requests may be serialized as HTML, JSON, or XML. JSON is the default if no format is specified. The format you wish to receive is requested via the HTTP <code>Accept</code> header.
+    </p>
+    <p>The following media types and parameters can be used:
+    </p>
+    <ul>
+      <li><strong>HTML</strong>: The media type for HTML is <code>text/html</code>.</li>
+      <li><strong>JSON</strong>: The media type for JSON is <code>application/json</code>. Providing the <code>indent</code> media type parameter allows clients to set the indenting for the response, for example: <code>Accept: application/json; indent=2</code>.
+      </li>
+      <li><strong>XML</strong>: The media type for XML is <code>application/xml</code>.</li>
+    </ul>
+    <p>By default, browsers send an <code>Accept</code> header similar to:
+    </p>
+    <pre class="scrollable">text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8</pre>
+    <p>This states that <code>text/html</code> is the preferred serialization format. The API respects that, returning HTML when requested by a browser and returning JSON when no <code>Accept</code> header is provided, because JSON is the default.
+    </p>
+    <p>If you wish to set the <code>Accept</code> header using a tool like cURL, you can do so using the <code>--header</code> flag:
+    </p>
+    <pre class="scrollable">curl --header "Accept: application/xml" \
+  "{% get_full_host %}{% url "opinioncluster-list" version="v3" %}"</pre>
+    <p>All data is serialized using the utf-8 charset.</p>
+
+
+    <h3 id="parsing">Parsing Uploaded Content</h3>
+    <p>If you are a user that has write access to these APIs (most users do not), you will need to use the <code>Content-Type</code> HTTP header to explicitly set the format of the content you are uploading. The header can be set to any of the values that are available for serialization or to <code>application/x-www-form-urlencoded</code> or <code>multipart/form-data</code>, if you are sending form data.
+    </p>
+
+
+    <h3 id="filtering">Filtering</h3>
+    <p>With the exception of the search API, these APIs can be filtered using a technique similar to <a href="https://docs.djangoproject.com/en/dev/ref/models/querysets/#field-lookups">Django's field lookups</a>.
+    </p>
+    <p>To see how an endpoint can be filtered, do an <code>OPTIONS</code> request on the API and inspect the <code>filters</code> key in the response.
+    </p>
+    <p>In the <code>filters</code> key, you'll find a dictionary listing the fields that can be used for filtering along with their types, lookup fields, and any values (aka choices) that can be used for specific lookups.
+    </p>
+    <p>For example, this uses <code>jq</code> to look at the filters on the docket API:</p>
+    <pre class="pre-scrollable">curl -X OPTIONS \
+  --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
+  "{% get_full_host %}{% url "docket-list" version="v3" %}" | jq '.filters'</pre>
+    <p>That returns something like:</p>
+    <pre class="pre-scrollable tall">{
+  "id": {
+    "type": "NumberRangeFilter",
+    "lookup_types": [
+      "exact",
+      "gte",
+      "gt",
+      "lte",
+      "lt",
+      "range"
+    ]
+  },
+...</pre>
+    <p>This means that you can filter dockets using the ID field, and that you can do exact, greater than or equal, greater than, less than or equal, less than, or range filtering.
+    </p>
+    <p>You can use these filters with a double underscore. For example, this gets IDs greater than 500 and less than 1,000:</p>
+    <pre class="pre-scrollable">curl \
+  --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
+  "{% get_full_host %}{% url "docket-list" version="v3" %}?id__gt=500&id__lt=1000" | jq '.count'
+499</pre>
+    <p>It also allows ranges (inclusive):</p>
+    <pre class="pre-scrollable">curl \
+  --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
+  "{% get_full_host %}{% url "docket-list" version="v3" %}?id__range=500,1000" | jq '.count'
+501</pre>
+    <p>Filters can be combined using multiple <code>GET</code> parameters.</p>
+    <p>There are a few special types of filters. The first are <code>Related Filters</code>, which allow you to join filters across APIs. For example, when you are using the docket API, you'll see that it has a filter for the court API:
+    </p>
+    <pre>
+"court": {
+    "type": "RelatedFilter",
+    "lookup_types": "See available filters for 'Courts'"
+}</pre>
+    <p>This means that you can use any of the court filters on the docket API. If you do an <code>OPTIONS</code> request on the court API, you'll see its filters:
+    </p>
+    <pre class="pre-scrollable">curl -X OPTIONS \
+  --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
+  "{% get_full_host %}{% url "court-list" version="v3" %}" | jq '.filters'</pre>
+    <p>Again, one of the fitlers is the ID field, but it only allows exact values on this API:</p>
+    <pre>
+"id": {
+    "type": "CharFilter",
+    "lookup_types": [
+        "exact"
+    ]
+}</pre>
+    <p>Putting this together, here's how you look up dockets for a particular court:
+    </p>
+    <pre class="pre-scrollable">curl \
+  --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
+  "{% get_full_host %}{% url "docket-list" version="v3" %}?court=scotus&id__range=500,1000" | jq '.count'
+36</pre>
+    <p>This opens up many possibilities. For example, another filter on the <code>Court</code> endpoint is for <code>jurisdictions</code>. To use it, you would use a GET parameter like <code>court__jurisdictions=FD</code>. In this case, the double underscore allows you to join the filter from the other court API to the docket API.
+    </p>
+    <p>If you want to join a filter, you could do something like <code>court__full_name__startswith=district</code>. That would return dockets in courts where the court's name starts with "district".
+    </p>
+    <p><code>RelatedFilters</code> can span many objects. For example, if you want to get all the Supreme Court <code>Opinion</code> objects, you will need to do that with a query such as:
+    </p>
+    <pre class="pre-scrollable">curl "{% get_full_host %}{% url "opinion-list" version="v3" %}?cluster__docket__court=scotus"</pre>
+    <p>This uses the <code>Opinion</code> API to get <code>Opinions</code> that are part of <code>Opinion Clusters</code> that are on <code>Dockets</code> in the <code>Court</code> with the ID of <code>scotus</code>. To understand this data model better, see the <a href="{% url "case_law_api_help" %}">case law API documentation</a>.
+    </p>
+    <p>To use date filters, supply dates in <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO-8601 format</a>.
+    </p>
+    <p>A final trick that can be used with the filters is the exclusion parameter. Any filter can be converted into an exclusion filter by prepending it with an exclamation mark. For example, this returns <code>Dockets</code> from non-Federal Appellate jurisdictions:
+    </p>
+    <pre class=pre-scrollable>curl "{% get_full_host %}{% url "docket-list" version="v3" %}?court__jurisdiction!=F"</pre>
+    <p>You can see more examples of filters in <a href="https://github.com/freelawproject/courtlistener/blob/main/cl/api/tests.py" target="_blank">our automated tests</a>.
+    </p>
+
+
+
+    <h3 id="ordering">Ordering</h3>
+    <p>With the exception of the search API, you can see which fields can be used for ordering, by looking at the <code>ordering</code> key in an <code>OPTIONS</code> request. For example, the <code>Position</code> endpoint contains this:
+    </p>
+    <pre class="pre-scrollable tall">
+"ordering": [
+    "id",
+    "date_created",
+    "date_modified",
+    "date_nominated",
+    "date_elected",
+    "date_recess_appointment",
+    "date_referred_to_judicial_committee",
+    "date_judicial_committee_action",
+    "date_hearing",
+    "date_confirmation",
+    "date_start",
+    "date_retirement",
+    "date_termination"
+]</pre>
+    <p>Thus, you can order using any of these fields in conjunction with the <code>order_by</code> parameter.
+    </p>
+    <p>Descending order can be done using a minus sign. Multiple fields can be requested using a comma-separated list. This, for example, returns judicial <code>Positions</code> ordered by the most recently modified, then by the most recently elected:
+    </p>
+    <pre class="scrollable">curl "{% get_full_host %}{% url "position-list" version="v3" %}?order_by=-date_modified,-date_elected"</pre>
+    <p>Ordering by fields with duplicate values is non-deterministic. If you wish to order by such a field, you should provide a second field as a tie-breaker to consistently order results. For example, ordering by <code>date_filed</code> will not return consistent ordering for items that have the same date, but this can be fixed by ordering by <code>date_filed,id</code>. In that case, if two items have the same <code>date_filed</code> value, the tie will be broken by the <code>id</code> field.
+    </p>
+
+
+    <h3 id="field-selection">Field Selection</h3>
+    <p>To save bandwidth and increase serialization performance, fields can be limited by using the <code>fields</code> parameter with a comma-separated list of fields.
+    </p>
+    <p>For example, to only receive the <code>educations</code> and <code>date_modified</code> fields from the <code>Judge</code> endpoint you could do so with:
+    </p>
+    <pre class="scrollable">curl "{% get_full_host %}{% url "person-list" version="v3" %}?fields=educations,date_modified"
+{
+  "educations": [
+    {
+      "resource_uri": "https://www.courtlistener.com/api/rest/v3/educations/12856/",
+      "id": 12856,
+      "school": {
+        "resource_uri": "https://www.courtlistener.com/api/rest/v3/schools/4240/",
+        "id": 4240,
+        "is_alias_of": null,
+        "date_created": "2010-06-07T17:00:00-07:00",
+        "date_modified": "2010-06-07T17:00:00-07:00",
+        "name": "University of Maine",
+        "ein": 16000769
+      },
+      "person": "https://www.courtlistener.com/api/rest/v3/people/16214/",
+      "date_created": "2023-03-31T07:15:28.556198-07:00",
+      "date_modified": "2023-03-31T07:15:28.556222-07:00",
+      "degree_level": "jd",
+      "degree_detail": "",
+      "degree_year": 1979
+    }
+  ],
+  "date_modified": "2023-03-31T07:15:28.409594-07:00"
+},
+...</pre>
+    <p>You can also exclude fields using <code>fields!=educations,date_modified</code>.
+    </p>
+    <p>Unfortunately, this cannot be used for nested resources, though <a href="https://github.com/wimglenn/djangorestframework-queryfields/issues/8" target="_blank">there is an open issue tracking this</a>.
+    </p>
+
+
+    <h3 id="rates">Rate Limits</h3>
+    <p>Our APIs allow 5,000 queries per hour to authenticated users. Unauthenticated users are allowed 100 queries per day for experimentation.
+    </p>
+    <p>To debug throttling issues:</p>
+    <ol>
+      <li>Try browsing the API while logged into the website. If this works and your code fails, it usually means that your token authentication is not configured properly, and your code is getting throttled as an anonymous user, not according to your token.
+      </li>
+      <li>Review your recent API usage by looking in your <a href="{% url "view_api" %}#usage">profile</a>, but remember that it will show stats for the browsable API as well.
+      </li>
+      <li>Review the <a href="https://github.com/freelawproject/courtlistener/discussions/1497
+">authentication/throttling tips in our forum</a>.</li>
+    </ol>
+    <p>If, after checking the above, you need your rate limit increased, <a href="{% url "contact" %}">please get in touch</a> so we can help.
+    </p>
+
+
+    <h3 id="performance-tips">Performance Tips</h3>
+    <p>A few things to consider that may increase your performance:</p>
+    <ol>
+      <li>
+        <p>When doing deep crawls of the data, going to very high page numbers will incur increasingly bad performance. This is common in databases because to go to a high page number means sorting the entire data set, then counting to the correct location. Page 50 isn't a big deal. Page 2,000 starts getting slower.
+        </p>
+        <p>The fix to this solution is often to work with "slices" of the data. Instead of paginating across the whole result set, use a date field or another range-type field to only paginate over a smaller set of the data. For example, you could slice a large result set by the month of the date filing field to prevent deep pagination.
+        </p>
+        <p>Be careful to slice using a field with a normal distribution. Do not use one like <code>date_created</code>, which could have extreme spikes of activity.
+        </p>
+      </li>
+      <li>
+        <p>Avoid doing queries like <code>court__id=xyz</code> when you can instead do <code>court=xyz</code>. Doing queries with the extra <code>__id</code> introduces a join that can be expensive.</p>
+      </li>
+      <li>
+        <p>In general, less data is easier and faster to get than more. Could you use a field to filter your result set down to something smaller?
+        </p>
+      </li>
+      <li>
+        <p>When using the <code>search</code> endpoint, smaller result sets are faster. It isn't always possible to tweak your query to return fewer results, but sometimes it is possible to do a more precise query first, thus making a broader query unnecessary. For example, a search for an individual in their expected jurisdiction will be faster than doing it in the entire corpus. This will benefit from profiling in your use case and application.
+        </p>
+      </li>
+    </ol>
+
+    <h3 id="field-details">Advanced Field Definitions</h3>
+    <p>Placing an HTTP <code>OPTIONS</code> request on an API is the best way to learn about its fields, but some fields require further explanation. Click below to learn about these fields.
+    </p>
+    <p>
+      <a href="{% url "field_api_help" %}" class="btn btn-lg btn-default">Learn About Fields</a>
+    </p>
+
+
+    <h2 id="apis">APIs</h2>
+    <h3 id="case-law-apis">Case Law APIs</h3>
+    <p>We started collecting case law in 2009 and launched this API in 2013 as the <a href="https://free.law/2013/11/19/free-law-project-unveils-api-for-american-opinions/">first</a> API for legal decisions.
+    </p>
+    <p>Use this API to build your own collection of case law, complete complex legal research, and more.
+    </p>
+    <p>
+      <a href="{% url "case_law_api_help" %}" class="btn btn-default btn-lg">Learn More</a>
+    </p>
+
+    <h3 id="pacer-apis">PACER Data APIs</h3>
+    <p>We have almost half a billion PACER-related objects in the RECAP Archive. Use these APIs to access and understand this data.
+    </p>
+    <p>
+      <a href="{% url "pacer_api_help" %}" class="btn btn-default btn-lg">Learn More</a>
+    </p>
+
+    <h3 id="recap-apis">RECAP APIs</h3>
+    <p>Use these APIs to gather data from PACER and to share your PACER data with the public.
+    </p>
+    <p>
+      <a href="{% url "recap_api_help" %}" class="btn btn-default btn-lg">Learn More</a>
+    </p>
+
+    <h3 id="search-api">Search API</h3>
+    <p>CourtListener allows you to search across hundreds of millions of items with advanced fields and operators. Use this API to automate the CourtListener search engine.
+    </p>
+    <p>
+      <a href="{% url "search_api_help" %}" class="btn btn-lg btn-default">Learn More</a>
+    </p>
+
+    <h3 id="judge-apis">Judge APIs</h3>
+    <p>Use these APIs to query and analyze thousands of federal and state court judges, including their biographical information, political affiliations, education and employment histories, and more.
+    </p>
+    <p>
+      <a href="{% url "judge_api_help" %}" class="btn btn-default btn-lg">Learn More</a>
+    </p>
+
+    <h3 id="disclosure-apis">Financial Disclosure APIs</h3>
+    <p>All federal judges and many state judges must file financial disclosure documents to indicate any real or perceived biases they may have.
+    </p>
+    <p>Use these APIs to work with this information.</p>
+    <p>
+      <a href="{% url "financial_disclosures_api_help" %}" class="btn btn-default btn-lg">Learn More</a>
+    </p>
+
+    <h3 id="oral-argument-apis">Oral Argument APIs</h3>
+    <p>CourtListener is home to the largest collection of oral argument recordings on the Internet. Use thees APIs to gather and analyze our collection.
+    </p>
+    <p>
+      <a href="{% url "oral_argument_api_help" %}" class="btn btn-default btn-lg">Learn More</a>
+    </p>
+
+    <h3 id="citation-lookup">Citation Lookup and Verification&nbsp;API</h3>
+    <p>Use this API to look up citations in CourtListener's database of millions of citations.</p>
+    <p>This API can look up either an individual citation or can parse and look up every citation in a block of text. This can be useful as a guardrail to help prevent hallucinated citations.
+    </p>
+    <p>
+      <a href="{% url "citation_lookup_api" %}" class="btn btn-default btn-lg">Learn More</a>
+    </p>
+
+    <h3 id="citation-network-apis">Citation Network APIs</h3>
+    <p>Use these APIs to traverse and analyze our network of citations between legal decisions.
+    </p>
+    <p>
+      <a href="{% url "citation_api_help" %}" class="btn btn-default btn-lg">Learn More</a>
+    </p>
+
+    <h3 id="alerts">Alert APIs</h3>
+    <p>CourtListener is a scalable system for sending alerts by email or <a href="{% url "webhooks_getting_started" %}">webhook</a> based on search queries or for particular cases. Use these APIs to create, modify, list, and delete alerts.</p>
+    <p>
+      <a href="{% url "alert_api_help" %}" class="btn btn-lg btn-default">Learn More</a>
+    </p>
+
+    <h3 id="visualizations">Visualization APIs</h3>
+    <p>To see and make Supreme Court case visualizations, use these APIs.</p>
+    <p>
+      <a href="{% url "visualization_api_help" %}" class="btn btn-lg btn-default">Learn More</a>
+    </p>
+
+
+
+    <h2 id="available-jurisdictions"><span>Available Jurisdictions</span></h2>
+    <p>We currently have <strong>{{ court_count }}</strong> jurisdictions that can be accessed with our APIs. Details about the jurisdictions that are available, including all abbreviations, can <a href="{% url "court_index" %}">be found here</a>.
+    </p>
+
+    <h2 id="upgrades">Upgrades and Fixes</h2>
+    <p>Like the rest of the CourtListener platform, this API and its documentation are <a href="https://github.com/freelawproject/courtlistener">open source</a>. If it lacks functionality that you desire or if you find this documentation lacking, pull requests providing improvements are encouraged. Just get in touch via our <a href="{% url "contact" %}">contact form</a> to discuss your ideas. Or, if it's something quick, just go ahead and send us a pull request.
+    </p>
+    <p>Getting this kind support is one of the most rewarding things possible for an organization like ours and is a major goal of <a href="https://free.law">Free Law Project</a>. Many of the features you use on CourtListener were built this way. We're building something together.
+    </p>
+
+    <h2 id="maintenance-schedule"><span>Maintenance Schedule</span></h2>
+    <p>There is a weekly maintenance window from 21:00-23:59PT on Thursday nights. If you are scheduling cron jobs or otherwise crawling the API, you may experience downtime during this window.
+    </p>
+    <p>Additionally, we regularly perform bulk tasks on our servers and maintain <a href="https://www.google.com/calendar/embed?src=michaeljaylissner.com_fvcq09gchprghkghqa69be5hl0@group.calendar.google.com&ctz=America/Los_Angeles">a public calendar</a> for tracking them. You may encounter larger delays while bulk processing jobs are running.
+    </p>
+
+
+    <h2 id="api-change-log">API Change Log</h2>
+    <p><a href="{% url "rest_change_log" %}"
+          class="btn btn-lg btn-primary">View the Change Log</a>
+    </p>
+
+    <h2 id="copyright"><span>Copyright</span></h2>
+    <p>Our data is free of known copyright restrictions.<br />
+      <a rel="license" href="https://creativecommons.org/publicdomain/mark/1.0/">
+        <img src="{% static "png/cc-pd.png" %}" alt="Public Domain Mark" height="31" width="88"/>
+      </a>
+    </p>
+
+    {% include "includes/donate_footer_plea.html" %}
+
+  </div>
+{% endblock %}
diff --git a/cl/api/templates/rest-docs-vlatest.html b/cl/api/templates/rest-docs-vlatest.html
index fdf13b7d40..7afa3b3457 100644
--- a/cl/api/templates/rest-docs-vlatest.html
+++ b/cl/api/templates/rest-docs-vlatest.html
@@ -2,7 +2,7 @@
 {% load static %}
 {% load extras %}
 
-{% block title %}REST API, v3.15 &ndash; CourtListener.com{% endblock %}
+{% block title %}REST API, v4 &ndash; CourtListener.com{% endblock %}
 {% block description %}REST API for federal and state case law, PACER data, the searchable RECAP Archive, oral argument recordings and more. Provided by Free Law Project, a 501(c)(3) non-profit. Please donate to support this service.{% endblock %}
 {% block og_description %}REST API for federal and state case law, PACER data, the searchable RECAP Archive, oral argument recordings and more. Provided by Free Law Project, a 501(c)(3) non-profit. Please donate to support this service.{% endblock %}
 
@@ -25,7 +25,7 @@ <h4 class="v-offset-below-2">
     {% include "includes/toc_sidebar.html" %}
   </div>
   <div class="col-xs-12 col-md-8 col-lg-6">
-    <h1 id="about">REST API &ndash; v3.15</h1>
+    <h1 id="about">REST API &ndash; v4.0</h1>
 
     <p class="lead">APIs for developers and researchers that need granular legal data.
     </p>
@@ -33,12 +33,12 @@ <h1 id="about">REST API &ndash; v3.15</h1>
     </p>
     <p>Let's get started. To see and browse all the API URLs, click the button below:
     </p>
-    <p><a href="{% url "api-root" version="v3" %}"
+    <p><a href="{% url "api-root" version="v4" %}"
           target="_blank"
           class="btn btn-lg btn-primary">Show the APIs</a>
     </p>
     <p>We could have also pulled up that same information using curl, with a command like:</p>
-    <pre class="scrollable">curl "{% get_full_host %}{% url "api-root" version="v3" %}"</pre>
+    <pre class="scrollable">curl "{% get_full_host %}{% url "api-root" version="v4" %}"</pre>
     <p>Note that when you press the button in your browser, you get an HTML result, but when you run <code>curl</code> you get a JSON object. This is <a href="#formats">discussed in more depth below</a>.
     </p>
     <p class="alert alert-warning"><i class="fa fa-warning"></i> <strong>Listen Up!</strong> Something else that's curious just happened. You didn't authenticate to the API. To encourage experimentation, many of our APIs are open by default. The biggest gotcha people have is that they forget to enable authentication before deploying their code. Don't make this mistake! Remember to add <a href="#authentication">authentication</a>.
@@ -47,7 +47,7 @@ <h1 id="about">REST API &ndash; v3.15</h1>
     </p>
     <p>To learn more about an API, you can send an <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/OPTIONS">HTTP OPTIONS</a> request to it, like so:
     </p>
-    <pre class="scrollable">curl -X OPTIONS "{% get_full_host %}{% url "api-root" version="v3" %}"</pre>
+    <pre class="scrollable">curl -X OPTIONS "{% get_full_host %}{% url "api-root" version="v4" %}"</pre>
     <p>An <code>OPTIONS</code> request is one of the best ways to understand the API.
     </p>
 
@@ -155,7 +155,7 @@ <h4 id="token-auth">Token Authentication</h4>
     </p>
     <pre class="scrollable">Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}</pre>
     <p>Using curl, this looks like:</p>
-    <pre class="scrollable">curl "{% get_full_host %}{% url "opinioncluster-list" version="v3" %}" \
+    <pre class="scrollable">curl "{% get_full_host %}{% url "opinioncluster-list" version="v4" %}" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}'</pre>
     <p>Note that quotes are used to enclose the whitespace in the header.</p>
     <p class="alert alert-warning"><i class="fa fa-warning"></i> <strong>Careful!</strong> A common mistake is to forget the word "Token" in the header.
@@ -178,9 +178,9 @@ <h4 id="basic-auth">HTTP Basic Authentication</h4>
     <p>To do HTTP Basic Authentication using curl, you might do something like this:
     </p>
     <pre class="scrollable">curl --user "harvey:your-password" \
-  "{% get_full_host %}{% url "opinioncluster-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "opinioncluster-list" version="v4" %}"</pre>
     <p>You can also do it in your browser with a url like:</p>
-    <pre class="scrollable">{% get_full_host username='harvey' password='your-password' %}{% url "opinioncluster-list" version="v3" %}</pre>
+    <pre class="scrollable">{% get_full_host username='harvey' password='your-password' %}{% url "opinioncluster-list" version="v4" %}</pre>
     <p>But if you're using your browser, <a href="{% url 'sign-in' %}">you might as well just log in</a>.
     </p>
 
@@ -204,7 +204,7 @@ <h3 id="formats">Serialization Formats</h3>
     <p>If you wish to set the <code>Accept</code> header using a tool like cURL, you can do so using the <code>--header</code> flag:
     </p>
     <pre class="scrollable">curl --header "Accept: application/xml" \
-  "{% get_full_host %}{% url "opinioncluster-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "opinioncluster-list" version="v4" %}"</pre>
     <p>All data is serialized using the utf-8 charset.</p>
 
 
@@ -223,7 +223,7 @@ <h3 id="filtering">Filtering</h3>
     <p>For example, this uses <code>jq</code> to look at the filters on the docket API:</p>
     <pre class="pre-scrollable">curl -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-list" version="v3" %}" | jq '.filters'</pre>
+  "{% get_full_host %}{% url "docket-list" version="v4" %}" | jq '.filters'</pre>
     <p>That returns something like:</p>
     <pre class="pre-scrollable tall">{
   "id": {
@@ -243,12 +243,12 @@ <h3 id="filtering">Filtering</h3>
     <p>You can use these filters with a double underscore. For example, this gets IDs greater than 500 and less than 1,000:</p>
     <pre class="pre-scrollable">curl \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-list" version="v3" %}?id__gt=500&id__lt=1000" | jq '.count'
+  "{% get_full_host %}{% url "docket-list" version="v4" %}?id__gt=500&id__lt=1000" | jq '.count'
 499</pre>
     <p>It also allows ranges (inclusive):</p>
     <pre class="pre-scrollable">curl \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-list" version="v3" %}?id__range=500,1000" | jq '.count'
+  "{% get_full_host %}{% url "docket-list" version="v4" %}?id__range=500,1000" | jq '.count'
 501</pre>
     <p>Filters can be combined using multiple <code>GET</code> parameters.</p>
     <p>There are a few special types of filters. The first are <code>Related Filters</code>, which allow you to join filters across APIs. For example, when you are using the docket API, you'll see that it has a filter for the court API:
@@ -262,7 +262,7 @@ <h3 id="filtering">Filtering</h3>
     </p>
     <pre class="pre-scrollable">curl -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "court-list" version="v3" %}" | jq '.filters'</pre>
+  "{% get_full_host %}{% url "court-list" version="v4" %}" | jq '.filters'</pre>
     <p>Again, one of the fitlers is the ID field, but it only allows exact values on this API:</p>
     <pre>
 "id": {
@@ -275,7 +275,7 @@ <h3 id="filtering">Filtering</h3>
     </p>
     <pre class="pre-scrollable">curl \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-list" version="v3" %}?court=scotus&id__range=500,1000" | jq '.count'
+  "{% get_full_host %}{% url "docket-list" version="v4" %}?court=scotus&id__range=500,1000" | jq '.count'
 36</pre>
     <p>This opens up many possibilities. For example, another filter on the <code>Court</code> endpoint is for <code>jurisdictions</code>. To use it, you would use a GET parameter like <code>court__jurisdictions=FD</code>. In this case, the double underscore allows you to join the filter from the other court API to the docket API.
     </p>
@@ -283,14 +283,14 @@ <h3 id="filtering">Filtering</h3>
     </p>
     <p><code>RelatedFilters</code> can span many objects. For example, if you want to get all the Supreme Court <code>Opinion</code> objects, you will need to do that with a query such as:
     </p>
-    <pre class="pre-scrollable">curl "{% get_full_host %}{% url "opinion-list" version="v3" %}?cluster__docket__court=scotus"</pre>
+    <pre class="pre-scrollable">curl "{% get_full_host %}{% url "opinion-list" version="v4" %}?cluster__docket__court=scotus"</pre>
     <p>This uses the <code>Opinion</code> API to get <code>Opinions</code> that are part of <code>Opinion Clusters</code> that are on <code>Dockets</code> in the <code>Court</code> with the ID of <code>scotus</code>. To understand this data model better, see the <a href="{% url "case_law_api_help" %}">case law API documentation</a>.
     </p>
     <p>To use date filters, supply dates in <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO-8601 format</a>.
     </p>
     <p>A final trick that can be used with the filters is the exclusion parameter. Any filter can be converted into an exclusion filter by prepending it with an exclamation mark. For example, this returns <code>Dockets</code> from non-Federal Appellate jurisdictions:
     </p>
-    <pre class=pre-scrollable>curl "{% get_full_host %}{% url "docket-list" version="v3" %}?court__jurisdiction!=F"</pre>
+    <pre class=pre-scrollable>curl "{% get_full_host %}{% url "docket-list" version="v4" %}?court__jurisdiction!=F"</pre>
     <p>You can see more examples of filters in <a href="https://github.com/freelawproject/courtlistener/blob/main/cl/api/tests.py" target="_blank">our automated tests</a>.
     </p>
 
@@ -319,7 +319,7 @@ <h3 id="ordering">Ordering</h3>
     </p>
     <p>Descending order can be done using a minus sign. Multiple fields can be requested using a comma-separated list. This, for example, returns judicial <code>Positions</code> ordered by the most recently modified, then by the most recently elected:
     </p>
-    <pre class="scrollable">curl "{% get_full_host %}{% url "position-list" version="v3" %}?order_by=-date_modified,-date_elected"</pre>
+    <pre class="scrollable">curl "{% get_full_host %}{% url "position-list" version="v4" %}?order_by=-date_modified,-date_elected"</pre>
     <p>Ordering by fields with duplicate values is non-deterministic. If you wish to order by such a field, you should provide a second field as a tie-breaker to consistently order results. For example, ordering by <code>date_filed</code> will not return consistent ordering for items that have the same date, but this can be fixed by ordering by <code>date_filed,id</code>. In that case, if two items have the same <code>date_filed</code> value, the tie will be broken by the <code>id</code> field.
     </p>
 
@@ -329,14 +329,14 @@ <h3 id="field-selection">Field Selection</h3>
     </p>
     <p>For example, to only receive the <code>educations</code> and <code>date_modified</code> fields from the <code>Judge</code> endpoint you could do so with:
     </p>
-    <pre class="scrollable">curl "{% get_full_host %}{% url "person-list" version="v3" %}?fields=educations,date_modified"
+    <pre class="scrollable">curl "{% get_full_host %}{% url "person-list" version="v4" %}?fields=educations,date_modified"
 {
   "educations": [
     {
-      "resource_uri": "https://www.courtlistener.com/api/rest/v3/educations/12856/",
+      "resource_uri": "https://www.courtlistener.com/api/rest/v4/educations/12856/",
       "id": 12856,
       "school": {
-        "resource_uri": "https://www.courtlistener.com/api/rest/v3/schools/4240/",
+        "resource_uri": "https://www.courtlistener.com/api/rest/v4/schools/4240/",
         "id": 4240,
         "is_alias_of": null,
         "date_created": "2010-06-07T17:00:00-07:00",
@@ -344,7 +344,7 @@ <h3 id="field-selection">Field Selection</h3>
         "name": "University of Maine",
         "ein": 16000769
       },
-      "person": "https://www.courtlistener.com/api/rest/v3/people/16214/",
+      "person": "https://www.courtlistener.com/api/rest/v4/people/16214/",
       "date_created": "2023-03-31T07:15:28.556198-07:00",
       "date_modified": "2023-03-31T07:15:28.556222-07:00",
       "degree_level": "jd",
diff --git a/cl/api/templates/search-api-docs-v3.html b/cl/api/templates/search-api-docs-v3.html
new file mode 100644
index 0000000000..deee13ae9b
--- /dev/null
+++ b/cl/api/templates/search-api-docs-v3.html
@@ -0,0 +1,238 @@
+{% extends "base.html" %}
+{% load extras %}
+
+{% block title %}Legal Search API – CourtListener.com{% endblock %}
+{% block og_title %}Legal Search API – CourtListener.com{% endblock %}
+
+{% block description %}Use this API to search case law, federal filings and cases, judges, and oral argument audio files.{% endblock %}
+{% block og_description %}Use this API to search case law, federal filings and cases, judges, and oral argument audio files.{% endblock %}
+
+{% block sidebar %}{% endblock %}
+
+{% block footer-scripts %}
+  {% include "includes/anchors.html" %}
+{% endblock %}
+
+{% block content %}
+<div class="col-xs-12 hidden-md hidden-lg">
+  <h4 class="v-offset-below-2">
+    <i class="fa fa-arrow-circle-o-left gray"></i>
+    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+  </h4>
+</div>
+
+
+<div id="toc-container" class="hidden-xs hidden-sm col-md-3">
+  <div id="toc">
+    <h4 class="v-offset-below-3">
+      <i class="fa fa-arrow-circle-o-left gray"></i>
+      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    </h4>
+    <h3>Table of Contents</h3>
+    <ul>
+      <li><a href="#about">Overview</a></li>
+      <li><a href="#usage">Basic Usage</a></li>
+      <li><a href="#understanding">Understanding</a></li>
+      <ul>
+        <li><a href="#type">Result Types</a></li>
+        <li><a href="#ordering">Ordering</a></li>
+        <li><a href="#filtering">Filtering</a></li>
+        <li><a href="#fields">Fields</a></li>
+        <li><a href="#notes">Special Notes</a></li>
+      </ul>
+      <li><a href="#monitoring">Monitoring a Query</a></li>
+    </ul>
+  </div>
+</div>
+
+<div class="col-xs-12 col-md-8 col-lg-6">
+  <h1 id="about">Legal Search&nbsp;API</h1>
+  <h2><code>{% url "search-list" version="v3" %}</code></h2>
+  <p class="lead v-offset-above-3">Use this API to search case law, PACER data, judges, and oral argument audio recordings.</p>
+  <p>To get the most out of this API, see our <a href="{% url "coverage" %}">coverage</a> and <a href="{% url "advanced_search" %}">advanced operators</a> documentation.
+  </p>
+
+  <h2 id="usage">Basic Usage</h2>
+  <p>This API uses the same GET parameters as the front end of the website. To use this API, place a search query on the front end of the website. That will give you a URL like:
+  </p>
+  <pre class="pre-scrollable">{% get_full_host %}/q=foo</pre>
+  <p>To make this into an API request, copy the GET parameters from this URL to the API endpoint, creating a request like:
+  </p>
+  <pre class="pre-scrollable">curl -X GET \
+  --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
+  '{% get_full_host %}{% url "search-list" version="v3" %}?q=foo'</pre>
+  <p>That returns:</p>
+  <pre class="pre-scrollable tall">{
+  "count": 2369,
+  "next": "https://www.courtlistener.com/api/rest/v3/search/?page=2&q=foo",
+  "previous": null,
+  "results": [
+    {
+      "absolute_url": "/opinion/106359/fong-foo-v-united-states/",
+      "attorney": "Arthur Richenthal argued the causes for petitioners and filed briefs for petitioner in No. 65. David E. Feller filed briefs for petitioners in No. 64., Solicitor General Cox argued the causes for the United States. With him on the briefs were Assistant Attorney General Miller, Stephen J. Poliak, Beatrice Rosenberg, Philip R. Monahan and J. F. Bishop.",
+      "author_id": null,
+      "caseName": "Fong Foo v. United States",
+      "caseNameShort": "Fong Foo",
+      "citation": [
+        "7 L. Ed. 2d 629",
+        "82 S. Ct. 671",
+        "369 U.S. 141",
+        "1962 U.S. LEXIS 1600"
+      ],
+      "citeCount": 357,
+      "cites": [
+        94515,
+        98794,
+        100989,
+        101974,
+        106273,
+        253004
+      ],
+      "cluster_id": 106359,
+      "court": "Supreme Court of the United States",
+      "court_citation_string": "SCOTUS",
+      "court_exact": "scotus",
+      "court_id": "scotus",
+      "dateArgued": null,
+      "dateFiled": "1962-03-19T00:00:00-08:00",
+      "dateReargued": null,
+      "dateReargumentDenied": null,
+      "docketNumber": "64",
+      "docket_id": 1153854,
+      "download_url": null,
+      "id": 106359,
+      "joined_by_ids": null,
+      "judge": "Harlan, Clark, Whittaker",
+      "lexisCite": "1962 U.S. LEXIS 1600",
+      "local_path": null,
+      "neutralCite": null,
+      "non_participating_judge_ids": null,
+      "pagerank": null,
+      "panel_ids": null,
+      "per_curiam": null,
+      "scdb_id": "1961-048",
+      "sibling_ids": [
+        106359,
+        9422362,
+        9422363,
+        9422364
+      ],
+      "snippet": "\n\n\n    \n369 U.S. 141 (1962)\nFONG <mark>FOO</mark> ET AL.\nv.\nUNITED STATES.\nNo. 64.\nSupreme Court of United States.&hellip;Court of the United States\nscotus\nSCOTUS\n\n\n\n    FONG <mark>FOO</mark> Et Al. v. UNITED STATES\n\n\nHarlan, Clark, Whittaker",
+      "source": "LRU",
+      "status": "Precedential",
+      "status_exact": "Precedential",
+      "suitNature": "",
+      "timestamp": "2024-03-01T14:12:07.892000-08:00",
+      "type": "010combined"
+    },
+    ...</pre>
+  <p>That's the simple version. Read on to learn the rest.</p>
+
+
+  <h2 id="understanding">Understanding the API</h2>
+  <p>Unlike most APIs on CourtListener, this API is powered by our search engine, not our database.
+  </p>
+  <p>This means that it does not use the same approach to ordering, filtering, or field definitions as our other APIs, and sending an HTTP <code>OPTIONS</code> request won't be useful.
+  </p>
+
+  <h3 id="type">Setting the Result <code>type</code></h3>
+  <p>The most important parameter in this API is <code>type</code>. This parameter sets the type of object you are querying:
+  </p>
+  <table class="table">
+    <thead>
+    <tr>
+      <th>Type</th>
+      <th>Definition</th>
+    </tr>
+    </thead>
+    <tbody>
+    <tr>
+      <td><code>o</code></td>
+      <td>Case law opinions</td>
+    </tr>
+    <tr>
+      <td><code>r</code></td>
+      <td>Federal filing documents from PACER</td>
+    </tr>
+    <tr>
+      <td><code>d</code></td>
+      <td>Federal cases (dockets) from PACER</td>
+    </tr>
+    <tr>
+      <td><code>p</code></td>
+      <td>Judges</td>
+    </tr>
+    <tr>
+      <td><code>oa</code></td>
+      <td>Oral argument audio files</td>
+    </tr>
+    </tbody>
+  </table>
+  <p>For example, this query searches case law:</p>
+  <pre class="pre-scrollable">{% get_full_host %}/q=foo&type=o</pre>
+  <p>And this query searches federal filings in the PACER system:</p>
+  <pre class="pre-scrollable">{% get_full_host %}/q=foo&type=r</pre>
+  <p>If the <code>type</code> parameter is not provided, the default is to search case law.</p>
+
+
+  <h3 id="ordering">Ordering Results</h3>
+  <p>Each search <code>type</code> can be sorted by certain fields. These are available on the front end in the ordering drop down, which sets the <code>order_by</code> parameter.
+  </p>
+
+
+  <h3 id="filtering">Filtering Results</h3>
+  <p>Results can be filtered with the input boxes provided on the front end or by <a href="{% url "advanced_search" %}">advanced query operators</a> provided to the <code>q</code> parameter.
+  </p>
+  <p>The best way to refine your query is to do so on the front end, and then copy the GET parameters to the API.
+  </p>
+
+
+  <h3 id="fields">Fields</h3>
+  <p>Unlike most of the fields on CourtListener, many fields on this API are provided in camelCase instead of snake_case. This is to make it easier for users to place queries like:
+  </p>
+  <pre class="pre-scrollable">caseName:foo</pre>
+  <p>Instead of:</p>
+  <pre class="pre-scrollable">case_name:foo</pre>
+  <p>All available fields are listed on the <a href="{% url "advanced_search" %}">advanced operators help page</a>.
+  </p>
+  <p>To understand the meaning of a field, find the object in our regular APIs that it corresponds to, and send an HTTP <code>OPTIONS</code> request to the API.
+  </p>
+  <p>For example, the <code>docketNumber</code> field in the search engine corresponds to the <code>docket_number</code> field in the <code>docket</code> API, so an HTTP <code>OPTIONS</code> request to that API returns its definition:
+  </p>
+  <pre class="pre-scrollable">curl -X OPTIONS \
+  --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
+  "{% get_full_host %}{% url "docket-list" version="v3" %}" \
+  | jq '.actions.POST.docket_number</pre>
+  <p>After filtering through <a href="https://github.com/jqlang/jq"><code>jq</code></a>, that returns:</p>
+  <pre class="pre-scrollable">{
+  "type": "string",
+  "required": false,
+  "read_only": false,
+  "label": "Docket number",
+  "help_text": "The docket numbers of a case, can be consolidated and quite long. In some instances they are too long to be indexed by postgres and we store the full docket in the correction field on the Opinion Cluster."
+}</pre>
+
+
+  <h3 id="notes">Special Notes</h3>
+  <p>A few fields deserve special consideration:</p>
+  <ol>
+    <li>
+      <p>As in the front end, when the <code>type</code> is set to return case law, only published results are returned by default. To include unpublished and other statuses, you need to explicitly request them.
+      </p>
+    </li>
+    <li>
+      <p>The <code>snippet</code> field contains the same values as are found on the front end. This uses the HTML5 <code>&lt;mark&gt;</code> element to identify up to five matches in a document.
+      </p>
+      <p>This field only responds to arguments provided to the <code>q</code> parameter.  If the <code>q</code> parameter is not used, the <code>snippet</code> field will show the first 500 characters of the <code>text</code> field.
+      </p>
+    </li>
+  </ol>
+
+
+  <h2 id="monitoring">Monitoring a Query for New&nbsp;Results</h2>
+  <p>To monitor queries for new results, use the <a href="{% url "search_api_help" %}">Alert API</a>, which will send emails or webhook events when there are new results.
+  </p>
+
+  {% include "includes/donate_footer_plea.html" %}
+</div>
+{% endblock %}
diff --git a/cl/api/templates/search-api-docs-vlatest.html b/cl/api/templates/search-api-docs-vlatest.html
index deee13ae9b..87f0cef413 100644
--- a/cl/api/templates/search-api-docs-vlatest.html
+++ b/cl/api/templates/search-api-docs-vlatest.html
@@ -17,7 +17,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -26,7 +26,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -47,7 +47,7 @@ <h3>Table of Contents</h3>
 
 <div class="col-xs-12 col-md-8 col-lg-6">
   <h1 id="about">Legal Search&nbsp;API</h1>
-  <h2><code>{% url "search-list" version="v3" %}</code></h2>
+  <h2><code>{% url "search-list" version=version %}</code></h2>
   <p class="lead v-offset-above-3">Use this API to search case law, PACER data, judges, and oral argument audio recordings.</p>
   <p>To get the most out of this API, see our <a href="{% url "coverage" %}">coverage</a> and <a href="{% url "advanced_search" %}">advanced operators</a> documentation.
   </p>
@@ -60,11 +60,11 @@ <h2 id="usage">Basic Usage</h2>
   </p>
   <pre class="pre-scrollable">curl -X GET \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  '{% get_full_host %}{% url "search-list" version="v3" %}?q=foo'</pre>
+  '{% get_full_host %}{% url "search-list" version=version %}?q=foo'</pre>
   <p>That returns:</p>
   <pre class="pre-scrollable tall">{
   "count": 2369,
-  "next": "https://www.courtlistener.com/api/rest/v3/search/?page=2&q=foo",
+  "next": "https://www.courtlistener.com/api/rest/{{ version }}/search/?page=2&q=foo",
   "previous": null,
   "results": [
     {
@@ -201,7 +201,7 @@ <h3 id="fields">Fields</h3>
   </p>
   <pre class="pre-scrollable">curl -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "docket-list" version="v3" %}" \
+  "{% get_full_host %}{% url "docket-list" version=version %}" \
   | jq '.actions.POST.docket_number</pre>
   <p>After filtering through <a href="https://github.com/jqlang/jq"><code>jq</code></a>, that returns:</p>
   <pre class="pre-scrollable">{
diff --git a/cl/api/templates/visualizations-api-docs-vlatest.html b/cl/api/templates/visualizations-api-docs-vlatest.html
index 5e7f8fe0a4..6fa134ee68 100644
--- a/cl/api/templates/visualizations-api-docs-vlatest.html
+++ b/cl/api/templates/visualizations-api-docs-vlatest.html
@@ -19,7 +19,7 @@
 <div class="col-xs-12 hidden-md hidden-lg">
   <h4 class="v-offset-below-2">
     <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
   </h4>
 </div>
 
@@ -28,7 +28,7 @@ <h4 class="v-offset-below-2">
   <div id="toc">
     <h4 class="v-offset-below-3">
       <i class="fa fa-arrow-circle-o-left gray"></i>
-      <a href="{% url "rest_docs" version="v3" %}">Back to API Docs</a>
+      <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
     </h4>
     <h3>Table of Contents</h3>
     <ul>
@@ -42,7 +42,7 @@ <h3>Table of Contents</h3>
 
 <div class="col-xs-12 col-md-8 col-lg-6">
   <h1 id="about">Supreme Court Visualization&nbsp;API</h1>
-  <h2><code>{% url "scotusmap-list" version="v3" %}</code></h2>
+  <h2><code>{% url "scotusmap-list" version=version %}</code></h2>
   <p class="lead">Use this API to programmatically see and create <a href="{% url "mapper_homepage" %}">visualizations of Supreme Court networks</a> in CourtListener.
   </p>
   <p>All visualizations are associated with a user and are private by default. When you GET these endpoints, you will see data for visualizations that have been made public by their owners or that you have created yourself.
@@ -52,11 +52,11 @@ <h2><code>{% url "scotusmap-list" version="v3" %}</code></h2>
   <h2 id="creating">Creating Visualizations</h2>
   <p>To create a new visualization, send an HTTP <code>POST</code> with a title, a starting cluster ID, and an ending cluster ID:</p>
   <pre class="scrollable">curl -X POST \
-  --data 'cluster_start=/api/rest/v3/clusters/105659/' \
-  --data 'cluster_end=/api/rest/v3/clusters/111891/' \
+  --data 'cluster_start=/api/rest/{{ version }}/clusters/105659/' \
+  --data 'cluster_end=/api/rest/{{ version }}/clusters/111891/' \
   --data 'title=A map from Trop to Salerno' \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "scotusmap-list" version="v3" %}"</pre>
+  "{% get_full_host %}{% url "scotusmap-list" version=version %}"</pre>
   <p>The <code>cluster_start</code> and <code>cluster_end</code> parameters use URLs instead of IDs.</p>
   <p>The above command creates a visualization unless there are no connections between the start and end clusters or the network becomes too large to generate.
   </p>
@@ -68,7 +68,7 @@ <h2 id="editing">Editing and Deleting Visualizations</h2>
   <pre class="scrollable">curl -X PATCH \
   --data 'published=True' \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
-  "{% get_full_host %}{% url "scotusmap-detail" version="v3" pk="1" %}"</pre>
+  "{% get_full_host %}{% url "scotusmap-detail" version=version pk="1" %}"</pre>
   <p>Similar commands can be used to update other non-readonly fields.</p>
   <p>To soft-delete a visualization, flip the <code>deleted</code> field to <code>True</code>. To hard-delete, send an HTTP <code>DELETE</code> request.
   </p>
diff --git a/cl/api/urls.py b/cl/api/urls.py
index 7413a287b4..64989ab4e4 100644
--- a/cl/api/urls.py
+++ b/cl/api/urls.py
@@ -194,98 +194,98 @@
     path("help/api/", views.api_index, name="api_index"),
     path("help/api/jurisdictions/", views.court_index, name="court_index"),
     re_path(
-        r"^help/api/rest/(?P<version>v[123])?/?$",
+        r"^help/api/rest/(?P<version>v[1234])?/?$",
         views.rest_docs,
         name="rest_docs",
     ),
-    path(
-        "help/api/rest/v3/citation-lookup/",
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?citation-lookup/$",
         views.citation_lookup_api,
         name="citation_lookup_api",
     ),
-    path(
-        "help/api/rest/v3/case-law/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?case-law/$",
+        views.VersionedTemplateView.as_view(
             template_name="case-law-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="case_law_api_help",
     ),
-    path(
-        "help/api/rest/v3/citations/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?citations/$",
+        views.VersionedTemplateView.as_view(
             template_name="citation-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="citation_api_help",
     ),
-    path(
-        "help/api/rest/v3/pacer/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?pacer/$",
+        views.VersionedTemplateView.as_view(
             template_name="pacer-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="pacer_api_help",
     ),
-    path(
-        "help/api/rest/v3/recap/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?recap/$",
+        views.VersionedTemplateView.as_view(
             template_name="recap-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="recap_api_help",
     ),
-    path(
-        "help/api/rest/v3/judges/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?judges/$",
+        views.VersionedTemplateView.as_view(
             template_name="judge-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="judge_api_help",
     ),
-    path(
-        "help/api/rest/v3/oral-arguments/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?oral-arguments/$",
+        views.VersionedTemplateView.as_view(
             template_name="oral-argument-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="oral_argument_api_help",
     ),
-    path(
-        "help/api/rest/v3/visualizations/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?visualizations/$",
+        views.VersionedTemplateView.as_view(
             template_name="visualizations-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="visualization_api_help",
     ),
-    path(
-        "help/api/rest/v3/financial-disclosures/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?financial-disclosures/$",
+        views.VersionedTemplateView.as_view(
             template_name="financial-disclosure-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="financial_disclosures_api_help",
     ),
-    path(
-        "help/api/rest/v3/search/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?search/$",
+        views.VersionedTemplateView.as_view(
             template_name="search-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="search_api_help",
     ),
-    path(
-        "help/api/rest/v3/alerts/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?alerts/$",
+        views.VersionedTemplateView.as_view(
             template_name="alert-api-docs-vlatest.html",
             extra_context={"private": False},
         ),
         name="alert_api_help",
     ),
-    path(
-        "help/api/rest/v3/fields/",
-        TemplateView.as_view(
+    re_path(
+        r"^help/api/rest/(?:(?P<version>v[34])/)?fields/$",
+        views.VersionedTemplateView.as_view(
             template_name="field-help.html",
             extra_context={"private": True},
         ),
diff --git a/cl/api/views.py b/cl/api/views.py
index 86941007b0..69e781a08e 100644
--- a/cl/api/views.py
+++ b/cl/api/views.py
@@ -10,6 +10,7 @@
 from django.shortcuts import aget_object_or_404  # type: ignore[attr-defined]
 from django.template.response import TemplateResponse
 from django.views.decorators.cache import cache_page
+from django.views.generic import TemplateView
 from requests import Session
 
 from cl.lib.elasticsearch_utils import do_es_alert_estimation_query
@@ -128,7 +129,10 @@ def parse_throttle_rate_for_template(rate: str) -> tuple[int, str] | None:
     return int(num), duration_as_str[period[0]]
 
 
-async def citation_lookup_api(request: HttpRequest) -> HttpResponse:
+async def citation_lookup_api(
+    request: HttpRequest, version=None
+) -> HttpResponse:
+
     cite_count = await Citation.objects.acount()
     rate = settings.REST_FRAMEWORK["DEFAULT_THROTTLE_RATES"]["citations"]  # type: ignore
     default_throttle_rate = parse_throttle_rate_for_template(rate)
@@ -141,13 +145,17 @@ async def citation_lookup_api(request: HttpRequest) -> HttpResponse:
 
     return TemplateResponse(
         request,
-        "citation-lookup-api.html",
+        [
+            f"citation-lookup-api-{version}.html",
+            "citation-lookup-api-vlatest.html",
+        ],
         {
             "cite_count": cite_count,
             "default_throttle_rate": default_throttle_rate,
             "custom_throttle_rate": custom_throttle_rate,
             "max_citation_per_request": settings.MAX_CITATIONS_PER_REQUEST,  # type: ignore
             "private": False,
+            "version": version if version else "v4",
         },
     )
 
@@ -343,3 +351,19 @@ async def webhooks_docs(request, version=None):
         [f"webhooks-docs-{version}.html", "webhooks-docs-vlatest.html"],
         context,
     )
+
+
+class VersionedTemplateView(TemplateView):
+    """Custom template view to handle the right template based on the path
+    version requested.
+    """
+
+    def get_template_names(self):
+        version = self.kwargs.get("version", "vlatest")
+        base_template = self.template_name.replace("-vlatest", f"-{version}")
+        return [base_template, self.template_name]
+
+    def get_context_data(self, **kwargs):
+        context = super().get_context_data(**kwargs)
+        context["version"] = self.kwargs.get("version", "v4")
+        return context

From 4d9456f8bcc9861282cad42a1c716f5ff6ab5b20 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Tue, 10 Sep 2024 15:50:36 -0700
Subject: [PATCH 02/19] Update rest-docs-vlatest.html

---
 cl/api/templates/rest-docs-vlatest.html | 1 +
 1 file changed, 1 insertion(+)

diff --git a/cl/api/templates/rest-docs-vlatest.html b/cl/api/templates/rest-docs-vlatest.html
index 7afa3b3457..f803ea6872 100644
--- a/cl/api/templates/rest-docs-vlatest.html
+++ b/cl/api/templates/rest-docs-vlatest.html
@@ -494,6 +494,7 @@ <h3 id="visualizations">Visualization APIs</h3>
     <h2 id="available-jurisdictions"><span>Available Jurisdictions</span></h2>
     <p>We currently have <strong>{{ court_count }}</strong> jurisdictions that can be accessed with our APIs. Details about the jurisdictions that are available, including all abbreviations, can <a href="{% url "court_index" %}">be found here</a>.
     </p>
+    <!-- Jurisdictions court count shows 0, but should be 3k+ -->
 
     <h2 id="upgrades">Upgrades and Fixes</h2>
     <p>Like the rest of the CourtListener platform, this API and its documentation are <a href="https://github.com/freelawproject/courtlistener">open source</a>. If it lacks functionality that you desire or if you find this documentation lacking, pull requests providing improvements are encouraged. Just get in touch via our <a href="{% url "contact" %}">contact form</a> to discuss your ideas. Or, if it's something quick, just go ahead and send us a pull request.

From 843389b8071b26b93d6d8de2ded6f4e22a6b22d0 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Tue, 10 Sep 2024 17:13:08 -0700
Subject: [PATCH 03/19] Update rest-docs-vlatest.html

---
 cl/api/templates/rest-docs-vlatest.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cl/api/templates/rest-docs-vlatest.html b/cl/api/templates/rest-docs-vlatest.html
index f803ea6872..d6e7661556 100644
--- a/cl/api/templates/rest-docs-vlatest.html
+++ b/cl/api/templates/rest-docs-vlatest.html
@@ -263,7 +263,7 @@ <h3 id="filtering">Filtering</h3>
     <pre class="pre-scrollable">curl -X OPTIONS \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}' \
   "{% get_full_host %}{% url "court-list" version="v4" %}" | jq '.filters'</pre>
-    <p>Again, one of the fitlers is the ID field, but it only allows exact values on this API:</p>
+    <p>Again, one of the filters is the ID field, but it only allows exact values on this API:</p>
     <pre>
 "id": {
     "type": "CharFilter",

From 27c57ae83cf2e0061e9fd113161a90115b005392 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Tue, 10 Sep 2024 17:43:02 -0700
Subject: [PATCH 04/19] Update field-help.html

Removed "human" from "human editors" per Mike's request.
---
 cl/api/templates/field-help.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/cl/api/templates/field-help.html b/cl/api/templates/field-help.html
index 4e0a8156b3..54a7e90d08 100644
--- a/cl/api/templates/field-help.html
+++ b/cl/api/templates/field-help.html
@@ -80,9 +80,9 @@ <h3 id="case-names">Case Names</h3>
     <li><code>case_name_full</code>: This is the full list of plaintiffs and defendants in a case, sometimes going on for hundreds of words, and often including titles or other information. For example: <em>Roe Et Al v. Wade, District Attorney of Dallas County</em>.
     </li>
   </ol>
-  <p>All cases have at least one of these values, many have two values, and some have all three. A <code>case_name_short</code> was generated algorithmically for every case possible, but about 40% of cases were too complicated for our program to process and so they were left blank. Human editors have ensured that every Supreme Court case from 1945 to 2018 has a <code>case_name_short</code> value.
+  <p>All cases have at least one of these values, many have two values, and some have all three. A <code>case_name_short</code> was generated algorithmically for every case possible, but about 40% of cases were too complicated for our program to process and so they were left blank. Editors have ensured that every Supreme Court case from 1945 to 2018 has a <code>case_name_short</code> value.
   </p>
-  <p><code>case_name</code> is available for the majority of cases, except those that were imported from Resource.org, which only provided <code>case_name_full</code> values. When that happened, there was no way for us to condense a <code>case_name_full</code>, so until a human editor is available to review them, they will lack this value. All cases have either a <code>case_name</code> or a <code>case_name_full</code> value.
+  <p><code>case_name</code> is available for the majority of cases, except those that were imported from Resource.org, which only provided <code>case_name_full</code> values. When that happened, there was no way for us to condense a <code>case_name_full</code>, so until an editor is available to review them, they will lack this value. All cases have either a <code>case_name</code> or a <code>case_name_full</code> value.
   </p>
   <p>Our advice is to use a <code>case_name</code> if it is available and to fall back on the <code>case_name_full</code> if it is not. If you are interested in sponsoring trained humans to improve this data, please <a href="{% url "contact" %}">get in touch</a>.
   </p>
@@ -100,7 +100,7 @@ <h3 id="absolute-url">The <code>absolute_url</code> Field</h3>
       <strong>$type</strong>: This is the type of object that has been returned, for example, "docket" indicates that you have gotten a docket as your result.
     </li>
     <li>
-      <strong>$id</strong>: This is a numeric ID for the document. This value increments as we add content to the system. Note that due to deletions and modifications the numeric IDs are not always sequential, but they will never be duplicated within an document type.
+      <strong>$id</strong>: This is a numeric ID for the document. This value increments as we add content to the system. Note that due to deletions and modifications the numeric IDs are not always sequential, but they will never be duplicated within a document type.
     </li>
     <li>
       <p><strong>$name-of-the-case</strong>: This is the "<a href="https://en.wikipedia.org/wiki/Slug_%28publishing%29">slug</a>" of the document, and generally mirrors its case name. This value can change if we clean up a case name, but provided it is not omitted completely, this part of the URL can be any value without affecting the page that is loaded.

From ee20194cd2463e2e4cecdbd4e25e279da70832e7 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Wed, 11 Sep 2024 10:55:09 -0700
Subject: [PATCH 05/19] Update rest-docs-vlatest.html

Removed "performance tip" number 1, per Mike's request.
---
 cl/api/templates/rest-docs-vlatest.html | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/cl/api/templates/rest-docs-vlatest.html b/cl/api/templates/rest-docs-vlatest.html
index d6e7661556..2edcc6ca66 100644
--- a/cl/api/templates/rest-docs-vlatest.html
+++ b/cl/api/templates/rest-docs-vlatest.html
@@ -380,14 +380,6 @@ <h3 id="rates">Rate Limits</h3>
     <h3 id="performance-tips">Performance Tips</h3>
     <p>A few things to consider that may increase your performance:</p>
     <ol>
-      <li>
-        <p>When doing deep crawls of the data, going to very high page numbers will incur increasingly bad performance. This is common in databases because to go to a high page number means sorting the entire data set, then counting to the correct location. Page 50 isn't a big deal. Page 2,000 starts getting slower.
-        </p>
-        <p>The fix to this solution is often to work with "slices" of the data. Instead of paginating across the whole result set, use a date field or another range-type field to only paginate over a smaller set of the data. For example, you could slice a large result set by the month of the date filing field to prevent deep pagination.
-        </p>
-        <p>Be careful to slice using a field with a normal distribution. Do not use one like <code>date_created</code>, which could have extreme spikes of activity.
-        </p>
-      </li>
       <li>
         <p>Avoid doing queries like <code>court__id=xyz</code> when you can instead do <code>court=xyz</code>. Doing queries with the extra <code>__id</code> introduces a join that can be expensive.</p>
       </li>

From 5ce1bee15d3b74214fb0f5748c320ecc50bf4472 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Wed, 11 Sep 2024 11:12:57 -0700
Subject: [PATCH 06/19] Update rest-docs-vlatest.html

---
 cl/api/templates/rest-docs-vlatest.html | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/cl/api/templates/rest-docs-vlatest.html b/cl/api/templates/rest-docs-vlatest.html
index 2edcc6ca66..74594a3116 100644
--- a/cl/api/templates/rest-docs-vlatest.html
+++ b/cl/api/templates/rest-docs-vlatest.html
@@ -360,7 +360,10 @@ <h3 id="field-selection">Field Selection</h3>
     <p>Unfortunately, this cannot be used for nested resources, though <a href="https://github.com/wimglenn/djangorestframework-queryfields/issues/8" target="_blank">there is an open issue tracking this</a>.
     </p>
 
-
+    <h3 id="pagination">Cursor-based Pagination</h3> <! -- I'm not sure what the "id" should be. -->
+    <p>Search API crawls are no longer limited to 100 pages. Deep pagination of search results is now possible. Users cannot directly jump to a specific page. Look at and follow the <code>next</code> and <code>previous</code> parameters provided in each response. Navigation of the API is exclusively through those keys in each API response.
+    </p>
+    
     <h3 id="rates">Rate Limits</h3>
     <p>Our APIs allow 5,000 queries per hour to authenticated users. Unauthenticated users are allowed 100 queries per day for experimentation.
     </p>

From e731c1f8c891b29d7b0a56924636820eba86545d Mon Sep 17 00:00:00 2001
From: Mike Lissner <mike@free.law>
Date: Wed, 11 Sep 2024 15:52:27 -0700
Subject: [PATCH 07/19] fix(docs): Fix anchor in documentation

---
 cl/api/templates/rest-docs-vlatest.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cl/api/templates/rest-docs-vlatest.html b/cl/api/templates/rest-docs-vlatest.html
index 74594a3116..81a922e3a2 100644
--- a/cl/api/templates/rest-docs-vlatest.html
+++ b/cl/api/templates/rest-docs-vlatest.html
@@ -102,7 +102,7 @@ <h2 id="overview">API Overview</h2>
     <h3 id="permissions">Permissions</h3>
     <p>Some of our APIs are only available to select users. If you need greater access to these APIs, <a href="{% url "contact" %}">please get in touch</a>.
     </p>
-    <p>All other endpoints are available according to the <a href="#limitations-throttles">throttling</a> and <a href="#authentication">authentication</a> limitations listed below.
+    <p>All other endpoints are available according to the <a href="#rates">throttling</a> and <a href="#authentication">authentication</a> limitations listed below.
     </p>
 
 

From f352a1de16ef9941d53ef5c67210b4ec75c1edd6 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Fri, 13 Sep 2024 13:16:24 -0700
Subject: [PATCH 08/19] Update case-law-api-docs-vlatest.html

Removed "count" field
---
 cl/api/templates/case-law-api-docs-vlatest.html | 1 -
 1 file changed, 1 deletion(-)

diff --git a/cl/api/templates/case-law-api-docs-vlatest.html b/cl/api/templates/case-law-api-docs-vlatest.html
index 2c0f7c53d5..9e4330162c 100644
--- a/cl/api/templates/case-law-api-docs-vlatest.html
+++ b/cl/api/templates/case-law-api-docs-vlatest.html
@@ -208,7 +208,6 @@ <h3 id="filtering-court">Filtering to Opinions in a Court</h3>
   "{% get_full_host %}{% url "opinion-list" version=version %}?cluster__docket__court=scotus"</pre>
   <p>That returns:</p>
   <pre class="pre-scrollable">{
-  "count": 521329,
   "next": "https://www.courtlistener.com/api/rest/{{ version }}/opinions/?cluster__docket__court=scotus&page=2",
   "previous": null,
   "results": [

From bd21dd0e4dc9d3164944fa9917356a0e10ae7b20 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Fri, 13 Sep 2024 13:20:23 -0700
Subject: [PATCH 09/19] Update pacer-api-docs-vlatest.html

Removed "count" fields
---
 cl/api/templates/pacer-api-docs-vlatest.html | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/cl/api/templates/pacer-api-docs-vlatest.html b/cl/api/templates/pacer-api-docs-vlatest.html
index a8b26c2ed2..7eed828e35 100644
--- a/cl/api/templates/pacer-api-docs-vlatest.html
+++ b/cl/api/templates/pacer-api-docs-vlatest.html
@@ -189,8 +189,7 @@ <h2 id="party-endpoint">Parties <small> — <code>{% url "party-list" version=ve
   "{% get_full_host %}{% url "party-list" version=version %}?docket=123"</pre>
   <p>It returns something like:</p>
   <pre class="pre-scrollable tall">{
-① "count": 35,
-  "next": "https://www.courtlistener.com/api/rest/{{ version }}/parties/?docket=123&page=2",
+① "next": "https://www.courtlistener.com/api/rest/{{ version }}/parties/?docket=123&page=2",
   "previous": null,
   "results": [
     {
@@ -267,7 +266,6 @@ <h2 id="attorney-endpoint">Attorneys <small> — <code>{% url "attorney-list" ve
   "{% get_full_host %}{% url "attorney-list" version=version %}?docket=4214664"</pre>
   <p>Returns:</p>
   <pre class="pre-scrollable tall">{
-    "count": 108,
     "next": "https://www.courtlistener.com/api/rest/{{ version }}/attorneys/?docket=4214664&page=2",
     "previous": null,
     "results": [
@@ -333,7 +331,6 @@ <h2 id="recap-query">Fast Document Lookup <small> — <code>{% url "fast-recapdo
   </pre>
   <p>This will return one entry for each document found, up to a maximum of 300 items:</p>
   <pre class="pre-scrollable tall">{
-  "count": 2,
   "next": null,
   "previous": null,
   "results": [

From 9c5ffdf97a4009a6a7ba550b800d6476b9d0fa33 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Fri, 13 Sep 2024 13:22:41 -0700
Subject: [PATCH 10/19] Update financial-disclosure-api-docs-vlatest.html

Removed "count" field
---
 cl/api/templates/financial-disclosure-api-docs-vlatest.html | 1 -
 1 file changed, 1 deletion(-)

diff --git a/cl/api/templates/financial-disclosure-api-docs-vlatest.html b/cl/api/templates/financial-disclosure-api-docs-vlatest.html
index 8be48f59ab..fa2f538168 100644
--- a/cl/api/templates/financial-disclosure-api-docs-vlatest.html
+++ b/cl/api/templates/financial-disclosure-api-docs-vlatest.html
@@ -184,7 +184,6 @@ <h3 id="redactions">Redactions</h3>
   <pre class="pre-scrollable tall">curl "{% get_full_host %}{% url "investment-list" version=version %}?redacted=True" \
   --header 'Authorization: Token {% if user.is_authenticated %}{{ user.auth_token }}{% else %}&lt;your-token-here&gt;{% endif %}'
 {
-  "count": 27404,
   "next": "https://www.courtlistener.com/api/rest/{{ version }}/investments/?page=2&redacted=True",
   "previous": null,
   "results": [

From 5dd809afb2d8732ba186ab080dedfe1a97f5b120 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Fri, 13 Sep 2024 15:34:06 -0700
Subject: [PATCH 11/19] Update search-api-docs-vlatest.html

---
 cl/api/templates/search-api-docs-vlatest.html | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/cl/api/templates/search-api-docs-vlatest.html b/cl/api/templates/search-api-docs-vlatest.html
index 87f0cef413..075a587639 100644
--- a/cl/api/templates/search-api-docs-vlatest.html
+++ b/cl/api/templates/search-api-docs-vlatest.html
@@ -152,6 +152,10 @@ <h3 id="type">Setting the Result <code>type</code></h3>
     </tr>
     <tr>
       <td><code>r</code></td>
+      <td>List of Federal cases (dockets) with up to three nested documents. If there are more than three matching documents, the <code>more_docs</code> field for the docket result will be </code>true</code>.</td>
+    </tr>
+    <tr>
+      <td><code>rd</code></td>
       <td>Federal filing documents from PACER</td>
     </tr>
     <tr>
@@ -178,6 +182,8 @@ <h3 id="type">Setting the Result <code>type</code></h3>
   <h3 id="ordering">Ordering Results</h3>
   <p>Each search <code>type</code> can be sorted by certain fields. These are available on the front end in the ordering drop down, which sets the <code>order_by</code> parameter.
   </p>
+  <p>If your sorting field has null values, those results will be sorted at the end of the query, regardless of whether you sort in ascending or descending order. For example if you sort by a date that is null for an opinion, that opinion will go at the end of the result set.
+  </p>
 
 
   <h3 id="filtering">Filtering Results</h3>
@@ -225,7 +231,19 @@ <h3 id="notes">Special Notes</h3>
       </p>
       <p>This field only responds to arguments provided to the <code>q</code> parameter.  If the <code>q</code> parameter is not used, the <code>snippet</code> field will show the first 500 characters of the <code>text</code> field.
       </p>
+      <p>This field only displays Opinion text content.
+      </p>
     </li>
+    <li>
+      <p>To enhance performance, results are not highlighted by default. To enable highlighting, include <code>highlight=on</code> in your request.
+      </p>
+      <p>When highlighting is disabled, the first 500 characters of snippet fields are returned for fields <code>o</code>, <code>r</code>, and <code>rd</code>. 
+      </p>
+    </li>
+     <li>
+      <p><code>type=d</code> and <code>type=r</code> use cardinality aggregation to compute the result count, which has an error of ±6% if results are over 2000.
+      </p>
+     </li>
   </ol>
 
 

From 439830831556120ee8e604f1afa92a90c360ee2e Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Mon, 16 Sep 2024 13:34:25 -0700
Subject: [PATCH 12/19] Update search-api-docs-vlatest.html

Added results from https://www.courtlistener.com/api/rest/v4/search/?q=foo
---
 cl/api/templates/search-api-docs-vlatest.html | 125 +++++++++---------
 1 file changed, 63 insertions(+), 62 deletions(-)

diff --git a/cl/api/templates/search-api-docs-vlatest.html b/cl/api/templates/search-api-docs-vlatest.html
index 075a587639..25c9ebbb59 100644
--- a/cl/api/templates/search-api-docs-vlatest.html
+++ b/cl/api/templates/search-api-docs-vlatest.html
@@ -63,68 +63,69 @@ <h2 id="usage">Basic Usage</h2>
   '{% get_full_host %}{% url "search-list" version=version %}?q=foo'</pre>
   <p>That returns:</p>
   <pre class="pre-scrollable tall">{
-  "count": 2369,
-  "next": "https://www.courtlistener.com/api/rest/{{ version }}/search/?page=2&q=foo",
-  "previous": null,
-  "results": [
-    {
-      "absolute_url": "/opinion/106359/fong-foo-v-united-states/",
-      "attorney": "Arthur Richenthal argued the causes for petitioners and filed briefs for petitioner in No. 65. David E. Feller filed briefs for petitioners in No. 64., Solicitor General Cox argued the causes for the United States. With him on the briefs were Assistant Attorney General Miller, Stephen J. Poliak, Beatrice Rosenberg, Philip R. Monahan and J. F. Bishop.",
-      "author_id": null,
-      "caseName": "Fong Foo v. United States",
-      "caseNameShort": "Fong Foo",
-      "citation": [
-        "7 L. Ed. 2d 629",
-        "82 S. Ct. 671",
-        "369 U.S. 141",
-        "1962 U.S. LEXIS 1600"
-      ],
-      "citeCount": 357,
-      "cites": [
-        94515,
-        98794,
-        100989,
-        101974,
-        106273,
-        253004
-      ],
-      "cluster_id": 106359,
-      "court": "Supreme Court of the United States",
-      "court_citation_string": "SCOTUS",
-      "court_exact": "scotus",
-      "court_id": "scotus",
-      "dateArgued": null,
-      "dateFiled": "1962-03-19T00:00:00-08:00",
-      "dateReargued": null,
-      "dateReargumentDenied": null,
-      "docketNumber": "64",
-      "docket_id": 1153854,
-      "download_url": null,
-      "id": 106359,
-      "joined_by_ids": null,
-      "judge": "Harlan, Clark, Whittaker",
-      "lexisCite": "1962 U.S. LEXIS 1600",
-      "local_path": null,
-      "neutralCite": null,
-      "non_participating_judge_ids": null,
-      "pagerank": null,
-      "panel_ids": null,
-      "per_curiam": null,
-      "scdb_id": "1961-048",
-      "sibling_ids": [
-        106359,
-        9422362,
-        9422363,
-        9422364
-      ],
-      "snippet": "\n\n\n    \n369 U.S. 141 (1962)\nFONG <mark>FOO</mark> ET AL.\nv.\nUNITED STATES.\nNo. 64.\nSupreme Court of United States.&hellip;Court of the United States\nscotus\nSCOTUS\n\n\n\n    FONG <mark>FOO</mark> Et Al. v. UNITED STATES\n\n\nHarlan, Clark, Whittaker",
-      "source": "LRU",
-      "status": "Precedential",
-      "status_exact": "Precedential",
-      "suitNature": "",
-      "timestamp": "2024-03-01T14:12:07.892000-08:00",
-      "type": "010combined"
-    },
+  "count": 2343,
+    "next": "https://www.courtlistener.com/api/rest/v4/search/?cursor=cz0yMzUuODcxMjUmcz04MDUzNTUzJnQ9byZkPTIwMjQtMDktMTY%3D&q=foo",
+    "previous": null,
+    "results": [
+        {
+            "absolute_url": "/opinion/6613686/foo-v-foo/",
+            "attorney": "",
+            "caseName": "Foo v. Foo",
+            "caseNameFull": "Foo v. Foo",
+            "citation": [
+                "101 Haw. 235",
+                "65 P.3d 182"
+            ],
+            "citeCount": 0,
+            "cluster_id": 6613686,
+            "court": "Hawaii Intermediate Court of Appeals",
+            "court_citation_string": "Haw. App.",
+            "court_id": "hawapp",
+            "dateArgued": null,
+            "dateFiled": "2003-01-10",
+            "dateReargued": null,
+            "dateReargumentDenied": null,
+            "docketNumber": "24158",
+            "docket_id": 63544014,
+            "judge": "",
+            "lexisCite": "",
+            "meta": {
+                "timestamp": "2024-06-22T10:26:35.320787Z",
+                "date_created": "2022-06-26T23:24:18.926040Z"
+            },
+            "neutralCite": "",
+            "non_participating_judge_ids": [],
+            "opinions": [
+                {
+                    "author_id": null,
+                    "cites": [],
+                    "download_url": null,
+                    "id": 6489975,
+                    "joined_by_ids": [],
+                    "local_path": null,
+                    "meta": {
+                        "timestamp": "2024-06-24T21:14:41.408206Z",
+                        "date_created": "2022-06-26T23:24:18.931912Z"
+                    },
+                    "per_curiam": false,
+                    "sha1": "",
+                    "snippet": "\nAffirmed in part, reversed in part, vacated and remanded\n",
+                    "type": "lead-opinion"
+                }
+            ],
+            "panel_ids": [],
+            "panel_names": [],
+            "posture": "",
+            "procedural_history": "",
+            "scdb_id": "",
+            "sibling_ids": [
+                6489975
+            ],
+            "source": "U",
+            "status": "Published",
+            "suitNature": "",
+            "syllabus": ""
+        },
     ...</pre>
   <p>That's the simple version. Read on to learn the rest.</p>
 

From 21b58a5bb911d6ae4d43688aaecf8fa168ea2571 Mon Sep 17 00:00:00 2001
From: s-taube <177274951+s-taube@users.noreply.github.com>
Date: Tue, 17 Sep 2024 14:21:49 -0700
Subject: [PATCH 13/19] Update rest-docs-vlatest.html

---
 cl/api/templates/rest-docs-vlatest.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/cl/api/templates/rest-docs-vlatest.html b/cl/api/templates/rest-docs-vlatest.html
index 81a922e3a2..41241500bd 100644
--- a/cl/api/templates/rest-docs-vlatest.html
+++ b/cl/api/templates/rest-docs-vlatest.html
@@ -29,6 +29,8 @@ <h1 id="about">REST API &ndash; v4.0</h1>
 
     <p class="lead">APIs for developers and researchers that need granular legal data.
     </p>
+    <p class="alert alert-warning"><i class="fa fa-warning"></i> <strong>Update!</strong> V4 of the API is now live! We encourage you to use the latest version. You can view information on previous versions of the API <a href="{% url "rest_change_log" %}">here</a>.
+    </p>
     <p>After more than a decade of development, these APIs are powerful. Our <a href="{% url "case_law_api_help" %}">case law API</a> was the first. Our <a href="{% url "pacer_api_help" %}">PACER</a> and <a href="{% url "oral_argument_api_help" %}">oral argument</a> APIs are the biggest. Our <a href="{% url "webhooks_getting_started" %}">webhooks</a> push data to you. Our <a href="{% url "citation_lookup_api" %}">citation lookup tool</a> can fight hallucinations in AI tools.
     </p>
     <p>Let's get started. To see and browse all the API URLs, click the button below:

From 6ad4278afb0993f9ba80eb67665a17d65ab5527c Mon Sep 17 00:00:00 2001
From: Alberto Islas <albertisfu@gmail.com>
Date: Wed, 18 Sep 2024 09:47:46 -0500
Subject: [PATCH 14/19] fix(docs): Added deprecation alert to V3 docs page

---
 cl/api/templates/rest-docs-v3.html | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/cl/api/templates/rest-docs-v3.html b/cl/api/templates/rest-docs-v3.html
index fdf13b7d40..c021f14752 100644
--- a/cl/api/templates/rest-docs-v3.html
+++ b/cl/api/templates/rest-docs-v3.html
@@ -25,6 +25,13 @@ <h4 class="v-offset-below-2">
     {% include "includes/toc_sidebar.html" %}
   </div>
   <div class="col-xs-12 col-md-8 col-lg-6">
+    <div class="alert-danger alert">
+      <p class="bottom">These notes are for a version of the API that has
+          been deprecated and will soon be disabled completely. Please use
+          the <a href="{% url "rest_docs" %}">latest version</a>, as
+          these notes are only maintained to help with migrations.
+      </p>
+    </div>
     <h1 id="about">REST API &ndash; v3.15</h1>
 
     <p class="lead">APIs for developers and researchers that need granular legal data.

From da352693c124d22b35ea8a493b447653a17638a1 Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Wed, 18 Sep 2024 14:52:57 +0000
Subject: [PATCH 15/19] [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci
---
 cl/api/templates/rest-docs-vlatest.html       | 2 +-
 cl/api/templates/search-api-docs-vlatest.html | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/cl/api/templates/rest-docs-vlatest.html b/cl/api/templates/rest-docs-vlatest.html
index 41241500bd..fc761f8374 100644
--- a/cl/api/templates/rest-docs-vlatest.html
+++ b/cl/api/templates/rest-docs-vlatest.html
@@ -365,7 +365,7 @@ <h3 id="field-selection">Field Selection</h3>
     <h3 id="pagination">Cursor-based Pagination</h3> <! -- I'm not sure what the "id" should be. -->
     <p>Search API crawls are no longer limited to 100 pages. Deep pagination of search results is now possible. Users cannot directly jump to a specific page. Look at and follow the <code>next</code> and <code>previous</code> parameters provided in each response. Navigation of the API is exclusively through those keys in each API response.
     </p>
-    
+
     <h3 id="rates">Rate Limits</h3>
     <p>Our APIs allow 5,000 queries per hour to authenticated users. Unauthenticated users are allowed 100 queries per day for experimentation.
     </p>
diff --git a/cl/api/templates/search-api-docs-vlatest.html b/cl/api/templates/search-api-docs-vlatest.html
index 25c9ebbb59..4923378c89 100644
--- a/cl/api/templates/search-api-docs-vlatest.html
+++ b/cl/api/templates/search-api-docs-vlatest.html
@@ -238,7 +238,7 @@ <h3 id="notes">Special Notes</h3>
     <li>
       <p>To enhance performance, results are not highlighted by default. To enable highlighting, include <code>highlight=on</code> in your request.
       </p>
-      <p>When highlighting is disabled, the first 500 characters of snippet fields are returned for fields <code>o</code>, <code>r</code>, and <code>rd</code>. 
+      <p>When highlighting is disabled, the first 500 characters of snippet fields are returned for fields <code>o</code>, <code>r</code>, and <code>rd</code>.
       </p>
     </li>
      <li>

From 93c956b9409f44b14cff7913f94fde823266e860 Mon Sep 17 00:00:00 2001
From: Alberto Islas <albertisfu@gmail.com>
Date: Wed, 18 Sep 2024 12:20:53 -0500
Subject: [PATCH 16/19] fix(docs): Updated deprecation alert on V3 docs page

---
 cl/api/templates/rest-docs-v3.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/cl/api/templates/rest-docs-v3.html b/cl/api/templates/rest-docs-v3.html
index c021f14752..ffca3cd83f 100644
--- a/cl/api/templates/rest-docs-v3.html
+++ b/cl/api/templates/rest-docs-v3.html
@@ -26,10 +26,10 @@ <h4 class="v-offset-below-2">
   </div>
   <div class="col-xs-12 col-md-8 col-lg-6">
     <div class="alert-danger alert">
-      <p class="bottom">These notes are for a version of the API that has
-          been deprecated and will soon be disabled completely. Please use
-          the <a href="{% url "rest_docs" %}">latest version</a>, as
-          these notes are only maintained to help with migrations.
+      <p class="bottom">These notes are for a version of the API that is deprecated.
+        New implementations should use the <a href="{% url "rest_docs" %}">latest version of the API</a>
+        and existing software <a href="{% url "rest_docs" %}">should be upgraded</a>.
+        These notes are maintained to help with migrations.
       </p>
     </div>
     <h1 id="about">REST API &ndash; v3.15</h1>

From 975845d868f9fef65dbcb77bbef0b9919661cbb1 Mon Sep 17 00:00:00 2001
From: Alberto Islas <albertisfu@gmail.com>
Date: Wed, 18 Sep 2024 15:05:01 -0500
Subject: [PATCH 17/19] fix(docs): Added V4 API Migration Guide view

---
 cl/api/templates/migration-docs.html | 40 ++++++++++++++++++++++++++++
 cl/api/templates/rest-docs-v3.html   |  2 +-
 cl/api/urls.py                       |  9 +++++++
 3 files changed, 50 insertions(+), 1 deletion(-)
 create mode 100644 cl/api/templates/migration-docs.html

diff --git a/cl/api/templates/migration-docs.html b/cl/api/templates/migration-docs.html
new file mode 100644
index 0000000000..f8787c8500
--- /dev/null
+++ b/cl/api/templates/migration-docs.html
@@ -0,0 +1,40 @@
+{% extends "base.html" %}
+{% load static %}
+{% load extras %}
+
+{% block title %}V4 API Migration Guide &ndash; CourtListener.com{% endblock %}
+{% block description %}
+{% endblock %}
+
+{% block sidebar %}{% endblock %}
+
+{% block footer-scripts %}
+  {% include "includes/anchors.html" %}
+{% endblock %}
+
+{% block content %}
+<div class="col-xs-12 hidden-md hidden-lg">
+  <h4 class="v-offset-below-2">
+    <i class="fa fa-arrow-circle-o-left gray"></i>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
+  </h4>
+</div>
+
+<div id="toc-container" class="hidden-xs hidden-sm col-md-3">
+  <h4 class="v-offset-below-3">
+    <i class="fa fa-arrow-circle-o-left gray"></i>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
+  </h4>
+  <div id="toc">
+    <h3>Table of Contents</h3>
+    <ul>
+      <li></li>
+    </ul>
+  </div>
+</div>
+
+<div class="col-xs-12 col-md-8 col-lg-6">
+  <h1 id="about">V4 API Migration Guide</h1>
+
+</div>
+{% endblock %}
diff --git a/cl/api/templates/rest-docs-v3.html b/cl/api/templates/rest-docs-v3.html
index ffca3cd83f..d42e218e46 100644
--- a/cl/api/templates/rest-docs-v3.html
+++ b/cl/api/templates/rest-docs-v3.html
@@ -28,7 +28,7 @@ <h4 class="v-offset-below-2">
     <div class="alert-danger alert">
       <p class="bottom">These notes are for a version of the API that is deprecated.
         New implementations should use the <a href="{% url "rest_docs" %}">latest version of the API</a>
-        and existing software <a href="{% url "rest_docs" %}">should be upgraded</a>.
+        and existing software <a href="{% url "migration_docs" %}">should be upgraded</a>.
         These notes are maintained to help with migrations.
       </p>
     </div>
diff --git a/cl/api/urls.py b/cl/api/urls.py
index 64989ab4e4..54b21600be 100644
--- a/cl/api/urls.py
+++ b/cl/api/urls.py
@@ -367,4 +367,13 @@
         "api/replication/",
         RedirectView.as_view(pattern_name="replication_docs", permanent=True),
     ),
+    # V4 Migration guide
+    path(
+        "help/api/migration-docs/",
+        TemplateView.as_view(
+            template_name="migration-docs.html",
+            extra_context={"private": False},
+        ),
+        name="migration_docs",
+    ),
 ]

From 61e96ee4bda5625e3e28dced2cc6cb74c11fc7c1 Mon Sep 17 00:00:00 2001
From: Alberto Islas <albertisfu@gmail.com>
Date: Thu, 19 Sep 2024 15:38:45 -0500
Subject: [PATCH 18/19] fix(docs): Added V4 API Migration Guide HTML

---
 .../includes/toc_migration_guide_sidebar.html |  83 ++++
 cl/api/templates/migration-docs.html          |  40 --
 cl/api/templates/migration-guide.html         | 445 ++++++++++++++++++
 cl/api/templates/rest-docs-v3.html            |   2 +-
 cl/api/urls.py                                |   6 +-
 5 files changed, 532 insertions(+), 44 deletions(-)
 create mode 100644 cl/api/templates/includes/toc_migration_guide_sidebar.html
 delete mode 100644 cl/api/templates/migration-docs.html
 create mode 100644 cl/api/templates/migration-guide.html

diff --git a/cl/api/templates/includes/toc_migration_guide_sidebar.html b/cl/api/templates/includes/toc_migration_guide_sidebar.html
new file mode 100644
index 0000000000..49de496a6d
--- /dev/null
+++ b/cl/api/templates/includes/toc_migration_guide_sidebar.html
@@ -0,0 +1,83 @@
+<div id="toc">
+    <h3>Table of Contents</h3>
+    <ul>
+      <li><a href="#whats-happening">What's Happening?</a></li>
+      <li><a href="#timeline-changes">Timeline for Changes</a></li>
+      <li><a href="#what-if-do-nothing">What If I Do Nothing?</a></li>
+      <li><a href="#what-to-expect">What New Features Can I Expect?</a>
+        <a class="collapse-header" data-toggle="collapse" href="#collapseWhatToExpect" role="button"
+          aria-expanded="false" aria-controls="collapseWhatToExpect">
+          [+]
+        </a>
+      </li>
+      <ul class="collapse" id="collapseWhatToExpect">
+        <li><a href="#cursor-pagination">Cursor-based pagination</a></li>
+        <li><a href="#elasticsearch">ElasticSearch</a></li>
+      </ul>
+      <li><a href="#breaking-changes">Breaking Changes to v3 of the Search API</a>
+        <a class="collapse-header" data-toggle="collapse" href="#collapseV3Breaking" role="button"
+          aria-expanded="false" aria-controls="collapseV3Breaking">
+          [+]
+        </a>
+      </li>
+      <ul class="collapse" id="collapseV3Breaking">
+        <li><a href="#recap-breaking-changes">RECAP (type=r)</a></li>
+        <li><a href="#opinions-breaking-changes">Opinions (type=o)</a></li>
+        <li><a href="#oa-breaking-changes">Oral Arguments (type=oa)</a></li>
+        <li><a href="#people-breaking-changes">People</a></li>
+      </ul>
+      <li><a href="#migrate-db-apis">How Do I Migrate Database APIs?</a>
+        <a class="collapse-header" data-toggle="collapse" href="#collapseMigrateDBAPIS" role="button"
+          aria-expanded="false" aria-controls="collapseMigrateDBAPIS">
+          [+]
+        </a>
+      </li>
+      <ul class="collapse" id="collapseMigrateDBAPIS">
+        <li><a href="#total-count-results">Total count of results</a></li>
+        <li><a href="#invalid-cursor">Invalid cursor error code: 404</a></li>
+      </ul>
+      <li><a href="#migrate-search-apis">How Do I Migrate the Search API?</a>
+        <a class="collapse-header" data-toggle="collapse" href="#collapseMigrateSearchAPIS" role="button"
+          aria-expanded="false" aria-controls="collapseMigrateSearchAPIS">
+          [+]
+        </a>
+      </li>
+      <ul class="collapse" id="collapseMigrateSearchAPIS">
+        <li><a href="#enhancements-v4">Enhancements in v4</a>
+          <a class="collapse-header" data-toggle="collapse" href="#collapseEnhancementsV4" role="button"
+            aria-expanded="false" aria-controls="collapseEnhancementsV4">
+            [+]
+          </a>
+        </li>
+        <ul class="collapse" id="collapseEnhancementsV4">
+          <li><a href="#enhancements-cursor-pagination">Search API crawls are no longer limited to 100 pages</a></li>
+          <li><a href="#enhancements-results-sorting">Result sorting is more consistent</a></li>
+          <li><a href="#enhancements-highlighting">Highlighting is more consistent</a></li>
+          <li><a href="#enhancements-empty-fields">Empty fields are standardized</a></li>
+        </ul>
+        <li><a href="#v4-backwards-incompatible-changes">Backwards incompatible changes in v4</a>
+          <a class="collapse-header" data-toggle="collapse" href="#collapseIncompatibleChangesV4" role="button"
+            aria-expanded="false" aria-controls="collapseIncompatibleChangesV4">
+            [+]
+          </a>
+        </li>
+        <ul class="collapse" id="collapseIncompatibleChangesV4">
+          <li><a href="#backwards-estimated-counts">High query counts are estimated</a></li>
+          <li><a href="#backwards-highlighting">Highlighting</a></li>
+          <li><a href="#backwards-nested-keys">Nested keys (documents) for type=o and type=p</a></li>
+          <li><a href="#backwards-type-r">type=r is now for dockets with nested documents</a></li>
+          <li><a href="#backwards-type-rd">type=rd is a new result type for documents</a></li>
+          <li><a href="#backwards-type-d">type=d still returns dockets</a></li>
+          <li><a href="#backwards-removed-fields">Removed fields</a></li>
+          <li><a href="#backwards-changed-fields">Changed field values</a></li>
+          <li><a href="#backwards-date-times">Dates and times</a></li>
+          <li><a href="#backwards-no-random-sorting">No more random sorting</a></li>
+          <li><a href="#backwards-stemming-synonyms">Stemming and Synonyms</a></li>
+          <li><a href="#backwards-get-params">Changes to GET parameters</a></li>
+          <li><a href="#backwards-400-error">Bad Request Error Code: 400</a></li>
+          <li><a href="#backwards-500-error">Server Error Code: 500</a></li>
+          <li><a href="#backwards-404-error">Not Found Error Code: 404</a></li>
+        </ul>
+      </ul>
+    </ul>
+  </div>
diff --git a/cl/api/templates/migration-docs.html b/cl/api/templates/migration-docs.html
deleted file mode 100644
index f8787c8500..0000000000
--- a/cl/api/templates/migration-docs.html
+++ /dev/null
@@ -1,40 +0,0 @@
-{% extends "base.html" %}
-{% load static %}
-{% load extras %}
-
-{% block title %}V4 API Migration Guide &ndash; CourtListener.com{% endblock %}
-{% block description %}
-{% endblock %}
-
-{% block sidebar %}{% endblock %}
-
-{% block footer-scripts %}
-  {% include "includes/anchors.html" %}
-{% endblock %}
-
-{% block content %}
-<div class="col-xs-12 hidden-md hidden-lg">
-  <h4 class="v-offset-below-2">
-    <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
-  </h4>
-</div>
-
-<div id="toc-container" class="hidden-xs hidden-sm col-md-3">
-  <h4 class="v-offset-below-3">
-    <i class="fa fa-arrow-circle-o-left gray"></i>
-    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
-  </h4>
-  <div id="toc">
-    <h3>Table of Contents</h3>
-    <ul>
-      <li></li>
-    </ul>
-  </div>
-</div>
-
-<div class="col-xs-12 col-md-8 col-lg-6">
-  <h1 id="about">V4 API Migration Guide</h1>
-
-</div>
-{% endblock %}
diff --git a/cl/api/templates/migration-guide.html b/cl/api/templates/migration-guide.html
new file mode 100644
index 0000000000..bed64e6961
--- /dev/null
+++ b/cl/api/templates/migration-guide.html
@@ -0,0 +1,445 @@
+{% extends "base.html" %}
+{% load static %}
+{% load extras %}
+
+{% block title %}V4 API Migration Guide &ndash; CourtListener.com{% endblock %}
+{% block description %}
+{% endblock %}
+
+{% block sidebar %}{% endblock %}
+
+{% block footer-scripts %}
+  {% include "includes/anchors.html" %}
+{% endblock %}
+
+{% block content %}
+<div class="col-xs-12 hidden-md hidden-lg">
+  <h4 class="v-offset-below-2">
+    <i class="fa fa-arrow-circle-o-left gray"></i>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
+  </h4>
+</div>
+
+<div id="toc-container" class="hidden-xs hidden-sm col-md-3">
+  <h4 class="v-offset-below-3">
+    <i class="fa fa-arrow-circle-o-left gray"></i>
+    <a href="{% url "rest_docs" version=version %}">Back to API Docs</a>
+  </h4>
+  {% include "includes/toc_migration_guide_sidebar.html" %}
+</div>
+
+<div class="col-xs-12 col-md-8 col-lg-6">
+  <h1 id="about">V4 API Migration Guide</h1>
+  <h2 id="whats-happening">What's Happening?</h2>
+  <p>
+    After several years of planning and development, we have released v4 of our APIs. In conjunction with this migration,
+    we are replacing our Solr search engine with an ElasticSearch cluster. v4 of the API responds to feedback we
+    have received over the years, and should be much better for our users — faster, more featureful, more scalable, and more accurate.
+  </p>
+  <p>
+    Unfortunately, we couldn't make these new APIs completely backwards compatible, so this guide explains the changes
+    in the new APIs and what it will take to migrate to them.
+  </p>
+  <h2 id="timeline-changes">Timeline for Changes</h2>
+  <p>v4 of the API is available now and is the default version for anybody creating new systems. Before its full release, a number of organizations beta tested it.
+  </p>
+  <p>
+    All of our APIs except for our search API are powered by our database. We do not have plans at present to deprecate
+    any of these APIs, but we'd like to remove them someday and urge you to migrate to v4 as soon as possible so we can do that.
+  </p>
+  <p>
+    That said, the v3 Search API is currently powered by Solr. v4 is powered by ElasticSearch. In <strong>nine weeks</strong>, we aim to switch v3 so it uses ElasticSearch too.
+    This will change v3 in small backwards incompatible ways, but will allow us to continue supporting it even after turning off our Solr server.
+  </p>
+  <p>
+    If you are a v3 Search API user, you will soon get an email from us to communicate and discuss timelines.
+  </p>
+  <h2 id="what-if-do-nothing">What If I Do Nothing?</h2>
+  <p>
+    You might be fine. Most of the database and search APIs are only changing slightly and v3 will be supported for some period of time.
+    But you should read this guide to see if any changes are needed to your application.
+  </p>
+  <p>The remainder of this guide is in three section:</p>
+  <ul>
+    <li>New features you can expect</li>
+    <li>How to migrate database APIs</li>
+    <li>How to migrate search APIs</li>
+  </ul>
+  <p>
+    We're very excited to be releasing v4 of our APIs. We hope you will review these changes so we can all have a smooth transition.
+  </p>
+  <h2 id="what-to-expect">What New Features Can I Expect?</h2>
+  <h3 id="cursor-pagination">Cursor-based pagination</h3>
+  <p>Our database-powered APIs now support cursor-based pagination. This allows you to crawl very deeply in the API. In v3, any page past 100 was blocked.
+  </p>
+  <h3 id="elasticsearch">ElasticSearch</h3>
+  <p>v4 of the Search API is powered by ElasticSearch instead of Solr. This is a huge upgrade to our API and search engine.
+  </p>
+  <p>Some of the improvements include:</p>
+  <ul>
+    <li>In v4, all PACER cases are now searchable. In v3 you only got results if a case had a docket entry.
+    </li>
+    <li>You can search for PACER filings based on what decisions they cite.
+    </li>
+    <li>You can now search for exact words like "Deposit" and not get back results for things like "Deposition."
+    </li>
+    <li>We've added about 800 legal acronyms like "IRS" to make sure those bring back results.
+    </li>
+    <li>Better relevancy for edge cases:
+    </li>
+    <ul>
+      <li>Small words like "of," "to," and "the" are now searchable.</li>
+      <li>Camelcase words like "McDonalds" are more searchable.</li>
+      <li>Highlighting is more consistent and can be disabled for better performance.</li>
+    </ul>
+    <li>Emojis and unicode characters are now searchable.</li>
+    <li>Docket number and other fielded searches are more robust.</li>
+    <li>Timezone handling is more consistent.</li>
+    <li>We've added a number of new searchable fields.
+ </li>
+  </ul>
+  <p>For more details please<a href="https://free.law/2024/01/18/new-recap-archive-search-is-live/" target="_blank"> see our blog</a>.</p>
+  <h2 id="breaking-changes">Breaking Changes to v3 of the Search API</h2>
+  <p>We cannot continue running Solr forever, but we can do our best to support v3 of the API. To do this, on <strong>XXXDATEXXX</strong>,
+    v3 of the Search API will be upgraded to use Elastic behind the scenes. This will cause some breaking changes.
+    If you have not migrated to v4 when we make this swap, these are the breaking changes you should prepare for:
+  </p>
+  <h3 id="recap-breaking-changes">RECAP (type=r)</h3>
+  <ul>
+    <li>Fields removed:</li>
+    <ul>
+      <li>attorney</li>
+      <li>attorney_id</li>
+      <li>firm</li>
+      <li>firm_id</li>
+      <li>party</li>
+      <li>party_id</li>
+      <li>docket_absolute_url</li>
+    </ul>
+  </ul>
+  <ul>
+    <li>Fielded text queries that includes party fields won't work, for instance:
+      <p><code>firm_id:1245 AND party:(United States)</code></p>
+    </li>
+  </ul>
+  <ul>
+      <li>The <code>type=d</code> uses a cardinality aggregation to compute the result count, which has an error of ±6% if results are over 2000.
+      </li>
+  </ul>
+  <h3 id="opinions-breaking-changes">Opinions (type=o)</h3>
+  <ul>
+      <li>Fields removed:</li>
+      <ul>
+        <li>caseNameShort</li>
+        <li>pagerank</li>
+        <li>status_exact</li>
+        <li>non_participating_judge_ids</li>
+        <li>source</li>
+      </ul>
+      <li>Field added:</li>
+      <ul>
+        <li>date_created</li>
+      </ul>
+      <li><code>snippet</code> has changed. In the Solr version, it included content from all fields, while in ES it displays only the Opinion text content.
+      </li>
+      <li>The <code>type=o</code> uses a cardinality aggregation to compute the result count, which has an error of ±6% if results are over 2000 hits.
+      </li>
+  </ul>
+  <h3 id="oa-breaking-changes">Oral Arguments (type=oa)</h3>
+  <ul>
+    <li>In this case, the API response will be fully compatible with the Solr version.</li>
+    <li>The only change is in the content of the <code>snippet</code> field, which previously stored different audio fields in Solr. Now, it stores the audio transcription.
+    </li>
+  </ul>
+  <h3 id="people-breaking-changes">People</h3>
+  <ul>
+    <li>No breaking changes. V3 is currently working on ES.</li>
+  </ul>
+  <h2 id="migrate-db-apis">How Do I Migrate Database APIs?</h2>
+  <h3 id="total-count-results">Total count of results</h3>
+  <ul>
+    <li>The total count of the results is no longer available in the response.
+      Most users don't need this when crawling the API, and computing the count for each response slows down the API.
+      If this value is essential to your service, let us know so we can discuss adding a new API with this feature.
+    </li>
+  </ul>
+  <h3 id="invalid-cursor">Invalid cursor error code: 404</h3>
+  <ul>
+    <li>A new type of error found in the V4 API is <strong>Invalid cursor</strong> with a 404 status code.</li>
+    <li>This error can occur if a user starts a request using one sorting key, then switches to a different one without clearing the cursor from the parameters.
+      For example:
+      <p>First request: <code>/api/rest/v4/dockets/?cursor=cD0yMDI0LTA4LTA5KzE4JTNBMTMlM0E1Ny4xODQ0MjUlMkIwMCUzQTAw&amp;order_by=date_created</code>
+      </p>
+      <p>Second request: <code>/api/rest/v4/dockets/?cursor=cD0yMDI0LTA4LTA5KzE4JTNBMTMlM0E1Ny4xODQ0MjUlMkIwMCUzQTAw&amp;order_by=id</code>
+      </p>
+    </li>
+    <li>The reason for this error is that cursor pagination maintains the original sorting key type for consistency.
+      If the new key type does not match the one stored in the cursor, the error is triggered.
+    </li>
+    <li>Additionally, if a user starts pagination with a key that supports cursor pagination and then switches to one that doesn't, the cursor parameter in the request will be ignored, and the new request will start from page 1.
+      Similarly, if the user begins with a non-cursor key and switches to one that supports CBP, the <code>page</code> parameter will be ignored, and the request will restart from page 1.
+    </li>
+  </ul>
+  <h2 id="migrate-search-apis">How Do I Migrate the Search API?</h2>
+  <h3 id="enhancements-v4">Enhancements in v4</h3>
+  <h4 id="enhancements-cursor-pagination">Search API crawls are no longer limited to 100 pages</h4>
+  <ul>
+    <li>Deep pagination of search results is now possible.</li>
+    <li>Users cannot directly jump to a specific page. Look at and follow the <code>next</code> and <code>previous</code> parameters provided in each response. Navigation of the API is exclusively through those keys in each API response.
+    </li>
+  </ul>
+  <h4 id="enhancements-results-sorting">Result sorting is more consistent</h4>
+  <ul>
+    <li>When sorting the API results, we now add a tie-breaking field to all responses. This ensures that ordering is consistent even when the ordering key has identical values for multiple results.
+    </li>
+    <li>If your sorting field has null values, those results will be sorted at the end of the query, regardless of whether you sort in ascending or descending order.
+      For example if you sort by a date that is null for an opinion, that opinion will go at the end of the result set.
+    </li>
+  </ul>
+  <h4 id="enhancements-highlighting">Highlighting is more consistent</h4>
+  <ul>
+    <li>When enabled, highlighting will more consistently highlight the fields in the response.</li>
+  </ul>
+  <h4 id="enhancements-empty-fields">Empty fields are standardized</h4>
+  <ul>
+      <li>Empty fields are now more consistent in their response types, and follow the conventions provided by Django.
+        This means that dates, date times, and integers return <code>null</code>, strings return an empty string, and lists return an empty array.
+      </li>
+  </ul>
+  <h3 id="v4-backwards-incompatible-changes">Backwards incompatible changes in v4</h3>
+  <h4 id="backwards-estimated-counts">High query counts are estimated</h4>
+  <ul>
+    <li>To enhance performance, query counts above 2,000 hits are approximate.
+      For those exceeding this threshold, counts can be off by as much as six percent.
+      We recommend noting this in your interface by saying something like, "About 5,000 results," instead of presenting the value as exact.
+    </li>
+  </ul>
+  <h4 id="backwards-highlighting">Highlighting</h4>
+  <ul>
+    <li>To enhance performance, results are not highlighted by default. To enable highlighting, include <code>highlight=on</code> in your request.
+    </li>
+    <li>When highlighting is disabled, the first 500 characters of <code>snippet</code> fields are returned for types <code>o</code>, <code>r</code>, and <code>rd</code>.
+    </li>
+  </ul>
+  <h4 id="backwards-nested-keys">Nested keys (documents) for <code>type=o</code> and <code>type=p</code></h4>
+  <ul>
+    <li>To enhance the structure of the API, sub-opinions are now nested within clusters in case law results (<code>type=o</code>), and <code>positions</code> are nested within judges in judge results (<code>type=p</code>).
+    </li>
+  </ul>
+  <h4 id="backwards-type-r"><code>type=r</code> is now for dockets with nested documents</h4>
+  <ul>
+    <li>To align the API results with the front end results, <code>type=r</code> no longer returns a flat list of documents.
+      Instead, it now returns a list of dockets with up to three matching documents nested within each docket's <code>recap_documents</code> key.
+    </li>
+    <li>To return a flat list of documents, as in the past, try the new <code>type=rd</code> parameter.
+      This can be useful for those upgrading from v3 to v4 of the search API.
+    </li>
+    <li>If there are more than three matching documents, the <code>more_docs</code> field for the docket result will be true.
+      As in the front end, you can get the remaining documents for a docket by placing a docket ID query like:
+      <code>type=rd&amp;q=(original query) AND docket_id:XYZ</code>
+    </li>
+    <li>This response type includes two counts of the results: <code>count</code> is the number of dockets returned. <code>document_count</code> is the number of documents.
+    </li>
+  </ul>
+  <h4 id="backwards-type-rd"><code>type=rd</code> is a new result type for documents</h4>
+  <ul>
+    <li><code>type=rd</code> returns a flat list of PACER documents, and is similar to <code>type=r</code> in v3 of the API.
+      Results for this type can be queried by any docket fields except the <code>party</code> and <code>attorney</code> fields.
+    </li>
+    <li>The field differences between <code>r</code> in v3 and <code>rd</code> in v4 are that all the docket-level fields were removed:
+    </li>
+    <ul>
+      <li>assignedTo</li>
+      <li>assigned_to_id</li>
+      <li>caseName</li>
+      <li>cause</li>
+      <li>court</li>
+      <li>court_citation_string</li>
+      <li>court_exact</li>
+      <li>court_id</li>
+      <li>dateArgued</li>
+      <li>dateFiled</li>
+      <li>dateTerminated</li>
+      <li>docketNumber</li>
+      <li>jurisdictionType</li>
+      <li>juryDemand</li>
+      <li>referredTo</li>
+      <li>referred_to_id</li>
+      <li>suitNature</li>
+    </ul>
+    <li><code>docket_id</code> is still available in the <code>rd</code> type so users can identify the docket and pull additional docket data from the docket API.
+    </li>
+    <li>One field that changed is <code>entry_date_filed</code>. In <code>r</code> v3, it was a <code>datetime</code> field with PST midnight as the default time.
+      Now, it's simply a date field.
+    </li>
+    <li>The <code>timestamp</code> field has been moved to the new <code>meta</code> field, which also contains <code>date_created</code>.
+    </li>
+  </ul>
+  <h4 id="backwards-type-d"><code>type=d</code> still returns dockets</h4>
+  <ul>
+    <li><code>type=d</code> returns dockets without nested documents. If all you need in the response is the docket information, this response type will be significantly faster.
+      You can query document fields with this response type even though they will not be returned.
+    </li>
+  </ul>
+  <h4 id="backwards-removed-fields">Removed fields</h4>
+  <ul>
+    <li>The following fields have been removed from the case law search results (<code>type=o</code>):
+    </li>
+    <ul>
+      <li>caseNameShort</li>
+      <li>pagerank</li>
+      <li>status_exact</li>
+      <li>non_participating_judge_ids</li>
+    </ul>
+  </ul>
+  <h4 id="backwards-changed-fields">Changed field values</h4>
+  <ul>
+    <li>For legibility, in the case law search results (<code>type=o</code>), some <code>type</code> field values have changed:
+    </li>
+    <ul>
+      <li>010combined → combined-opinion</li>
+      <li>015unamimous → unanimous-opinion</li>
+      <li>020lead → lead-opinion</li>
+      <li>025plurality → plurality-opinion</li>
+      <li>030concurrence → concurrence-opinion</li>
+      <li>035concurrenceinpart → in-part-opinion</li>
+      <li>040dissent → dissent</li>
+      <li>050addendum → addendum</li>
+      <li>060remittitur → remittitur</li>
+      <li>070rehearing → rehearing</li>
+      <li>080onthemerits → on-the-merits</li>
+      <li>090onmotiontostrike → on-motion-to-strike</li>
+    </ul>
+  </ul>
+  <ul>
+    <li>Some of the values of the <code>status</code> field in the case law search results have changed:
+    </li>
+    <ul>
+      <li>precedential → published</li>
+      <li>non-precedential → unpublished</li>
+      <li>errata → errata</li>
+      <li>separate opinion → separate</li>
+      <li>in-chambers → in-chambers</li>
+      <li>relating-to orders → relating-to</li>
+      <li>unknown status → unknown</li>
+    </ul>
+    <li>The <code>snippet</code> field in the case law search results previously included more than one opinion text field.
+      It now only contains the best text field, based on the following priority and determined by availability:
+    </li>
+    <ul>
+      <li>html_columbia</li>
+      <li>html_lawbox</li>
+      <li>xml_harvard</li>
+      <li>html_anon_2020</li>
+      <li>html</li>
+      <li>plain_text</li>
+    </ul>
+  </ul>
+  <h4 id="backwards-date-times">Dates and times</h4>
+  <ul>
+    <li>All dates and times are in UTC instead of PST.</li>
+    <li>Date objects are now rendered as an ISO-8601 date instead of an ISO-8601 datetime.
+    </li>
+  </ul>
+  <p>The following is a full list of date fields that are now date objects (rather than datetime objects, which they were in v3):
+  </p>
+  <ul>
+    <li>types <code>r</code> and <code>d</code>:</li>
+    <ul>
+      <li>dateArgued</li>
+      <li>dateFiled</li>
+      <li>dateTerminated</li>
+    </ul>
+    <li>types <code>r</code> and <code>rd</code>:</li>
+    <ul>
+      <li><code>entry_date_filed</code> (in type <code>r</code> is available in documents nested within the <code>recap_documents key</code>)</li>
+    </ul>
+    <li>type <code>o</code>:</li>
+    <ul>
+      <li>dateArgued</li>
+      <li>dateFiled</li>
+      <li>dateReargued</li>
+      <li>dateReargumentDenied</li>
+    </ul>
+    <li>type <code>oa</code>:</li>
+    <ul>
+      <li>dateArgued</li>
+      <li>dateReargued</li>
+      <li>dateReargumentDenied</li>
+    </ul>
+    <li>type <code>p</code>:</li>
+    <ul>
+      <li>dob</li>
+      <li>dod</li>
+      <li>The following fields are available within the nested <code>positions</code> key:
+      </li>
+      <ul>
+        <li>date_confirmation</li>
+        <li>date_elected</li>
+        <li>date_hearing</li>
+        <li>date_judicial_committee_action</li>
+        <li>date_nominated</li>
+        <li>date_recess_appointment</li>
+        <li>date_referred_to_judicial_committee</li>
+        <li>date_retirement</li>
+        <li>date_start</li>
+        <li>date_termination</li>
+      </ul>
+    </ul>
+  </ul>
+  <h4 id="backwards-no-random-sorting">No more random sorting</h4>
+  <ul>
+    <li>You can no longer sort the results randomly. This was only used by developers and was difficult to support.
+    </li>
+  </ul>
+  <h4 id="backwards-stemming-synonyms">Stemming and Synonyms</h4>
+  <ul>
+    <li>To provide better relevancy, stemming and synonyms are disabled on the <code>caseName</code> fields.
+    </li>
+    <li>This is because broadening a query to include synonyms and other words with the same stem are not relevant when a user searches for a case by name.
+      For example, when searching for a case name that includes the word "Howells" results for a search on the word "Howell" would not be relevant.
+    </li>
+    <li>This change applies to both the <code>case_name</code> filter and the text query.
+    </li>
+  </ul>
+  <h4 id="backwards-get-params">Changes to GET parameters</h4>
+  <ul>
+    <li>When searching the case law status fields, the GET parameters have been changed as follows:</li>
+    <ul>
+      <li>stat_Precedential → stat_Published</li>
+      <li>stat_Non-Precedential → stat_Unpublished</li>
+      <li>stat_Errata → stat_Errata</li>
+      <li>stat_Separate Opinion → stat_Separate</li>
+      <li>stat_In-chambers → stat_In-chambers</li>
+      <li>stat_Relating-to orders → stat_Relating-to</li>
+      <li>stat_Unknown Status → stat_Unknown</li>
+    </ul>
+  </ul>
+  <h4 id="backwards-400-error">Bad Request Error Code: 400</h4>
+  <ul>
+    <li>The error can contain one of the following custom messages in the <code>detail</code>key, explaining the reason for the error:
+    </li>
+    <ul>
+      <li>The query contains unbalanced parentheses.</li>
+      <li>The query contains unbalanced quotes.</li>
+      <li>The query contains an unrecognized proximity token.</li>
+    </ul>
+  </ul>
+  <h4 id="backwards-500-error">Server Error Code: 500</h4>
+  <ul>
+    <li>Any other error, such as a connection error or a parsing error of the ES query, will raise <code>Server Error</code> Code: <code>500</code>.</li>
+    <li>And the message in the detail key: <code>Internal Server Error. Please try again later or review your query.</code></li>
+  </ul>
+  <h4 id="backwards-404-error">Not Found Error Code: 404</h4>
+  <ul>
+    <li>In the V4 Search API or other V4 database-based endpoints using cursor pagination, the following error can be raised: <code>Not Found Error</code> Code: <code>404</code>
+    </li>
+    <li>Message in the <code>detail</code> key: <code>Invalid cursor</code>
+    </li>
+    <li>This can happen if the cursor was modified manually or if the ordering key changed and doesn't match the ordering key in the cursor.
+    </li>
+    <li>To avoid this problem, when changing the sorting key, restart your request by removing the cursor key from your request.
+    </li>
+  </ul>
+</div>
+{% endblock %}
diff --git a/cl/api/templates/rest-docs-v3.html b/cl/api/templates/rest-docs-v3.html
index d42e218e46..61966fd674 100644
--- a/cl/api/templates/rest-docs-v3.html
+++ b/cl/api/templates/rest-docs-v3.html
@@ -28,7 +28,7 @@ <h4 class="v-offset-below-2">
     <div class="alert-danger alert">
       <p class="bottom">These notes are for a version of the API that is deprecated.
         New implementations should use the <a href="{% url "rest_docs" %}">latest version of the API</a>
-        and existing software <a href="{% url "migration_docs" %}">should be upgraded</a>.
+        and existing software <a href="{% url "migration_guide" %}">should be upgraded</a>.
         These notes are maintained to help with migrations.
       </p>
     </div>
diff --git a/cl/api/urls.py b/cl/api/urls.py
index 54b21600be..68066fc79a 100644
--- a/cl/api/urls.py
+++ b/cl/api/urls.py
@@ -369,11 +369,11 @@
     ),
     # V4 Migration guide
     path(
-        "help/api/migration-docs/",
+        "help/api/v4/migration-guide/",
         TemplateView.as_view(
-            template_name="migration-docs.html",
+            template_name="migration-guide.html",
             extra_context={"private": False},
         ),
-        name="migration_docs",
+        name="migration_guide",
     ),
 ]

From 2b5ac59cabd5ce2cae49a1121447c24af74fb256 Mon Sep 17 00:00:00 2001
From: Mike Lissner <mike@free.law>
Date: Fri, 20 Sep 2024 17:25:31 -0700
Subject: [PATCH 19/19] feat(docs): Add deprecation date

---
 cl/api/templates/migration-guide.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cl/api/templates/migration-guide.html b/cl/api/templates/migration-guide.html
index bed64e6961..44bac10e17 100644
--- a/cl/api/templates/migration-guide.html
+++ b/cl/api/templates/migration-guide.html
@@ -100,7 +100,7 @@ <h3 id="elasticsearch">ElasticSearch</h3>
   </ul>
   <p>For more details please<a href="https://free.law/2024/01/18/new-recap-archive-search-is-live/" target="_blank"> see our blog</a>.</p>
   <h2 id="breaking-changes">Breaking Changes to v3 of the Search API</h2>
-  <p>We cannot continue running Solr forever, but we can do our best to support v3 of the API. To do this, on <strong>XXXDATEXXX</strong>,
+  <p>We cannot continue running Solr forever, but we can do our best to support v3 of the API. To do this, on <strong>November 25, 2024</strong>,
     v3 of the Search API will be upgraded to use Elastic behind the scenes. This will cause some breaking changes.
     If you have not migrated to v4 when we make this swap, these are the breaking changes you should prepare for:
   </p>