Update Organization Profile
PATCH/organization
Updates the organization profile details. Only account owners have permission to do this. Note: both fields are optional but at least one should be sent in the request. It is not necessary to set the header Content-Type for this request. It is set automatically by the HTTP client.
Request
- multipart/form-data
Body
The logo of the organization, file type must be png or jpeg.
A JSON string that contains the details to update. Contains the following keys: organization_name
(string): the new name of the organization, timezone_utc_offset
(string): the new timezone offset of the organization, is_approval_required
(boolean): whether the approval workflow is enabled or not. receiver_registration_message_template
(string): the message template sent to the receivers inviting them to registration. Sending this field empty sets the default
value for it. otp_message_template
(string): the message template sent to the receivers sending the OTP to complete the registration flow. Sending this field empty sets the default
value for it. For example: '{"organization_name": "NewOrgName", "timezone_utc_offset": "+02:00", "is_approval_required": true, "receiver_registration_message_template": "You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register.", "otp_message_template": "{{.OTP}} is your {{.OrganizationName}} phone verification code."}'
Responses
- 200
- 401
- 403
OK
- application/json
- Schema
- Example (from schema)
- Example
Schema
{
"message": "string"
}
{
"message": "organization profile updated successfully"
}
Unauthorized
- application/json
- Schema
- Example (from schema)
- Example
Schema
extras
object
{
"error": "Not authorized",
"extras": {
"status": 401,
"message": "Not authorized"
}
}
{
"error": "Not authorized",
"extras": {
"status": 401,
"message": "Not authorized"
}
}
Forbidden
- application/json
- Schema
- Example (from schema)
- Example
Schema
{
"error": "Forbidden"
}
{
"error": "Forbidden"
}