Integration development overview | Mingcedar

<div class="manual-doc-article manual-doc-article-section"><h2 id="integration">User guide: Integration development overview</h2>

IO State API provides external read-only access, the page SDK supports runtime interaction, and Python runs host project logic.

<div class="doc-card-list">

<article class="doc-card">

<h3 id="integration-item-1">IO State API V2</h3>

<p>Configure Profiles, published revisions and Access Keys in IO State API for scoped reads and live subscriptions by external systems. It reads collected state and does not provide device writes.</p>

</article>

<article class="doc-card">

<h3 id="integration-item-2">Custom page SDK</h3>

<p>Custom HTML pages use the SDK for declared live values, writes, alarms and history. Publication, menu login requirements and user permissions determine available operations.</p>

</article>

<article class="doc-card">

<h3 id="integration-item-3">Python projects</h3>

<p>Manage code, actions, events and records in the script workspace. Reuse functions through common/ within a project, and manage third-party modules and custom shared packages in Settings → Python.</p>

</article>

<article class="doc-card">

<h3 id="integration-item-4">Databases and external services</h3>

<p>Python uses native database-driver and HTTP-client APIs. Projects manage credentials, timeouts, transactions and external-operation outcomes. Host database and cache credentials are not exposed to scripts.</p>

</article>

</div>

</div>