Transfer schedule ownership
Schedules
Transfer schedule ownership
PUT
Transfer schedule ownership
Transfers ownership of a schedule from one user to another user in the same organization. New ownership will be immediate and can’t be reversed using this endpoint.
How ownership transfer affects schedule execution depends on the type of destination the schedule uses, and for email destinations, whether the Personalize delivery with the recipient’s user attributes is enabled:
| Slack, SFTP, & Webhooks | Email without personalization | Email with personalization | |
|---|---|---|---|
| Future jobs are executed by… | New owner | New owner | Each recipient |
| Permissions, data access, & user attributes are based on… | New owner | New owner | Each recipient |
| Output is generated using… | New owner access | New owner access | Recipient access |
Authorizations
Can be either an Organization API Key or Personal Access Token (PAT).
Include in the Authorization header as: Bearer YOUR_TOKEN
Path Parameters
The ID of the schedule. To find a schedule's ID:
- Navigate to the dashboard of a document.
- Click File > Deliveries & Alerts.
- Next to a schedule, click Edit.
The schedule's ID is in the page's URL, after /schedules/. For example, the schedule ID in this URL is 123e4567-e89b-12d3-a456-426614174000:
https://blobsrus.omniapp.co/dashboards/e23ebaa0/schedules/123e4567-e89b-12d3-a456-426614174000
Body
application/json
The ID of the user to transfer schedule ownership to. Use the List users endpoint to retrieve user IDs.
The new owner must:
- Be a member of the same organization
- Not be the current owner
- Have permission to view the dashboard associated with the schedule
Response
Ownership transferred successfully
Example:
true