---
title: "Streamlabs"
description: "Read Streamlabs account metadata with customer-managed OAuth. Two explicit read commands; no writes."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Streamlabs

<p>Read Streamlabs account metadata with customer-managed OAuth. Two explicit read commands; no writes.</p>

<details data-command-index><summary>What you can do (2)</summary>
<h2>What you can do</h2>
<p>Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/streamlabs#command-streamlabs-user-get">Get Streamlabs identity</a> — <code>streamlabs.user.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/streamlabs#command-streamlabs-donations-list">List donation summaries</a> — <code>streamlabs.donations.list</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/streamlabs">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Streamlabs, then enter the issued values in the connection form below.</p>
<ol>
<li>Register an API application using Streamlabs Developer Settings and the official registration guide, with <a href="https://api.tooluse.net/v1/oauth/callback">https://api.tooluse.net/v1/oauth/callback</a> as its redirect URI. Put the OAuth client ID and client secret in this integration’s connection form, save, and choose Sign in to provider with donations.read. No donation creation or alert permissions are requested. Tooluse.net encrypts the grant and respects actual expiry: tokens returned without expiry are not periodically refreshed; if expiry is returned, refresh uses the original registered callback. Disconnect here and remove the application in Streamlabs to revoke source access. Get user returns only Streamlabs ID/display name; linked social accounts are excluded. List donations returns IDs, Unix creation time, amount and currency, excluding donor names/messages. Use limit and an explicit before or after donation ID (not both) for one page; no automatic traversal. Uses current API v2.0, not v1.0.</li>
</ol>
<p><a href="https://dev.streamlabs.com/docs/register-your-application">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>OAuth access token (optional)</td>
<td>Optional</td>
</tr>
<tr>
<td>Streamlabs OAuth client ID</td>
<td>Optional</td>
</tr>
<tr>
<td>Streamlabs OAuth client secret</td>
<td>Optional</td>
</tr>
<tr>
<td>Registered OAuth redirect URI (optional)</td>
<td>Optional</td>
</tr>
<tr>
<td>Return URL after authorization</td>
<td>Optional</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-streamlabs-user-get">
<summary><span>Get Streamlabs identity — <code>streamlabs.<wbr>user.<wbr>get</code></span></summary>
<p>Read only the connected Streamlabs ID and display name. Excludes linked Twitch, YouTube and Facebook accounts; no account changes.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/streamlabs?command=streamlabs.user.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/streamlabs/commands/streamlabs.user.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-streamlabs-donations-list">
<summary><span>List donation summaries — <code>streamlabs.<wbr>donations.<wbr>list</code></span></summary>
<p>Read one explicit donation page in descending creation order. Returns ID, Unix creation time, amount and original currency; excludes donor names/messages. Use before or after donation ID, not both, to continue. No creation or alerts.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/streamlabs?command=streamlabs.donations.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.limit</code></td>
<td>integer</td>
<td>Required</td>
<td>Requested page size. Choose a small page such as 20; response byte budget applies. This is an int32 parameter, not an invented provider page cap.</td>
<td><code>minimum: 1; maximum: 2147483647</code></td>
</tr>
<tr>
<td><code>query.before</code></td>
<td>integer</td>
<td>Optional</td>
<td>Donation ID before which to read; omit initially.</td>
<td><code>minimum: 1; maximum: 2147483647</code></td>
</tr>
<tr>
<td><code>query.after</code></td>
<td>integer</td>
<td>Optional</td>
<td>Donation ID after which to read; do not combine with before.</td>
<td><code>minimum: 1; maximum: 2147483647</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/streamlabs/commands/streamlabs.donations.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "limit": 20,
    "before": 80179030
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://dev.streamlabs.com/docs/register-your-application">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/streamlabs/index.mdx