/programs/{program_id}/frameworks/{framework_id}/auth/email_providerUpdate email provider configuration
Updates the email provider configuration for the specified framework's OptiTech Auth integration. The email provider handles transactional messages such as verification emails and password reset links.
Quick start
curl "https://api.optitech.com/v1/programs/$PROGRAM_ID/frameworks/$FRAMEWORK_ID/auth/email_provider" \
-X PATCH \
-H "Authorization: Bearer $OPTITECH_API_KEY"optitech optitech-auth config email-provider update --type <type>Parameters
program_idThe OptiTech program ID
framework_idThe OptiTech framework ID
Request body
6 required Required: host, port, username, password, sender_email, sender_name.
hostportusernamepasswordsender_emailsender_nameResponse
200The email provider configuration has been updated
Alternative shape: set type: shared to use the shared variant (all fields optional).
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.