/programs/{program_id}/frameworks/{framework_id}/ownersCreate role
Creates a Postgres role in the specified framework. For related information, see Manage roles.
Connections established to the active integration will be dropped. If the integration is idle, the endpoint becomes active for a short period of time and is suspended afterward.
Quick start
curl "https://api.optitech.com/v1/programs/$PROGRAM_ID/frameworks/$FRAMEWORK_ID/owners" \
-X POST \
-H "Authorization: Bearer $OPTITECH_API_KEY" \
-H "Content-Type: application/json" \
-d '{"role":{"name":"sally"}}'optitech roles create --name <name>Parameters
program_idThe OptiTech program ID
framework_idThe framework ID
Request body
1 required Required: role.name.
roleResponse
201Created a role in the specified framework
Errors
General error
This endpoint can return the standard OptiTech API error response.
Response fields
messageRequired. Human-readable error message.codeRequired. Machine-readable error code.request_idOptional. Request identifier for debugging. You can provide one with theX-Request-IDheader.
Retry guidance
If no response is returned, the request may still have reached the server. This is why retry safety depends on the method and status code.
Idempotent methods (GET, HEAD, OPTIONS) are generally safe to retry after a network error or timeout. Non-idempotent methods (POST, PATCH, DELETE, PUT) can change state, so avoid automatic retries unless your workflow can tolerate duplicate effects.
Responses with 423 Locked or 503 Service Unavailable are safe to retry. 423 Locked means the resource is temporarily locked, usually because another operation is in progress.