Skip to content

feat: Updated OpenAPI spec #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HavenDV merged 1 commit into from
Sep 24, 2026
Merged

feat: Updated OpenAPI spec #67

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 24 additions & 15 deletions src/libs/SmallestAI/Generated/SmallestAI.AuthClient.CreateAccessToken.g.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,21 +45,24 @@ partial void ProcessCreateAccessTokenResponseContent(
/// Create access token<br/>
/// Mint a short-lived access token from your API key. Call this from your server,<br/>
/// then hand the returned `access_token` to a browser or mobile client. The client<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS and STT requests. On<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS, STT and speech-to-speech<br/>
/// requests. On<br/>
/// WebSocket connections it can also go in the `api_key` query parameter. HTTP<br/>
/// requests must use the header.<br/>
/// A token works any number of times until it expires. It is accepted only on<br/>
/// TTS, STT and speech-to-speech inference routes: `POST /waves/v1/stt/`, `WSS /waves/v1/stt/live`,<br/>
/// `POST /waves/v1/tts`, `POST /waves/v1/tts/live`, `WSS /waves/v1/tts/live`, the<br/>
/// dedicated Lightning v3.1 routes (`POST /waves/v1/lightning-v3.1/get_speech`,<br/>
/// `POST /waves/v1/lightning-v3.1/stream`, `WSS /waves/v1/lightning-v3.1/get_speech/stream`),<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes. Every other<br/>
/// route, including this one and `POST /waves/v1/pulse/get_text`, returns `403`<br/>
/// to a token.<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes (public catalog, no cloned<br/>
/// voices). Treat any route not listed as unavailable to tokens. This endpoint,<br/>
/// `POST /waves/v1/pulse/get_text`, voice cloning, pronunciation dictionaries,<br/>
/// analytics and chat completions return `403` to a token.<br/>
/// Requests made with a token are billed to the API key that minted it. Deleting<br/>
/// that key invalidates its tokens. A token is valid only in the region that<br/>
/// minted it. If your server and your users can be in different regions, mint and<br/>
/// call through the same region-pinned hostname (for example `api.us.smallest.ai`).<br/>
/// call through the same region-pinned hostname: `api.india.smallest.ai` (Mumbai) or<br/>
/// `api.us.smallest.ai` (Oregon).<br/>
/// ```bash<br/>
/// curl -X POST "https://api.smallest.ai/waves/v1/auth/token" \<br/>
/// -H "Authorization: Bearer $SMALLEST_API_KEY" \<br/>
Expand Down Expand Up @@ -92,21 +95,24 @@ partial void ProcessCreateAccessTokenResponseContent(
/// Create access token<br/>
/// Mint a short-lived access token from your API key. Call this from your server,<br/>
/// then hand the returned `access_token` to a browser or mobile client. The client<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS and STT requests. On<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS, STT and speech-to-speech<br/>
/// requests. On<br/>
/// WebSocket connections it can also go in the `api_key` query parameter. HTTP<br/>
/// requests must use the header.<br/>
/// A token works any number of times until it expires. It is accepted only on<br/>
/// TTS, STT and speech-to-speech inference routes: `POST /waves/v1/stt/`, `WSS /waves/v1/stt/live`,<br/>
/// `POST /waves/v1/tts`, `POST /waves/v1/tts/live`, `WSS /waves/v1/tts/live`, the<br/>
/// dedicated Lightning v3.1 routes (`POST /waves/v1/lightning-v3.1/get_speech`,<br/>
/// `POST /waves/v1/lightning-v3.1/stream`, `WSS /waves/v1/lightning-v3.1/get_speech/stream`),<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes. Every other<br/>
/// route, including this one and `POST /waves/v1/pulse/get_text`, returns `403`<br/>
/// to a token.<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes (public catalog, no cloned<br/>
/// voices). Treat any route not listed as unavailable to tokens. This endpoint,<br/>
/// `POST /waves/v1/pulse/get_text`, voice cloning, pronunciation dictionaries,<br/>
/// analytics and chat completions return `403` to a token.<br/>
/// Requests made with a token are billed to the API key that minted it. Deleting<br/>
/// that key invalidates its tokens. A token is valid only in the region that<br/>
/// minted it. If your server and your users can be in different regions, mint and<br/>
/// call through the same region-pinned hostname (for example `api.us.smallest.ai`).<br/>
/// call through the same region-pinned hostname: `api.india.smallest.ai` (Mumbai) or<br/>
/// `api.us.smallest.ai` (Oregon).<br/>
/// ```bash<br/>
/// curl -X POST "https://api.smallest.ai/waves/v1/auth/token" \<br/>
/// -H "Authorization: Bearer $SMALLEST_API_KEY" \<br/>
Expand Down Expand Up @@ -670,21 +676,24 @@ partial void ProcessCreateAccessTokenResponseContent(
/// Create access token<br/>
/// Mint a short-lived access token from your API key. Call this from your server,<br/>
/// then hand the returned `access_token` to a browser or mobile client. The client<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS and STT requests. On<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS, STT and speech-to-speech<br/>
/// requests. On<br/>
/// WebSocket connections it can also go in the `api_key` query parameter. HTTP<br/>
/// requests must use the header.<br/>
/// A token works any number of times until it expires. It is accepted only on<br/>
/// TTS, STT and speech-to-speech inference routes: `POST /waves/v1/stt/`, `WSS /waves/v1/stt/live`,<br/>
/// `POST /waves/v1/tts`, `POST /waves/v1/tts/live`, `WSS /waves/v1/tts/live`, the<br/>
/// dedicated Lightning v3.1 routes (`POST /waves/v1/lightning-v3.1/get_speech`,<br/>
/// `POST /waves/v1/lightning-v3.1/stream`, `WSS /waves/v1/lightning-v3.1/get_speech/stream`),<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes. Every other<br/>
/// route, including this one and `POST /waves/v1/pulse/get_text`, returns `403`<br/>
/// to a token.<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes (public catalog, no cloned<br/>
/// voices). Treat any route not listed as unavailable to tokens. This endpoint,<br/>
/// `POST /waves/v1/pulse/get_text`, voice cloning, pronunciation dictionaries,<br/>
/// analytics and chat completions return `403` to a token.<br/>
/// Requests made with a token are billed to the API key that minted it. Deleting<br/>
/// that key invalidates its tokens. A token is valid only in the region that<br/>
/// minted it. If your server and your users can be in different regions, mint and<br/>
/// call through the same region-pinned hostname (for example `api.us.smallest.ai`).<br/>
/// call through the same region-pinned hostname: `api.india.smallest.ai` (Mumbai) or<br/>
/// `api.us.smallest.ai` (Oregon).<br/>
/// ```bash<br/>
/// curl -X POST "https://api.smallest.ai/waves/v1/auth/token" \<br/>
/// -H "Authorization: Bearer $SMALLEST_API_KEY" \<br/>
Expand Down
39 changes: 24 additions & 15 deletions src/libs/SmallestAI/Generated/SmallestAI.IAuthClient.CreateAccessToken.g.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,21 +8,24 @@ public partial interface IAuthClient
/// Create access token<br/>
/// Mint a short-lived access token from your API key. Call this from your server,<br/>
/// then hand the returned `access_token` to a browser or mobile client. The client<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS and STT requests. On<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS, STT and speech-to-speech<br/>
/// requests. On<br/>
/// WebSocket connections it can also go in the `api_key` query parameter. HTTP<br/>
/// requests must use the header.<br/>
/// A token works any number of times until it expires. It is accepted only on<br/>
/// TTS, STT and speech-to-speech inference routes: `POST /waves/v1/stt/`, `WSS /waves/v1/stt/live`,<br/>
/// `POST /waves/v1/tts`, `POST /waves/v1/tts/live`, `WSS /waves/v1/tts/live`, the<br/>
/// dedicated Lightning v3.1 routes (`POST /waves/v1/lightning-v3.1/get_speech`,<br/>
/// `POST /waves/v1/lightning-v3.1/stream`, `WSS /waves/v1/lightning-v3.1/get_speech/stream`),<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes. Every other<br/>
/// route, including this one and `POST /waves/v1/pulse/get_text`, returns `403`<br/>
/// to a token.<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes (public catalog, no cloned<br/>
/// voices). Treat any route not listed as unavailable to tokens. This endpoint,<br/>
/// `POST /waves/v1/pulse/get_text`, voice cloning, pronunciation dictionaries,<br/>
/// analytics and chat completions return `403` to a token.<br/>
/// Requests made with a token are billed to the API key that minted it. Deleting<br/>
/// that key invalidates its tokens. A token is valid only in the region that<br/>
/// minted it. If your server and your users can be in different regions, mint and<br/>
/// call through the same region-pinned hostname (for example `api.us.smallest.ai`).<br/>
/// call through the same region-pinned hostname: `api.india.smallest.ai` (Mumbai) or<br/>
/// `api.us.smallest.ai` (Oregon).<br/>
/// ```bash<br/>
/// curl -X POST "https://api.smallest.ai/waves/v1/auth/token" \<br/>
/// -H "Authorization: Bearer $SMALLEST_API_KEY" \<br/>
Expand All @@ -45,21 +48,24 @@ public partial interface IAuthClient
/// Create access token<br/>
/// Mint a short-lived access token from your API key. Call this from your server,<br/>
/// then hand the returned `access_token` to a browser or mobile client. The client<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS and STT requests. On<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS, STT and speech-to-speech<br/>
/// requests. On<br/>
/// WebSocket connections it can also go in the `api_key` query parameter. HTTP<br/>
/// requests must use the header.<br/>
/// A token works any number of times until it expires. It is accepted only on<br/>
/// TTS, STT and speech-to-speech inference routes: `POST /waves/v1/stt/`, `WSS /waves/v1/stt/live`,<br/>
/// `POST /waves/v1/tts`, `POST /waves/v1/tts/live`, `WSS /waves/v1/tts/live`, the<br/>
/// dedicated Lightning v3.1 routes (`POST /waves/v1/lightning-v3.1/get_speech`,<br/>
/// `POST /waves/v1/lightning-v3.1/stream`, `WSS /waves/v1/lightning-v3.1/get_speech/stream`),<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes. Every other<br/>
/// route, including this one and `POST /waves/v1/pulse/get_text`, returns `403`<br/>
/// to a token.<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes (public catalog, no cloned<br/>
/// voices). Treat any route not listed as unavailable to tokens. This endpoint,<br/>
/// `POST /waves/v1/pulse/get_text`, voice cloning, pronunciation dictionaries,<br/>
/// analytics and chat completions return `403` to a token.<br/>
/// Requests made with a token are billed to the API key that minted it. Deleting<br/>
/// that key invalidates its tokens. A token is valid only in the region that<br/>
/// minted it. If your server and your users can be in different regions, mint and<br/>
/// call through the same region-pinned hostname (for example `api.us.smallest.ai`).<br/>
/// call through the same region-pinned hostname: `api.india.smallest.ai` (Mumbai) or<br/>
/// `api.us.smallest.ai` (Oregon).<br/>
/// ```bash<br/>
/// curl -X POST "https://api.smallest.ai/waves/v1/auth/token" \<br/>
/// -H "Authorization: Bearer $SMALLEST_API_KEY" \<br/>
Expand All @@ -82,21 +88,24 @@ public partial interface IAuthClient
/// Create access token<br/>
/// Mint a short-lived access token from your API key. Call this from your server,<br/>
/// then hand the returned `access_token` to a browser or mobile client. The client<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS and STT requests. On<br/>
/// sends it as `Authorization: Bearer &lt;access_token&gt;` on TTS, STT and speech-to-speech<br/>
/// requests. On<br/>
/// WebSocket connections it can also go in the `api_key` query parameter. HTTP<br/>
/// requests must use the header.<br/>
/// A token works any number of times until it expires. It is accepted only on<br/>
/// TTS, STT and speech-to-speech inference routes: `POST /waves/v1/stt/`, `WSS /waves/v1/stt/live`,<br/>
/// `POST /waves/v1/tts`, `POST /waves/v1/tts/live`, `WSS /waves/v1/tts/live`, the<br/>
/// dedicated Lightning v3.1 routes (`POST /waves/v1/lightning-v3.1/get_speech`,<br/>
/// `POST /waves/v1/lightning-v3.1/stream`, `WSS /waves/v1/lightning-v3.1/get_speech/stream`),<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes. Every other<br/>
/// route, including this one and `POST /waves/v1/pulse/get_text`, returns `403`<br/>
/// to a token.<br/>
/// `WSS /waves/v1/s2s`, and the voice-listing routes (public catalog, no cloned<br/>
/// voices). Treat any route not listed as unavailable to tokens. This endpoint,<br/>
/// `POST /waves/v1/pulse/get_text`, voice cloning, pronunciation dictionaries,<br/>
/// analytics and chat completions return `403` to a token.<br/>
/// Requests made with a token are billed to the API key that minted it. Deleting<br/>
/// that key invalidates its tokens. A token is valid only in the region that<br/>
/// minted it. If your server and your users can be in different regions, mint and<br/>
/// call through the same region-pinned hostname (for example `api.us.smallest.ai`).<br/>
/// call through the same region-pinned hostname: `api.india.smallest.ai` (Mumbai) or<br/>
/// `api.us.smallest.ai` (Oregon).<br/>
/// ```bash<br/>
/// curl -X POST "https://api.smallest.ai/waves/v1/auth/token" \<br/>
/// -H "Authorization: Bearer $SMALLEST_API_KEY" \<br/>
Expand Down
2 changes: 1 addition & 1 deletion src/libs/SmallestAI/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
"post": {
"operationId": "auth_create_access_token",
"summary": "Create access token",
"description": "Mint a short-lived access token from your API key. Call this from your server,\nthen hand the returned `access_token` to a browser or mobile client. The client\nsends it as `Authorization: Bearer <access_token>` on TTS and STT requests. On\nWebSocket connections it can also go in the `api_key` query parameter. HTTP\nrequests must use the header.\n\nA token works any number of times until it expires. It is accepted only on\nTTS, STT and speech-to-speech inference routes: `POST /waves/v1/stt/`, `WSS /waves/v1/stt/live`,\n`POST /waves/v1/tts`, `POST /waves/v1/tts/live`, `WSS /waves/v1/tts/live`, the\ndedicated Lightning v3.1 routes (`POST /waves/v1/lightning-v3.1/get_speech`,\n`POST /waves/v1/lightning-v3.1/stream`, `WSS /waves/v1/lightning-v3.1/get_speech/stream`),\n`WSS /waves/v1/s2s`, and the voice-listing routes. Every other\nroute, including this one and `POST /waves/v1/pulse/get_text`, returns `403`\nto a token.\n\nRequests made with a token are billed to the API key that minted it. Deleting\nthat key invalidates its tokens. A token is valid only in the region that\nminted it. If your server and your users can be in different regions, mint and\ncall through the same region-pinned hostname (for example `api.us.smallest.ai`).\n\n```bash\ncurl -X POST \"https://api.smallest.ai/waves/v1/auth/token\" \\\n -H \"Authorization: Bearer $SMALLEST_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"ttl_seconds\": 300}'\n```\n\nSee the [Authentication guide](/models/api-reference/token-based-authentication)\nfor the end-to-end server and client flow.\n",
"description": "Mint a short-lived access token from your API key. Call this from your server,\nthen hand the returned `access_token` to a browser or mobile client. The client\nsends it as `Authorization: Bearer <access_token>` on TTS, STT and speech-to-speech\nrequests. On\nWebSocket connections it can also go in the `api_key` query parameter. HTTP\nrequests must use the header.\n\nA token works any number of times until it expires. It is accepted only on\nTTS, STT and speech-to-speech inference routes: `POST /waves/v1/stt/`, `WSS /waves/v1/stt/live`,\n`POST /waves/v1/tts`, `POST /waves/v1/tts/live`, `WSS /waves/v1/tts/live`, the\ndedicated Lightning v3.1 routes (`POST /waves/v1/lightning-v3.1/get_speech`,\n`POST /waves/v1/lightning-v3.1/stream`, `WSS /waves/v1/lightning-v3.1/get_speech/stream`),\n`WSS /waves/v1/s2s`, and the voice-listing routes (public catalog, no cloned\nvoices). Treat any route not listed as unavailable to tokens. This endpoint,\n`POST /waves/v1/pulse/get_text`, voice cloning, pronunciation dictionaries,\nanalytics and chat completions return `403` to a token.\n\nRequests made with a token are billed to the API key that minted it. Deleting\nthat key invalidates its tokens. A token is valid only in the region that\nminted it. If your server and your users can be in different regions, mint and\ncall through the same region-pinned hostname: `api.india.smallest.ai` (Mumbai) or\n`api.us.smallest.ai` (Oregon).\n\n```bash\ncurl -X POST \"https://api.smallest.ai/waves/v1/auth/token\" \\\n -H \"Authorization: Bearer $SMALLEST_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"ttl_seconds\": 300}'\n```\n\nSee the [Authentication guide](/models/api-reference/token-based-authentication)\nfor the end-to-end server and client flow.\n",
"tags": [
"auth"
],
Expand Down
Loading