## Перевірка у документації

Ви можете побачити визначені cookie в інтерфейсі документації за адресою `/docs`:

<div class="screenshot">
<img src="/img/tutorial/cookie-param-models/image01.png">
</div>

/// info | Інформація

* ⚫️ 📨 🎚 🆎 `HTTPBasicCredentials`:
    * ⚫️ 🔌 `username` & `password` 📨.

{* ../../docs_src/security/tutorial006.py hl[2,6,10] *}

🕐❔ 👆 🔄 📂 📛 🥇 🕰 (⚖️ 🖊 "🛠️" 🔼 🩺) 🖥 🔜 💭 👆 👆 🆔 & 🔐:

<img src="/img/tutorial/security/image12.png">

## ✅ 🆔

📥 🌅 🏁 🖼.

⚙️ 🔗 ✅ 🚥 🆔 &amp; 🔐 ☑.

filename | sha256 hash
-------- | -----------
[kubernetes.tar.gz](https://dl.k8s.io/v1.8.15/kubernetes.tar.gz) | `d3478129e17e98e70d1108d841495cc6f54b218671c18ad0a5eb96ccfee79021`
[kubernetes-src.tar.gz](https://dl.k8s.io/v1.8.15/kubernetes-src.tar.gz) | `befa7e693f8b56ccf562f205ba6821349ad74ac8da616d0701eb7aa18c5c2739`

### Client Binaries

filename | sha256 hash
-------- | -----------

<img src="/img/tutorial/behind-a-proxy/image01.png">

But if we access the docs UI at the "official" URL using the proxy with port `9999`, at `/api/v1/docs`, it works correctly! 🎉

You can check it at <a href="http://127.0.0.1:9999/api/v1/docs" class="external-link" target="_blank">http://127.0.0.1:9999/api/v1/docs</a>:

<img src="/img/tutorial/behind-a-proxy/image02.png">

[kubernetes.tar.gz](https://dl.k8s.io/v1.20.15/kubernetes.tar.gz) | 470f3c6779d9bb19adc7153f2f7a235f4ce4c30cab193b630683b86853508bd670d4d6866c3a9a601b7b074a03d194efe18f131607ca78bbc9dba91c4285ca75
[kubernetes-src.tar.gz](https://dl.k8s.io/v1.20.15/kubernetes-src.tar.gz) | cb2fd7da08d2db9ae287769295b2e89448853973934f5d87c6bd0553e7fcc638639579f5f09fa11559d7bb8d7a21d332f061bf8a878d43d796d3495f1e2a8a04

### Client Binaries

filename | sha512 hash

👉 🌌, 👆 💪 🤚 🏆 👯‍♂️ 🌏: 🆎 ✍ ⏮️ **🏭 🐕‍🦺** & **💽 🖥**.

## 👀 ⚫️ 🩺

🕐❔ 👆 👀 🏧 🩺, 👆 💪 ✅ 👈 🔢 🏷 & 🔢 🏷 🔜 👯‍♂️ ✔️ 👫 👍 🎻 🔗:

<img src="/img/tutorial/response-model/image01.png">

&amp; 👯‍♂️ 🏷 🔜 ⚙️ 🎓 🛠️ 🧾:

<img src="/img/tutorial/response-model/image02.png">

## 🎏 📨 🆎 ✍

📤 5️⃣📆 💼 🌐❔ 👆 📨 🕳 👈 🚫 ☑ Pydantic 🏑 &amp; 👆 ✍ ⚫️ 🔢, 🕴 🤚 🐕‍🦺 🚚 🏭 (👨‍🎨, ✍, ♒️).

[kubernetes.tar.gz](https://dl.k8s.io/v1.30.14/kubernetes.tar.gz) | fc6533c68b5bf3368106b019c4f0d9fa9064ee7a3d1167b5e8e4506cf2b6d5296e4ba8eccad3569a8b56208b7b52936edb20a8e60b058fd4d212687df3a3abab
[kubernetes-src.tar.gz](https://dl.k8s.io/v1.30.14/kubernetes-src.tar.gz) | 576cfc9ae808d5f9e3c2a09f305d75ae025d1de289995758cd70999d27d5131c11ae80d6e4c32cb6ce1899dabdb8040d84434d3a17df2eef5522d97f0f0f8220

### Client Binaries

filename | sha512 hash

///

The interactive API docs will update accordingly, to allow multiple values:

<img src="/img/tutorial/query-params-str-validations/image02.png">

### Query parameter list / multiple values with defaults { #query-parameter-list-multiple-values-with-defaults }

When you see the automatic docs, you can check that the input model and output model will both have their own JSON Schema:

<img src="/img/tutorial/response-model/image01.png">

And both models will be used for the interactive API documentation:

<img src="/img/tutorial/response-model/image02.png">

## Other Return Type Annotations { #other-return-type-annotations }

Quando você vê a documentação automática, pode verificar se o modelo de entrada e o modelo de saída terão seus próprios esquemas JSON:

<img src="/img/tutorial/response-model/image01.png">

E ambos os modelos serão usados ​​para a documentação interativa da API:

<img src="/img/tutorial/response-model/image02.png">

## Outras anotações de tipo de retorno