POST /v1/storedProcedures
Create a Stored Procedure
Create a new stored procedure within a database schema
POST
POST /v1/storedProcedures
Create a Stored Procedure
Create a new stored procedure within a database schema.Body Parameters
string
required
Name of the stored procedure. Must be unique within the parent database schema.
string
required
Fully qualified name of the parent DatabaseSchema (e.g.,
snowflake_prod.analytics.public).object
The source code and language of the stored procedure.
string
Human-readable display name for the stored procedure.
string
Description of the stored procedure in Markdown format.
array
Array of owner references (users or teams) to assign to the stored procedure.
string
Fully qualified name of the domain to assign for governance purposes.
array
Array of classification tags to apply to the stored procedure.
object
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
string
Unique identifier for the stored procedure (UUID format).
string
Stored procedure name.
string
Fully qualified name in format
service.database.schema.storedProcedure.string
Human-readable display name.
string
Description of the stored procedure in Markdown format.
object
Reference to the parent database schema.
object
The source code and language of the stored procedure.
string
Type of database service (e.g., Snowflake, BigQuery, PostgreSQL).
array
List of owners assigned to the stored procedure.
array
Domain assignments for governance.
array
Classification tags applied to the stored procedure.
object
Custom property values defined by your organization’s metadata schema.
number
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.