<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Enabling the MiroTalk meetings API (success!)]]></title><description><![CDATA[<p dir="auto">In case this is useful to anyone else:</p>
<p dir="auto">I wanted to gain access to the full meetings and token APIs at <code>my-server.com</code>/api/v1/docs/:</p>
<p dir="auto"><img src="/assets/uploads/files/1764368793993-9f0b4e5d-b62e-4a55-be88-9b62a224918c-image-resized.png" alt="9f0b4e5d-b62e-4a55-be88-9b62a224918c-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">Since I was able to access the page above, it looked at first like everything was already set and ready to go!</p>
<p dir="auto">However, I soon learned that this was not the case:</p>
<blockquote>
<p dir="auto">{"error":"This endpoint has been disabled. Please contact the administrator for further information."}</p>
</blockquote>
<p dir="auto">This made me think that I needed to use the secret in <code>/app/data/api_secret</code> to access the API. But it didn't work (same error message as above).</p>
<p dir="auto">It turns out I needed to add the following to the <code>/app/data/env</code> file:</p>
<blockquote>
<p dir="auto">API_ALLOW_MEETINGS=true<br />
API_ALLOW_TOKEN=true</p>
</blockquote>
<p dir="auto">Once I restarted the server, I was rewarded with a new error!</p>
<blockquote>
<p dir="auto">{"error":"Unauthorized!"}</p>
</blockquote>
<p dir="auto">This unauthorized error shows up because, I believe, the <code>/app/data/api_secret</code> is not used for the meetings or token APIs. You need to ALSO add the following to your <code>/app/data/env</code> file:</p>
<blockquote>
<p dir="auto">API_KEY_SECRET=yourVerySpecialSecret</p>
</blockquote>
<p dir="auto">Finally, you can click the <code>Authorize</code> button in the swagger / MiroTalk SFU API page (shown above),  and add <code>yourVerySpecialSecret</code> to the input box there. After that, you have access to your own MiroTalk SFU API!</p>
<p dir="auto">Update to add: You can find a complete list of possible <code>env</code> settings here:</p>
<p dir="auto"><a href="https://github.com/miroslavpejic85/mirotalksfu/blob/main/.env.template" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/miroslavpejic85/mirotalksfu/blob/main/.env.template</a></p>
]]></description><link>https://forum.cloudron.io/topic/14643/enabling-the-mirotalk-meetings-api-success</link><generator>RSS for Node</generator><lastBuildDate>Sat, 18 Apr 2026 16:45:17 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/14643.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 28 Nov 2025 22:31:51 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Enabling the MiroTalk meetings API (success!) on Sat, 29 Nov 2025 23:38:29 GMT]]></title><description><![CDATA[<p dir="auto">Thank you, <a class="plugin-mentions-user plugin-mentions-a" href="/user/canadaduane" aria-label="Profile: canadaduane">@<bdi>canadaduane</bdi></a>  for the great analysis! <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f609.png?v=665e13d50c8" class="not-responsive emoji emoji-android emoji--wink" style="height:23px;width:auto;vertical-align:middle" title="😉" alt="😉" /></p>
<p dir="auto">In case it’s helpful, here are some examples of API usage in different languages:</p>
<ul>
<li><strong>JavaScript</strong></li>
<li><strong>PHP</strong></li>
<li><strong>Python</strong></li>
<li><strong>Bash</strong></li>
</ul>
<p dir="auto">You can find full working examples here:<br />
<strong><a href="https://docs.mirotalk.com/mirotalk-sfu/api/" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.mirotalk.com/mirotalk-sfu/api/</a></strong></p>
]]></description><link>https://forum.cloudron.io/post/116222</link><guid isPermaLink="true">https://forum.cloudron.io/post/116222</guid><dc:creator><![CDATA[MiroTalk]]></dc:creator><pubDate>Sat, 29 Nov 2025 23:38:29 GMT</pubDate></item></channel></rss>