POST /v1/storedProcedures
Create a Stored Procedure
Create a new stored procedure within a database schema
POST
POST /v1/storedProcedures
Documentation Index
Fetch the complete documentation index at: https://openmetadata-codex-audit-docs-codebase-alignment.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Create a Stored Procedure
Create a new stored procedure within a database schema.Body Parameters
Name of the stored procedure. Must be unique within the parent database schema.
Fully qualified name of the parent DatabaseSchema (e.g.,
snowflake_prod.analytics.public).The source code and language of the stored procedure.
Human-readable display name for the stored procedure.
Description of the stored procedure in Markdown format.
Array of owner references (users or teams) to assign to the stored procedure.
Fully qualified name of the domain to assign for governance purposes.
Array of classification tags to apply to the stored procedure.
Custom property values defined by your organization’s metadata schema.
POST /v1/storedProcedures
Returns
Returns the created stored procedure object with all specified properties and system-generated fields.Response
Unique identifier for the stored procedure (UUID format).
Stored procedure name.
Fully qualified name in format
service.database.schema.storedProcedure.Human-readable display name.
Description of the stored procedure in Markdown format.
Reference to the parent database schema.
The source code and language of the stored procedure.
Type of database service (e.g., Snowflake, BigQuery, PostgreSQL).
List of owners assigned to the stored procedure.
Domain assignments for governance.
Classification tags applied to the stored procedure.
Custom property values defined by your organization’s metadata schema.
Version number for the entity (starts at 0.1).
Create or Update (PUT)
UsePUT /v1/storedProcedures instead of POST to perform an upsert. If a stored procedure with the same fullyQualifiedName already exists, it will be updated; otherwise, a new stored procedure is created. The request body is the same as POST.
PUT will not return a 409 conflict error if the entity already exists — it will update the existing entity instead.Bulk Create or Update (PUT)
UsePUT /v1/storedProcedures/bulk to create or update multiple stored procedures in a single request. The request body is an array of create request objects.
Error Handling
| Code | Error Type | Description |
|---|---|---|
400 | BAD_REQUEST | Invalid request body or missing required fields |
401 | UNAUTHORIZED | Invalid or missing authentication token |
403 | FORBIDDEN | User lacks permission to create stored procedures |
409 | ENTITY_ALREADY_EXISTS | Stored procedure with same name already exists in schema (POST only) |