api-sdk-rb 1.11.66 → 1.11.111

data/lib/api-sdk-rb/api/managed_users_api.rb

@@ -309,7 +309,7 @@ module ApiSdkRb
     end
 
     # Create an editor session for a managed user
-    # Makes a short-lived credential that lets the browser of ONE of your managed users use Widgetic's editor pieces, such as the File Browser and the composition editor, without your API key ever reaching that browser. Call this from your server when the page that hosts the editor opens, and hand the `token` in the answer to that page.  The token is shown once. It starts with `wgt_ses_` and the browser sends it as `Authorization: Bearer <token>`. It can do only what the `surfaces` you name allow, and only for this managed user:  - `files`: upload a file (`uploadsPost`) and list the files uploaded for this user (`uploadsGet`). Every   file is filed for this user and stored in your own storage destination, never in Widgetic's: a file a   customer uploads is yours to keep, and takes none of your storage allowance. Partner storage is not   optional, so no session, whatever its surfaces, can be made until you have set a destination   (`setPartnerStorageDestination`); until then it is refused with 409 and `PARTNER_STORAGE_REQUIRED`, and   when the destination cannot be used with 503 and `STORAGE_DESTINATION_UNAVAILABLE`. A destination you   remove after the session was made stops its uploads too (the same 409; the browser is only told that   the feature is not available right now). To keep a customer from uploading, leave `files` out of the   session and hand the editors your own media library instead (`mediaLibrary`). - `editor`: edit one of this user's compositions: read it (`getCompositionById`, its content, design,   embed settings and schemas), check a content change (`validateCompositionContent`), and change its   name, content, design and embed settings (`updateComposition`, `setDynamicContent`). It can reach   only compositions you created for this managed user (tag them with `managedUserId` when you create   them); any other composition, including another of your users', answers 404. - `creator`: use Widgetic's widget creator for this user, including its AI. Draw on canvases and save   them (`getAllCanvases`, `getCanvas`, `createCanvas`, `updateCanvas`, `previewDeleteCanvas`,   `deleteCanvas`); make, change, copy and delete the widgets on them (`createWidget`, `getWidgets`,   `getWidgetsBatch`, `updateWidget`, `uploadWidgetThumbnail`, `duplicateWidget`, `deleteWidget`);   list and make the compositions of a widget it built (`getAllCompositions`, `createComposition`), which   is how it shows the widget with sample values; keep the   conversation of each widget (`getConversationsByWidgetId`, `createConversationForWidget`,   `updateConversation`, `getMessages`, `createMessage`, `updateMessage`, `restoreCheckpoint`); and read a   widget's schemas and give it its repository (`getWidgetContentSchema`, `getWidgetDesignSchema`,   `updateWidgetRepository`). The AI that builds a widget is part of it: list the models   (`agentModelsGet`), open the widget's repository (`agentRepositoriesPost`,   `agentRepositoriesRepoIdGet`), start a generation and follow or cancel it (`agentCodeGeneratePost`,   `operationsStreamGet`, `operationsIdGet`, `operationsIdCancelPost`), build and preview the result   (`agentWidgetBuilderRepoHeadWidgetIdGet`, `buildWidgetFromRepo`, `previewWidgetVersion`), publish a   version of the widget and move between its versions (`agentWidgetBuilderPublishWidgetIdPost`,   `getWidgetPublishHistory`, `setWidgetPublishHistoryLive`, `renameWidgetPublishHistoryTitle`), and   turn a stroke or a sentence into a decision (`agentShapeRecognizePost`, `agentDesignResolvePost`). It can   also offer the customer your presets as starting points: read them and ask for a copy for this customer   (`listMyPresets`, `copyMyPreset`; you choose the presets with `setPartnerPreset`).   What the session makes is filed for this managed user, and the lists it reads hold only this user's   canvases, widgets and compositions. It can reach only canvases, widgets, compositions, repositories,   uploaded files and operations made for this managed user (tag the canvases and widgets you create   with `managedUserId`); any other canvas, widget, composition, conversation, message, repository, file   or operation, including another of your users', answers 404. The creator also saves the composition   it is editing (`updateComposition`, from the `editor` surface) and attaches pictures to its chat   (`uploadsPost`, from the `files` surface), and the surfaces do not imply one another: to open the   whole creator for a user, ask for `creator`, `editor` and `files` together. A generation or a build   one user starts can be followed and cancelled by that user and by you, never by another of your   users. The AI is paid for by your account, as your own calls are: its credits and allowances are   yours. A session cannot make a widget public (publishing a version does not), file one under a   project or an organization, or set anything the creator does not set: a body with another field is   refused with 403 and `EDITOR_SESSION_FIELD_NOT_ALLOWED`.  Everything else is refused with 403 and `EDITOR_SESSION_ROUTE_NOT_ALLOWED`: a session cannot read your account, make more sessions, change your presets or delete a composition, and a session without the `creator` surface cannot create or list compositions. Create the composition yourself with your API key, then open the editor on it.  A session ends at `expiresAt` (at most four hours), when you end it (`revokeManagedUserEditorSession`), or when the managed user is switched off or deleted. A managed user can have at most 100 live sessions at once (`429 EDITOR_SESSION_LIMIT_REACHED`). A session that is bound to a web page (`allowedOrigin`) is refused from any other origin.  The AI the session runs is paid for with your credits. Set `maxCredits` to hold the session to a number of them: once its generations have taken that many (a generation that fails is refunded and does not count), the next one is refused with 402 and `EDITOR_SESSION_CREDIT_LIMIT_REACHED`, and the browser is told only that the feature is not available right now. Without it, the limit Widgetic has set for your account applies when it has set one (the same limit for every session you make, and `maxCredits: null` asks for none), and otherwise the credits of your account are the only ceiling. What each of your users' sessions has spent is in `getManagedUserUsage`.  Each call makes a new session. It does not take an `Idempotency-Key`: the answer holds the token, and the token is never stored where a retry could read it back. The answer is sent with `Cache-Control: no-store`. 
+    # Makes a short-lived credential that lets the browser of ONE of your managed users use Widgetic's editor pieces, such as the File Browser and the composition editor, without your API key ever reaching that browser. Call this from your server when the page that hosts the editor opens, and hand the `token` in the answer to that page.  The token is shown once. It starts with `wgt_ses_` and the browser sends it as `Authorization: Bearer <token>`. It can do only what the `surfaces` you name allow, and only for this managed user:  - `files`: upload a file (`uploadsPost`) and list the files uploaded for this user (`uploadsGet`). Every   file is filed for this user and stored in your own storage destination, never in Widgetic's: a file a   customer uploads is yours to keep, and takes none of your storage allowance. Partner storage is not   optional, so no session, whatever its surfaces, can be made until you have set a destination   (`setPartnerStorageDestination`); until then it is refused with 409 and `PARTNER_STORAGE_REQUIRED`, and   when the destination cannot be used with 503 and `STORAGE_DESTINATION_UNAVAILABLE`. A destination you   remove after the session was made stops its uploads too (the same 409; the browser is only told that   the feature is not available right now). To keep a customer from uploading, leave `files` out of the   session and hand the editors your own media library instead (`mediaLibrary`). - `editor`: edit one of this user's compositions: read it (`getCompositionById`, its content, design,   embed settings and schemas), check a content change (`validateCompositionContent`), and change its   name, content, design and embed settings (`updateComposition`, `setDynamicContent`). For a widget that   answers visitors' questions from documents (the `ai-answers` adapter), it also lists those documents,   adds one as text or as a file (a text file or a picture; a PDF once PDFs are read), and removes one   (`getAiAnswersKnowledge`, `addAiAnswersKnowledgeDocument`, `addAiAnswersKnowledgeFile`,   `removeAiAnswersKnowledgeDocument`); adding costs no credits, and is limited for each of your users   separately. It can reach   only compositions you created for this managed user (tag them with `managedUserId` when you create   them); any other composition, including another of your users', answers 404. - `creator`: use Widgetic's widget creator for this user, including its AI. Draw on canvases and save   them (`getAllCanvases`, `getCanvas`, `createCanvas`, `updateCanvas`, `previewDeleteCanvas`,   `deleteCanvas`); make, change, copy and delete the widgets on them (`createWidget`, `getWidgets`,   `getWidgetsBatch`, `updateWidget`, `uploadWidgetThumbnail`, `duplicateWidget`, `deleteWidget`);   list and make the compositions of a widget it built (`getAllCompositions`, `createComposition`), which   is how it shows the widget with sample values; keep the   conversation of each widget (`getConversationsByWidgetId`, `createConversationForWidget`,   `updateConversation`, `getMessages`, `createMessage`, `updateMessage`, `restoreCheckpoint`); and read a   widget's schemas and give it its repository (`getWidgetContentSchema`, `getWidgetDesignSchema`,   `updateWidgetRepository`). The AI that builds a widget is part of it: list the models   (`agentModelsGet`), open the widget's repository (`agentRepositoriesPost`,   `agentRepositoriesRepoIdGet`), start a generation and follow or cancel it (`agentCodeGeneratePost`,   `operationsStreamGet`, `operationsIdGet`, `operationsIdCancelPost`), build and preview the result   (`agentWidgetBuilderRepoHeadWidgetIdGet`, `buildWidgetFromRepo`, `previewWidgetVersion`), publish a   version of the widget and move between its versions (`agentWidgetBuilderPublishWidgetIdPost`,   `getWidgetPublishHistory`, `setWidgetPublishHistoryLive`, `renameWidgetPublishHistoryTitle`), and   turn a stroke or a sentence into a decision (`agentShapeRecognizePost`, `agentDesignResolvePost`). It can   also offer the customer your presets as starting points: read them and ask for a copy for this customer   (`listMyPresets`, `copyMyPreset`; you choose the presets with `setPartnerPreset`).   What the session makes is filed for this managed user, and the lists it reads hold only this user's   canvases, widgets and compositions. It can reach only canvases, widgets, compositions, repositories,   uploaded files and operations made for this managed user (tag the canvases and widgets you create   with `managedUserId`); any other canvas, widget, composition, conversation, message, repository, file   or operation, including another of your users', answers 404. The creator also saves the composition   it is editing (`updateComposition`, from the `editor` surface) and attaches pictures to its chat   (`uploadsPost`, from the `files` surface), and the surfaces do not imply one another: to open the   whole creator for a user, ask for `creator`, `editor` and `files` together. A generation or a build   one user starts can be followed and cancelled by that user and by you, never by another of your   users. The AI is paid for by your account, as your own calls are: its credits and allowances are   yours. A session cannot make a widget public (publishing a version does not), file one under a   project or an organization, or set anything the creator does not set: a body with another field is   refused with 403 and `EDITOR_SESSION_FIELD_NOT_ALLOWED`. - `workflows`: use Widgetic's Workflows editor for this user. List their workflows and the compositions   a workflow of theirs can chain (`listWorkspaceWorkflows`, `listWorkspaceWorkflowCompositionOptions`);   list the starting points you offer them and make a workflow from one, which gives the user their own copy   of every widget it chains, a composition of their own on each copy, and a draft   (`listWorkspaceWorkflowPresets`, `createWorkspaceWorkflowFromPreset`; you offer them with   `setPartnerWorkflowPreset`);   make, open, change and delete one (`createWorkspaceWorkflow`, `getWorkspaceWorkflow`,   `saveWorkspaceWorkflow`, `deleteWorkspaceWorkflow`) and copy it (`duplicateWorkspaceWorkflow`); publish   it or discard the changes of its draft (`publishWorkspaceWorkflow`,   `discardWorkspaceWorkflowChanges`); read and restore its versions (`listWorkspaceWorkflowVersions`,   `getWorkspaceWorkflowVersion`, `restoreWorkspaceWorkflowVersion`); pause, resume, archive and unarchive it   (`pauseWorkspaceWorkflow`, `resumeWorkspaceWorkflow`, `archiveWorkspaceWorkflow`,   `unarchiveWorkspaceWorkflow`); and read its counts (`getWorkspaceWorkflowStats`). The workspace in each   path is `personal`: a session has no other, and a path that names an organization is refused. What the   session makes is filed for this managed user (`managedUserId`), the lists hold only this user's workflows,   and it can reach only workflows made for this managed user; any other workflow, including one of yours   or of another of your users, answers 404. A workflow can chain only the compositions you made for this   managed user (tag them with `managedUserId`): one that belongs to anybody else is not available, and   publishing a workflow that uses it is refused. A customer can have at most 50 workflows, and what a   customer's session reads never says who published a version. A session cannot set who a workflow belongs   to or which workspace it is in: a body with another field is refused with 403 and   `EDITOR_SESSION_FIELD_NOT_ALLOWED`.  Everything else is refused with 403 and `EDITOR_SESSION_ROUTE_NOT_ALLOWED`: a session cannot read your account, make more sessions, change your presets or delete a composition, and a session without the `creator` surface cannot create or list compositions. Create the composition yourself with your API key, then open the editor on it.  A session ends at `expiresAt` (at most four hours), when you end it (`revokeManagedUserEditorSession`), or when the managed user is switched off or deleted. A managed user can have at most 100 live sessions at once (`429 EDITOR_SESSION_LIMIT_REACHED`). A session that is bound to a web page (`allowedOrigin`) is refused from any other origin.  The AI the session runs is paid for with your credits. Set `maxCredits` to hold the session to a number of them: once its generations have taken that many (a generation that fails is refunded and does not count), the next one is refused with 402 and `EDITOR_SESSION_CREDIT_LIMIT_REACHED`, and the browser is told only that the feature is not available right now. Without it, the limit Widgetic has set for your account applies when it has set one (the same limit for every session you make, and `maxCredits: null` asks for none), and otherwise the credits of your account are the only ceiling. What each of your users' sessions has spent is in `getManagedUserUsage`.  Each call makes a new session. It does not take an `Idempotency-Key`: the answer holds the token, and the token is never stored where a retry could read it back. The answer is sent with `Cache-Control: no-store`. 
     # @param id [String] The managed user the session is for (Widgetic&#39;s id for the user)
     # @param new_editor_session [NewEditorSession] 
     # @param [Hash] opts the optional parameters
@@ -320,7 +320,7 @@ module ApiSdkRb
     end
 
     # Create an editor session for a managed user
-    # Makes a short-lived credential that lets the browser of ONE of your managed users use Widgetic&#39;s editor pieces, such as the File Browser and the composition editor, without your API key ever reaching that browser. Call this from your server when the page that hosts the editor opens, and hand the &#x60;token&#x60; in the answer to that page.  The token is shown once. It starts with &#x60;wgt_ses_&#x60; and the browser sends it as &#x60;Authorization: Bearer &lt;token&gt;&#x60;. It can do only what the &#x60;surfaces&#x60; you name allow, and only for this managed user:  - &#x60;files&#x60;: upload a file (&#x60;uploadsPost&#x60;) and list the files uploaded for this user (&#x60;uploadsGet&#x60;). Every   file is filed for this user and stored in your own storage destination, never in Widgetic&#39;s: a file a   customer uploads is yours to keep, and takes none of your storage allowance. Partner storage is not   optional, so no session, whatever its surfaces, can be made until you have set a destination   (&#x60;setPartnerStorageDestination&#x60;); until then it is refused with 409 and &#x60;PARTNER_STORAGE_REQUIRED&#x60;, and   when the destination cannot be used with 503 and &#x60;STORAGE_DESTINATION_UNAVAILABLE&#x60;. A destination you   remove after the session was made stops its uploads too (the same 409; the browser is only told that   the feature is not available right now). To keep a customer from uploading, leave &#x60;files&#x60; out of the   session and hand the editors your own media library instead (&#x60;mediaLibrary&#x60;). - &#x60;editor&#x60;: edit one of this user&#39;s compositions: read it (&#x60;getCompositionById&#x60;, its content, design,   embed settings and schemas), check a content change (&#x60;validateCompositionContent&#x60;), and change its   name, content, design and embed settings (&#x60;updateComposition&#x60;, &#x60;setDynamicContent&#x60;). It can reach   only compositions you created for this managed user (tag them with &#x60;managedUserId&#x60; when you create   them); any other composition, including another of your users&#39;, answers 404. - &#x60;creator&#x60;: use Widgetic&#39;s widget creator for this user, including its AI. Draw on canvases and save   them (&#x60;getAllCanvases&#x60;, &#x60;getCanvas&#x60;, &#x60;createCanvas&#x60;, &#x60;updateCanvas&#x60;, &#x60;previewDeleteCanvas&#x60;,   &#x60;deleteCanvas&#x60;); make, change, copy and delete the widgets on them (&#x60;createWidget&#x60;, &#x60;getWidgets&#x60;,   &#x60;getWidgetsBatch&#x60;, &#x60;updateWidget&#x60;, &#x60;uploadWidgetThumbnail&#x60;, &#x60;duplicateWidget&#x60;, &#x60;deleteWidget&#x60;);   list and make the compositions of a widget it built (&#x60;getAllCompositions&#x60;, &#x60;createComposition&#x60;), which   is how it shows the widget with sample values; keep the   conversation of each widget (&#x60;getConversationsByWidgetId&#x60;, &#x60;createConversationForWidget&#x60;,   &#x60;updateConversation&#x60;, &#x60;getMessages&#x60;, &#x60;createMessage&#x60;, &#x60;updateMessage&#x60;, &#x60;restoreCheckpoint&#x60;); and read a   widget&#39;s schemas and give it its repository (&#x60;getWidgetContentSchema&#x60;, &#x60;getWidgetDesignSchema&#x60;,   &#x60;updateWidgetRepository&#x60;). The AI that builds a widget is part of it: list the models   (&#x60;agentModelsGet&#x60;), open the widget&#39;s repository (&#x60;agentRepositoriesPost&#x60;,   &#x60;agentRepositoriesRepoIdGet&#x60;), start a generation and follow or cancel it (&#x60;agentCodeGeneratePost&#x60;,   &#x60;operationsStreamGet&#x60;, &#x60;operationsIdGet&#x60;, &#x60;operationsIdCancelPost&#x60;), build and preview the result   (&#x60;agentWidgetBuilderRepoHeadWidgetIdGet&#x60;, &#x60;buildWidgetFromRepo&#x60;, &#x60;previewWidgetVersion&#x60;), publish a   version of the widget and move between its versions (&#x60;agentWidgetBuilderPublishWidgetIdPost&#x60;,   &#x60;getWidgetPublishHistory&#x60;, &#x60;setWidgetPublishHistoryLive&#x60;, &#x60;renameWidgetPublishHistoryTitle&#x60;), and   turn a stroke or a sentence into a decision (&#x60;agentShapeRecognizePost&#x60;, &#x60;agentDesignResolvePost&#x60;). It can   also offer the customer your presets as starting points: read them and ask for a copy for this customer   (&#x60;listMyPresets&#x60;, &#x60;copyMyPreset&#x60;; you choose the presets with &#x60;setPartnerPreset&#x60;).   What the session makes is filed for this managed user, and the lists it reads hold only this user&#39;s   canvases, widgets and compositions. It can reach only canvases, widgets, compositions, repositories,   uploaded files and operations made for this managed user (tag the canvases and widgets you create   with &#x60;managedUserId&#x60;); any other canvas, widget, composition, conversation, message, repository, file   or operation, including another of your users&#39;, answers 404. The creator also saves the composition   it is editing (&#x60;updateComposition&#x60;, from the &#x60;editor&#x60; surface) and attaches pictures to its chat   (&#x60;uploadsPost&#x60;, from the &#x60;files&#x60; surface), and the surfaces do not imply one another: to open the   whole creator for a user, ask for &#x60;creator&#x60;, &#x60;editor&#x60; and &#x60;files&#x60; together. A generation or a build   one user starts can be followed and cancelled by that user and by you, never by another of your   users. The AI is paid for by your account, as your own calls are: its credits and allowances are   yours. A session cannot make a widget public (publishing a version does not), file one under a   project or an organization, or set anything the creator does not set: a body with another field is   refused with 403 and &#x60;EDITOR_SESSION_FIELD_NOT_ALLOWED&#x60;.  Everything else is refused with 403 and &#x60;EDITOR_SESSION_ROUTE_NOT_ALLOWED&#x60;: a session cannot read your account, make more sessions, change your presets or delete a composition, and a session without the &#x60;creator&#x60; surface cannot create or list compositions. Create the composition yourself with your API key, then open the editor on it.  A session ends at &#x60;expiresAt&#x60; (at most four hours), when you end it (&#x60;revokeManagedUserEditorSession&#x60;), or when the managed user is switched off or deleted. A managed user can have at most 100 live sessions at once (&#x60;429 EDITOR_SESSION_LIMIT_REACHED&#x60;). A session that is bound to a web page (&#x60;allowedOrigin&#x60;) is refused from any other origin.  The AI the session runs is paid for with your credits. Set &#x60;maxCredits&#x60; to hold the session to a number of them: once its generations have taken that many (a generation that fails is refunded and does not count), the next one is refused with 402 and &#x60;EDITOR_SESSION_CREDIT_LIMIT_REACHED&#x60;, and the browser is told only that the feature is not available right now. Without it, the limit Widgetic has set for your account applies when it has set one (the same limit for every session you make, and &#x60;maxCredits: null&#x60; asks for none), and otherwise the credits of your account are the only ceiling. What each of your users&#39; sessions has spent is in &#x60;getManagedUserUsage&#x60;.  Each call makes a new session. It does not take an &#x60;Idempotency-Key&#x60;: the answer holds the token, and the token is never stored where a retry could read it back. The answer is sent with &#x60;Cache-Control: no-store&#x60;. 
+    # Makes a short-lived credential that lets the browser of ONE of your managed users use Widgetic&#39;s editor pieces, such as the File Browser and the composition editor, without your API key ever reaching that browser. Call this from your server when the page that hosts the editor opens, and hand the &#x60;token&#x60; in the answer to that page.  The token is shown once. It starts with &#x60;wgt_ses_&#x60; and the browser sends it as &#x60;Authorization: Bearer &lt;token&gt;&#x60;. It can do only what the &#x60;surfaces&#x60; you name allow, and only for this managed user:  - &#x60;files&#x60;: upload a file (&#x60;uploadsPost&#x60;) and list the files uploaded for this user (&#x60;uploadsGet&#x60;). Every   file is filed for this user and stored in your own storage destination, never in Widgetic&#39;s: a file a   customer uploads is yours to keep, and takes none of your storage allowance. Partner storage is not   optional, so no session, whatever its surfaces, can be made until you have set a destination   (&#x60;setPartnerStorageDestination&#x60;); until then it is refused with 409 and &#x60;PARTNER_STORAGE_REQUIRED&#x60;, and   when the destination cannot be used with 503 and &#x60;STORAGE_DESTINATION_UNAVAILABLE&#x60;. A destination you   remove after the session was made stops its uploads too (the same 409; the browser is only told that   the feature is not available right now). To keep a customer from uploading, leave &#x60;files&#x60; out of the   session and hand the editors your own media library instead (&#x60;mediaLibrary&#x60;). - &#x60;editor&#x60;: edit one of this user&#39;s compositions: read it (&#x60;getCompositionById&#x60;, its content, design,   embed settings and schemas), check a content change (&#x60;validateCompositionContent&#x60;), and change its   name, content, design and embed settings (&#x60;updateComposition&#x60;, &#x60;setDynamicContent&#x60;). For a widget that   answers visitors&#39; questions from documents (the &#x60;ai-answers&#x60; adapter), it also lists those documents,   adds one as text or as a file (a text file or a picture; a PDF once PDFs are read), and removes one   (&#x60;getAiAnswersKnowledge&#x60;, &#x60;addAiAnswersKnowledgeDocument&#x60;, &#x60;addAiAnswersKnowledgeFile&#x60;,   &#x60;removeAiAnswersKnowledgeDocument&#x60;); adding costs no credits, and is limited for each of your users   separately. It can reach   only compositions you created for this managed user (tag them with &#x60;managedUserId&#x60; when you create   them); any other composition, including another of your users&#39;, answers 404. - &#x60;creator&#x60;: use Widgetic&#39;s widget creator for this user, including its AI. Draw on canvases and save   them (&#x60;getAllCanvases&#x60;, &#x60;getCanvas&#x60;, &#x60;createCanvas&#x60;, &#x60;updateCanvas&#x60;, &#x60;previewDeleteCanvas&#x60;,   &#x60;deleteCanvas&#x60;); make, change, copy and delete the widgets on them (&#x60;createWidget&#x60;, &#x60;getWidgets&#x60;,   &#x60;getWidgetsBatch&#x60;, &#x60;updateWidget&#x60;, &#x60;uploadWidgetThumbnail&#x60;, &#x60;duplicateWidget&#x60;, &#x60;deleteWidget&#x60;);   list and make the compositions of a widget it built (&#x60;getAllCompositions&#x60;, &#x60;createComposition&#x60;), which   is how it shows the widget with sample values; keep the   conversation of each widget (&#x60;getConversationsByWidgetId&#x60;, &#x60;createConversationForWidget&#x60;,   &#x60;updateConversation&#x60;, &#x60;getMessages&#x60;, &#x60;createMessage&#x60;, &#x60;updateMessage&#x60;, &#x60;restoreCheckpoint&#x60;); and read a   widget&#39;s schemas and give it its repository (&#x60;getWidgetContentSchema&#x60;, &#x60;getWidgetDesignSchema&#x60;,   &#x60;updateWidgetRepository&#x60;). The AI that builds a widget is part of it: list the models   (&#x60;agentModelsGet&#x60;), open the widget&#39;s repository (&#x60;agentRepositoriesPost&#x60;,   &#x60;agentRepositoriesRepoIdGet&#x60;), start a generation and follow or cancel it (&#x60;agentCodeGeneratePost&#x60;,   &#x60;operationsStreamGet&#x60;, &#x60;operationsIdGet&#x60;, &#x60;operationsIdCancelPost&#x60;), build and preview the result   (&#x60;agentWidgetBuilderRepoHeadWidgetIdGet&#x60;, &#x60;buildWidgetFromRepo&#x60;, &#x60;previewWidgetVersion&#x60;), publish a   version of the widget and move between its versions (&#x60;agentWidgetBuilderPublishWidgetIdPost&#x60;,   &#x60;getWidgetPublishHistory&#x60;, &#x60;setWidgetPublishHistoryLive&#x60;, &#x60;renameWidgetPublishHistoryTitle&#x60;), and   turn a stroke or a sentence into a decision (&#x60;agentShapeRecognizePost&#x60;, &#x60;agentDesignResolvePost&#x60;). It can   also offer the customer your presets as starting points: read them and ask for a copy for this customer   (&#x60;listMyPresets&#x60;, &#x60;copyMyPreset&#x60;; you choose the presets with &#x60;setPartnerPreset&#x60;).   What the session makes is filed for this managed user, and the lists it reads hold only this user&#39;s   canvases, widgets and compositions. It can reach only canvases, widgets, compositions, repositories,   uploaded files and operations made for this managed user (tag the canvases and widgets you create   with &#x60;managedUserId&#x60;); any other canvas, widget, composition, conversation, message, repository, file   or operation, including another of your users&#39;, answers 404. The creator also saves the composition   it is editing (&#x60;updateComposition&#x60;, from the &#x60;editor&#x60; surface) and attaches pictures to its chat   (&#x60;uploadsPost&#x60;, from the &#x60;files&#x60; surface), and the surfaces do not imply one another: to open the   whole creator for a user, ask for &#x60;creator&#x60;, &#x60;editor&#x60; and &#x60;files&#x60; together. A generation or a build   one user starts can be followed and cancelled by that user and by you, never by another of your   users. The AI is paid for by your account, as your own calls are: its credits and allowances are   yours. A session cannot make a widget public (publishing a version does not), file one under a   project or an organization, or set anything the creator does not set: a body with another field is   refused with 403 and &#x60;EDITOR_SESSION_FIELD_NOT_ALLOWED&#x60;. - &#x60;workflows&#x60;: use Widgetic&#39;s Workflows editor for this user. List their workflows and the compositions   a workflow of theirs can chain (&#x60;listWorkspaceWorkflows&#x60;, &#x60;listWorkspaceWorkflowCompositionOptions&#x60;);   list the starting points you offer them and make a workflow from one, which gives the user their own copy   of every widget it chains, a composition of their own on each copy, and a draft   (&#x60;listWorkspaceWorkflowPresets&#x60;, &#x60;createWorkspaceWorkflowFromPreset&#x60;; you offer them with   &#x60;setPartnerWorkflowPreset&#x60;);   make, open, change and delete one (&#x60;createWorkspaceWorkflow&#x60;, &#x60;getWorkspaceWorkflow&#x60;,   &#x60;saveWorkspaceWorkflow&#x60;, &#x60;deleteWorkspaceWorkflow&#x60;) and copy it (&#x60;duplicateWorkspaceWorkflow&#x60;); publish   it or discard the changes of its draft (&#x60;publishWorkspaceWorkflow&#x60;,   &#x60;discardWorkspaceWorkflowChanges&#x60;); read and restore its versions (&#x60;listWorkspaceWorkflowVersions&#x60;,   &#x60;getWorkspaceWorkflowVersion&#x60;, &#x60;restoreWorkspaceWorkflowVersion&#x60;); pause, resume, archive and unarchive it   (&#x60;pauseWorkspaceWorkflow&#x60;, &#x60;resumeWorkspaceWorkflow&#x60;, &#x60;archiveWorkspaceWorkflow&#x60;,   &#x60;unarchiveWorkspaceWorkflow&#x60;); and read its counts (&#x60;getWorkspaceWorkflowStats&#x60;). The workspace in each   path is &#x60;personal&#x60;: a session has no other, and a path that names an organization is refused. What the   session makes is filed for this managed user (&#x60;managedUserId&#x60;), the lists hold only this user&#39;s workflows,   and it can reach only workflows made for this managed user; any other workflow, including one of yours   or of another of your users, answers 404. A workflow can chain only the compositions you made for this   managed user (tag them with &#x60;managedUserId&#x60;): one that belongs to anybody else is not available, and   publishing a workflow that uses it is refused. A customer can have at most 50 workflows, and what a   customer&#39;s session reads never says who published a version. A session cannot set who a workflow belongs   to or which workspace it is in: a body with another field is refused with 403 and   &#x60;EDITOR_SESSION_FIELD_NOT_ALLOWED&#x60;.  Everything else is refused with 403 and &#x60;EDITOR_SESSION_ROUTE_NOT_ALLOWED&#x60;: a session cannot read your account, make more sessions, change your presets or delete a composition, and a session without the &#x60;creator&#x60; surface cannot create or list compositions. Create the composition yourself with your API key, then open the editor on it.  A session ends at &#x60;expiresAt&#x60; (at most four hours), when you end it (&#x60;revokeManagedUserEditorSession&#x60;), or when the managed user is switched off or deleted. A managed user can have at most 100 live sessions at once (&#x60;429 EDITOR_SESSION_LIMIT_REACHED&#x60;). A session that is bound to a web page (&#x60;allowedOrigin&#x60;) is refused from any other origin.  The AI the session runs is paid for with your credits. Set &#x60;maxCredits&#x60; to hold the session to a number of them: once its generations have taken that many (a generation that fails is refunded and does not count), the next one is refused with 402 and &#x60;EDITOR_SESSION_CREDIT_LIMIT_REACHED&#x60;, and the browser is told only that the feature is not available right now. Without it, the limit Widgetic has set for your account applies when it has set one (the same limit for every session you make, and &#x60;maxCredits: null&#x60; asks for none), and otherwise the credits of your account are the only ceiling. What each of your users&#39; sessions has spent is in &#x60;getManagedUserUsage&#x60;.  Each call makes a new session. It does not take an &#x60;Idempotency-Key&#x60;: the answer holds the token, and the token is never stored where a retry could read it back. The answer is sent with &#x60;Cache-Control: no-store&#x60;. 
     # @param id [String] The managed user the session is for (Widgetic&#39;s id for the user)
     # @param new_editor_session [NewEditorSession] 
     # @param [Hash] opts the optional parameters