motherduck-rest-api

You can automate MotherDuck service account provisioning by making control-plane REST calls to create service accounts and manage their lifecycle. This requires bearer admin authentication and applies to provisioning operations rather than SQL data plane queries.

The MotherDuck control-plane REST API handles admin tasks like service-account provisioning, token lifecycle operations, and Duckling configuration. The SQL data plane or query endpoints are for application querying and should not be used for these provisioning and configuration operations.

You manage MotherDuck access token lifecycle through admin-controlled REST API operations to create tokens, list metadata, and invalidate them. One-time secrets are preserved safely while requiring bearer admin authentication for all operations.

Yes, you can read and update Duckling instance settings and mint Dive embed sessions for specific service accounts through MotherDuck REST API control-plane calls. This requires a read-before-write posture for configuration changes.

MotherDuck control-plane REST API workflows require bearer admin authentication. Strict error handling surfaces status codes and response bodies, and destructive operations like service account deletion require explicit confirmation.

You should not use MotherDuck REST API control-plane endpoints for application querying or SQL data plane operations. These endpoints are intended strictly for provisioning, configuration, active account inspection, and embedding operations.