widgetic api managed-users <command> runs the Managed Users operations of the REST API. It has 18 commands. Every command also takes the flags every command takes.
widgetic api managed-users copy-preset-for-managed-user
Give a managed user a copy of one of your presets
- Request:
POST /managed-users/{id}/presets/{key}/copy - Operation:
copyPresetForManagedUser(widgetic api call copyPresetForManagedUserruns it by that name) - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users copy-preset-for-managed-user.
widgetic api managed-users create-composition-from-preset
Create a composition from one of your presets in one call
- Request:
POST /managed-users/{id}/presets/{key}/composition - Operation:
createCompositionFromPreset(widgetic api call createCompositionFromPresetruns it by that name) - Works with any API key.
The whole description and the schemas:
widgetic schema api managed-users create-composition-from-preset.
widgetic api managed-users create-managed-user
Create Managed User
- Request:
POST /managed-users - Operation:
createManagedUser(widgetic api call createManagedUserruns it by that name) - Also written:
widgetic api managed-users create - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users create-managed-user.
widgetic api managed-users create-managed-user-editor-session
Create an editor session for a managed user
- Request:
POST /managed-users/{id}/editor-sessions - Operation:
createManagedUserEditorSession(widgetic api call createManagedUserEditorSessionruns it by that name) - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users create-managed-user-editor-session.
widgetic api managed-users delete-managed-user
Delete Managed User
- Request:
DELETE /managed-users/{id} - Operation:
deleteManagedUser(widgetic api call deleteManagedUserruns it by that name) - Also written:
widgetic api managed-users delete - Needs a partner API key (wgt_prt_…).
- It deletes something, so it asks first; without a terminal it needs
--yes.
The whole description and the schemas:
widgetic schema api managed-users delete-managed-user.
widgetic api managed-users get-all-managed-users
Get Managed Users
- Request:
GET /managed-users - Operation:
getAllManagedUsers(widgetic api call getAllManagedUsersruns it by that name) - Also written:
widgetic api managed-users list - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users get-all-managed-users.
widgetic api managed-users get-managed-user-by-id
Get Managed User By ID
- Request:
GET /managed-users/{id} - Operation:
getManagedUserById(widgetic api call getManagedUserByIdruns it by that name) - Also written:
widgetic api managed-users get - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users get-managed-user-by-id.
widgetic api managed-users get-managed-user-design-defaults
Read design defaults for one managed user
- Request:
GET /managed-users/{id}/design-defaults - Operation:
getManagedUserDesignDefaults(widgetic api call getManagedUserDesignDefaultsruns it by that name) - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users get-managed-user-design-defaults.
widgetic api managed-users get-managed-user-limits
Read monthly credit cap and usage for one managed user
- Request:
GET /managed-users/{id}/limits - Operation:
getManagedUserLimits(widgetic api call getManagedUserLimitsruns it by that name) - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users get-managed-user-limits.
widgetic api managed-users get-managed-user-storage-usage
Storage used by one managed user’s uploads
- Request:
GET /managed-users/{id}/storage-usage - Operation:
getManagedUserStorageUsage(widgetic api call getManagedUserStorageUsageruns it by that name) - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users get-managed-user-storage-usage.
widgetic api managed-users get-managed-user-usage
What a managed user’s editor sessions spent
- Request:
GET /managed-users/{id}/usage - Operation:
getManagedUserUsage(widgetic api call getManagedUserUsageruns it by that name) - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users get-managed-user-usage.
widgetic api managed-users get-managed-users-by-manager-id
Get Managed Users By Manager
- Request:
GET /users/{managerId}/managed-users - Operation:
getManagedUsersByManagerId(widgetic api call getManagedUsersByManagerIdruns it by that name) - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users get-managed-users-by-manager-id.
widgetic api managed-users list-managed-user-entries
List entries across a managed user’s compositions
- Request:
GET /managed-users/{id}/entries - Operation:
listManagedUserEntries(widgetic api call listManagedUserEntriesruns it by that name) - Works with any API key.
The whole description and the schemas:
widgetic schema api managed-users list-managed-user-entries.
widgetic api managed-users revoke-managed-user-editor-session
End one editor session of a managed user
- Request:
DELETE /managed-users/{id}/editor-sessions/{sessionId} - Operation:
revokeManagedUserEditorSession(widgetic api call revokeManagedUserEditorSessionruns it by that name) - Needs a partner API key (wgt_prt_…).
- It deletes something, so it asks first; without a terminal it needs
--yes.
The whole description and the schemas:
widgetic schema api managed-users revoke-managed-user-editor-session.
widgetic api managed-users revoke-managed-user-editor-sessions
End every editor session of a managed user
- Request:
DELETE /managed-users/{id}/editor-sessions - Operation:
revokeManagedUserEditorSessions(widgetic api call revokeManagedUserEditorSessionsruns it by that name) - Needs a partner API key (wgt_prt_…).
- It deletes something, so it asks first; without a terminal it needs
--yes.
The whole description and the schemas:
widgetic schema api managed-users revoke-managed-user-editor-sessions.
widgetic api managed-users set-managed-user-design-defaults
Set or clear design defaults for one managed user
- Request:
PUT /managed-users/{id}/design-defaults - Operation:
setManagedUserDesignDefaults(widgetic api call setManagedUserDesignDefaultsruns it by that name) - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users set-managed-user-design-defaults.
widgetic api managed-users set-managed-user-limits
Set or clear the monthly credit cap for one managed user
- Request:
PUT /managed-users/{id}/limits - Operation:
setManagedUserLimits(widgetic api call setManagedUserLimitsruns it by that name) - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users set-managed-user-limits.
widgetic api managed-users update-managed-user
Update Managed User
- Request:
PUT /managed-users/{id} - Operation:
updateManagedUser(widgetic api call updateManagedUserruns it by that name) - Also written:
widgetic api managed-users update - Needs a partner API key (wgt_prt_…).
The whole description and the schemas:
widgetic schema api managed-users update-managed-user.