ImmyBot Tools
Written By Christopher Scaminaci
Last updated 7 days ago
ImmyBot Tools
immy_ · 555 tools · Free 264 · Pro 291
Software deployment and endpoint maintenance for MSPs. Authentication is app-only against the customer's own Microsoft Entra directory, so the credential has four parts: an Entra application id and secret, the Entra tenant id or domain, and your ImmyBot instance address. The Entra token is presented straight to the ImmyBot instance; there is no ImmyBot-native token exchange and no refresh token, so expiry is recovered by minting again. Paging is mixed: list endpoints take a page number with page size, filters and sorts, while the grid feeds take skip and take with a page size capped at 100. POST is verb-overloaded here, so several tools that read data are POSTs and stay read-only. Bodies are passed through as sent, except the four spreadsheet exports, which return a link to the stored file.
All connector tools · ImmyBot setup guide
ImmyBot tool groups
- Computers — 26 tools
- Computer Inventory — 10 tools
- Computer Agents — 8 tools
- Software — 22 tools
- Software Versions — 12 tools
- Licenses — 10 tools
- Script Catalog & Functions — 6 tools
- Script Execution — 9 tools
- Scripts — 26 tools
- Deployments — 32 tools
- Deployment Change Requests — 8 tools
- Maintenance Actions — 11 tools
- Maintenance Sessions — 17 tools
- Maintenance Tasks — 20 tools
- Inventory Tasks — 6 tools
- Tags — 7 tools
- Tenants — 23 tools
- Provider Links — 19 tools
- Provider Link Assets — 16 tools
- Provider Agents — 9 tools
- Provider Clients & Agents — 28 tools
- Provider Types — 5 tools
- Personal Access Tokens — 4 tools
- Persons — 13 tools
- Users — 13 tools
- Roles, Groups & Permissions — 24 tools
- User Role Assignments — 12 tools
- Identity & Azure — 18 tools
- OAuth & Syncs — 13 tools
- Media — 17 tools
- Schedules — 13 tools
- Dynamic Provider Types — 16 tools
- Diagnostics & Metrics — 15 tools
- Brandings — 9 tools
- Maintenance Email Jobs — 3 tools
- Notifications — 6 tools
- Notification Preferences — 5 tools
- SMTP Configuration — 7 tools
- Billing — 14 tools
- System — 23 tools
Computers
immy_add_tags_to_computers details
immy_add_tags_to_computers details
[ImmyBot] Add one or more tags to a set of computers (bulk). Body typically carries the computer ids and the tag ids to apply. Tag ids come from immy_list_tags; computer ids from immy_list_computers.
immy_bulk_delete_computers details
immy_bulk_delete_computers details
[ImmyBot] Permanently delete multiple computers (bulk). DESTRUCTIVE — removes the computer records; recover with immy_computers_restore only where ImmyBot supports soft-delete. Body carries the list of computer ids to delete (from immy_list_computers).
immy_computers_change_tenant details
immy_computers_change_tenant details
[ImmyBot] Move one or more computers to a different tenant. Body carries the computer ids and the destination tenant id (from immy_list_tenants). This reassigns which customer the endpoints belong to.
immy_computers_exclude_from_maintenance details
immy_computers_exclude_from_maintenance details
[ImmyBot] Exclude a computer from maintenance (it will be skipped by maintenance sessions). computerId comes from immy_list_computers. Body carries the exclusion options (e.g. reason/duration) as ImmyBot's schema allows; pass for defaults.
immy_computers_notes details
immy_computers_notes details
[ImmyBot] Set/update the notes on a computer. computerId comes from immy_list_computers. Body carries the notes payload (e.g. {"notes":"..."}).
immy_computers_reinventory details
immy_computers_reinventory details
[ImmyBot] Trigger a reinventory of a computer (re-collect its software/inventory data). computerId comes from immy_list_computers. This action takes no options — pass for the body.
immy_computers_restore details
immy_computers_restore details
[ImmyBot] Restore previously (soft-)deleted computers. Body is a JSON array of the computer ids to restore. Counterpart of immy_bulk_delete_computers.
immy_computers_set_to_needs_onboarding details
immy_computers_set_to_needs_onboarding details
[ImmyBot] Flag a computer as needing onboarding (re-enters the onboarding pipeline). computerId comes from immy_list_computers. This action takes no options — pass for the body. Inverse of immy_computers_skip_onboarding.
immy_computers_skip_onboarding details
immy_computers_skip_onboarding details
[ImmyBot] Mark computers to skip onboarding. Body is a JSON array of skip-onboarding requests (each identifying a computer and its skip options). See immy_list_computers_onboarding for the onboarding queue and immy_computers_set_to_needs_onboarding for the inverse.
immy_computers_update_additional_persons details
immy_computers_update_additional_persons details
[ImmyBot] Update the additional (secondary) persons associated with a computer. computerId comes from immy_list_computers; person ids from immy_list_persons. Body carries the additional-person assignments. See also immy_computers_update_primary_person.
immy_computers_update_primary_person details
immy_computers_update_primary_person details
[ImmyBot] Update the primary person associated with a computer (its main user). computerId comes from immy_list_computers; person id from immy_list_persons. Body carries the primary-person assignment. See also immy_computers_update_additional_persons.
immy_get_computers details
immy_get_computers details
[ImmyBot] Get a single computer by id, including its default detail (sessions, primary/additional persons and provider-agent data as ImmyBot resolves them). computerId comes from immy_list_computers / immy_list_computers_paged.
immy_list_computers details
immy_list_computers details
[ImmyBot] List managed computers (basic view). Only pageSize is supported here (capped at 100). For server-side filtering, sorting or paging use immy_list_computers_paged or immy_list_computers_dx; for per-computer detail use immy_get_computers.
immy_list_computers_agent_status details
immy_list_computers_agent_status details
[ImmyBot] List computers with their agent connectivity/health status (DevExtreme grid feed). filters/sorts use DevExtreme syntax: filters is a JSON filter array (e.g. ["name","contains","srv"]) and sorts a JSON sort array (e.g. [{"selector":"name","desc":false}]). pageSize is capped at 100. See also immy_list_computers_status for a single computer.
immy_list_computers_device_update_form_data details
immy_list_computers_device_update_form_data details
[ImmyBot] Get the device-update form data for a computer (the fields/options used to drive a device update). computerId comes from immy_list_computers.
immy_list_computers_dx details
immy_list_computers_dx details
[ImmyBot] List computers via the raw DevExtreme grid feed. Accepts native DevExtreme load options: skip, take (capped at 100), filter (JSON filter array string) and sort (JSON sort array string). Set requireTotalCount=true to include the total row count in the response.
immy_list_computers_events details
immy_list_computers_events details
[ImmyBot] List the event history for a computer. The endpoint pages via skip/take only (no server-side filter/sort); page/pageSize are mapped onto them and pageSize is capped at 100. computerId comes from immy_list_computers.
immy_list_computers_export details
immy_list_computers_export details
[ImmyBot] Export the computers grid to an XLSX spreadsheet. The binary is uploaded to StackJack blob storage and returned as a short-lived (~15 minute) read-only SAS URL envelope {sasUrl, contentType, suggestedFilename, sizeBytes, expiresAt} — fetch the file from sasUrl within the window; do NOT decode the URL as content. filters/sorts use DevExtreme syntax.
immy_list_computers_my details
immy_list_computers_my details
[ImmyBot] List the computers scoped to the calling identity/session. Takes no parameters. For the full tenant inventory use immy_list_computers or immy_list_computers_paged.
immy_list_computers_onboarding details
immy_list_computers_onboarding details
[ImmyBot] List computers currently in the onboarding pipeline (awaiting or undergoing onboarding). Takes no parameters. Related actions: immy_computers_skip_onboarding, immy_computers_set_to_needs_onboarding.
immy_list_computers_paged details
immy_list_computers_paged details
[ImmyBot] List computers with DevExtreme server-side paging, filtering and sorting — the richer counterpart to immy_list_computers. filter/sort use DevExtreme syntax (JSON array strings). pageSize is capped at 100. Some vendor convenience boolean flags (staleOnly, onboardingOnly, orphanedOnly and similar) are not exposed by this tool; express the equivalent constraint through the DevExtreme filter instead.
immy_list_computers_parent_tenant_info details
immy_list_computers_parent_tenant_info details
[ImmyBot] Get the parent-tenant information for a computer (the tenant hierarchy context the computer belongs to). computerId comes from immy_list_computers.
immy_list_computers_status details
immy_list_computers_status details
[ImmyBot] Get the current status of a single computer (online/agent/maintenance state). computerId comes from immy_list_computers. For a fleet-wide view use immy_list_computers_agent_status.
immy_remove_tags_from_computers details
immy_remove_tags_from_computers details
[ImmyBot] Remove one or more tags from a set of computers (bulk). Body carries the computer ids and the tag ids to remove. Counterpart of immy_add_tags_to_computers.
immy_resolve_computer_onboarding_target_assignments details
immy_resolve_computer_onboarding_target_assignments details
[ImmyBot] Resolve the onboarding target-assignments (deployments) that can be overridden for a computer — a preview used before onboarding. computerId comes from immy_list_computers. Read-only.
immy_update_computers details
immy_update_computers details
[ImmyBot] Update a computer (PUT). computerId comes from immy_list_computers. Body is the computer object with the fields to change (e.g. name, notes, tenant assignment as ImmyBot's schema allows).
Computer Inventory
immy_computers_exclude_from_user_affinity details
immy_computers_exclude_from_user_affinity details
[ImmyBot] Exclude a single computer from user-affinity tracking. computerId comes from immy_list_computers. Pass for the body unless ImmyBot expects exclusion options. For a bulk operation use immy_computers_set_excluded_from_user_affinity.
immy_computers_set_excluded_from_user_affinity details
immy_computers_set_excluded_from_user_affinity details
[ImmyBot] Bulk set whether a set of computers are excluded from user-affinity tracking. Body carries the computer ids and the excluded flag. For a single computer use immy_computers_exclude_from_user_affinity.
immy_get_computers_inventory_script_results details
immy_get_computers_inventory_script_results details
[ImmyBot] Get the results of a specific inventory script for a computer, keyed by inventoryKey. computerId comes from immy_list_computers; inventoryKey identifies which inventory-task/script's output to return.
immy_list_computers_detected_computer_software details
immy_list_computers_detected_computer_software details
[ImmyBot] List the detected (installed) software for a single computer. computerId comes from immy_list_computers. Returns the full detected-software set (no server-side paging).
immy_list_computers_inventory details
immy_list_computers_inventory details
[ImmyBot] List the collected computer inventory (DevExtreme grid feed). filters/sorts use DevExtreme syntax (JSON array strings); pageSize is capped at 100. For a single computer's detected software use immy_list_computers_detected_computer_software.
immy_list_computers_inventory_export details
immy_list_computers_inventory_export details
[ImmyBot] Export the computer-inventory grid to an XLSX spreadsheet. Returns a short-lived (~15 minute) read-only SAS URL envelope {sasUrl, contentType, suggestedFilename, sizeBytes, expiresAt} — fetch the file from sasUrl within the window; do NOT decode the URL as content. filters/sorts use DevExtreme syntax.
immy_list_computers_inventory_software_search_by_name details
immy_list_computers_inventory_software_search_by_name details
[ImmyBot] Search the software inventory across computers by (partial) product name. Returns matching installed-software records. Use immy_list_computers_inventory_software_search_by_upgrade_code to search by MSI upgrade code instead.
immy_list_computers_inventory_software_search_by_upgrade_code details
immy_list_computers_inventory_software_search_by_upgrade_code details
[ImmyBot] Search the software inventory across computers by MSI upgrade code. Returns matching installed-software records. Use immy_list_computers_inventory_software_search_by_name to search by product name instead.
immy_list_computers_user_affinities details
immy_list_computers_user_affinities details
[ImmyBot] List computer↔user affinities (which persons are associated with which computers, inferred from usage). DevExtreme grid feed — filters/sorts use DevExtreme syntax (JSON array strings); pageSize is capped at 100.
immy_list_computers_user_affinities_export details
immy_list_computers_user_affinities_export details
[ImmyBot] Export the computer user-affinity grid to an XLSX spreadsheet. Returns a short-lived (~15 minute) read-only SAS URL envelope {sasUrl, contentType, suggestedFilename, sizeBytes, expiresAt} — fetch the file from sasUrl within the window; do NOT decode the URL as content. filters/sorts use DevExtreme syntax.
Computer Agents
immy_computers_ephemeral_agent_circuit_breaker_reset details
immy_computers_ephemeral_agent_circuit_breaker_reset details
[ImmyBot] Reset the ephemeral-agent circuit breaker for a computer (clears the tripped state so agent launches are retried). computerId comes from immy_list_computers. This action takes no options — pass for the body. Inspect state first with immy_list_computers_ephemeral_agent_circuit_breaker.
immy_computers_registry_keys details
immy_computers_registry_keys details
[ImmyBot] Enumerate the registry sub-keys under a supplied path on a computer (read-only; POST is used to carry the query path). computerId comes from immy_list_computers. Body identifies the hive/path to enumerate (e.g. {"path":"HKLM:\SOFTWARE"}). Use immy_computers_registry_values to read the values within a key.
immy_computers_registry_values details
immy_computers_registry_values details
[ImmyBot] Read the registry values under a supplied key on a computer (read-only; POST is used to carry the query key). computerId comes from immy_list_computers. Body identifies the hive/key to read (e.g. {"path":"HKLM:\SOFTWARE\..."}). Use immy_computers_registry_keys to list sub-keys first.
immy_end_ephemeral_agent_session details
immy_end_ephemeral_agent_session details
[ImmyBot] End (terminate) the live ephemeral-agent session on a computer. DESTRUCTIVE — the active agent session is torn down immediately; any in-flight work on that session is interrupted. computerId comes from immy_list_computers. Launch a new session with immy_launch_ephemeral_agent.
immy_launch_ephemeral_agent details
immy_launch_ephemeral_agent details
[ImmyBot] Launch a short-lived ephemeral agent on a computer (an ACTION despite the GET verb — it establishes a live agent session, so it is NOT read-only). computerId comes from immy_list_computers. Check state with immy_list_computers_ephemeral_agent and tear down with immy_end_ephemeral_agent_session.
immy_list_computers_ephemeral_agent details
immy_list_computers_ephemeral_agent details
[ImmyBot] Get the current ephemeral-agent state for a computer (whether a short-lived agent session is active and its details). computerId comes from immy_list_computers. Launch one with immy_launch_ephemeral_agent; end one with immy_end_ephemeral_agent_session.
immy_list_computers_ephemeral_agent_circuit_breaker details
immy_list_computers_ephemeral_agent_circuit_breaker details
[ImmyBot] Get the ephemeral-agent circuit-breaker state for a computer (whether repeated agent-launch failures have tripped the breaker). computerId comes from immy_list_computers. Reset it with immy_computers_ephemeral_agent_circuit_breaker_reset.
immy_list_computers_provider_links_screen_share_url details
immy_list_computers_provider_links_screen_share_url details
Software
immy_delete_software_global details
immy_delete_software_global details
[ImmyBot] Delete a global software item by softwareIdentifier, including all its versions. Deployments (target-assignments) referencing it will break. Cannot be undone. Returns the raw ImmyBot result.
immy_delete_software_local details
immy_delete_software_local details
[ImmyBot] Delete a local software item by softwareIdentifier, including all its versions. Deployments (target-assignments) referencing it will break. Cannot be undone. Returns the raw ImmyBot result.
immy_get_software_global details
immy_get_software_global details
[ImmyBot] Get a single global software item by softwareIdentifier (from immy_list_software_global). Returns the raw ImmyBot software JSON. Use immy_list_software_global_versions for its version list.
immy_get_software_local details
immy_get_software_local details
[ImmyBot] Get a single local software item by softwareIdentifier (from immy_list_software_local). Returns the raw ImmyBot software JSON. Use immy_list_software_local_versions for its version list.
immy_list_software_global details
immy_list_software_global details
[ImmyBot] List global (shared/vendor-maintained) software items, optionally filtered with a Sieve `filters` expression. Global software is available to every tenant. Returns raw ImmyBot JSON. Use immy_get_software_global for one item, immy_list_software_global_versions for its versions, or immy_list_software_local for instance-authored software.
immy_list_software_global_latest details
immy_list_software_global_latest details
[ImmyBot] Get the latest version of a global software item by softwareIdentifier (from immy_list_software_global). Returns the raw ImmyBot version JSON for the newest version. Use immy_list_software_global_versions for the full history.
immy_list_software_local details
immy_list_software_local details
[ImmyBot] List local (instance-authored) software items, optionally filtered with a Sieve `filters` expression. Local software is defined inside this ImmyBot instance and can be migrated to global. Returns raw ImmyBot JSON. Use immy_get_software_local for one item, or immy_list_software_global for shared software.
immy_list_software_local_authorization details
immy_list_software_local_authorization details
[ImmyBot] Get the authorization (tenant/scope access) configuration for a local software item by softwareIdentifier. Shows which tenants may use it. Returns raw ImmyBot JSON. Use immy_software_local_authorization to change it.
immy_list_software_local_latest details
immy_list_software_local_latest details
[ImmyBot] Get the latest version of a local software item by softwareIdentifier (from immy_list_software_local). Returns the raw ImmyBot version JSON for the newest version. Use immy_list_software_local_versions for the full history.
immy_list_software_local_migrate_local_to_global_what_if details
immy_list_software_local_migrate_local_to_global_what_if details
[ImmyBot] Preview (what-if) migrating a local software item to the global catalog by softwareIdentifier — reports what would change WITHOUT migrating. Run this before immy_software_local_migrate_local_to_global. Returns the raw ImmyBot preview JSON.
immy_patch_software_global details
immy_patch_software_global details
[ImmyBot] Partially update a global software item by softwareIdentifier. Provide a JSON object body (fieldsJson) with only the fields to change (JSON merge-patch semantics). Returns the updated software JSON.
immy_patch_software_local details
immy_patch_software_local details
[ImmyBot] Partially update a local software item by softwareIdentifier. Provide a JSON object body (fieldsJson) with only the fields to change (JSON merge-patch semantics). Returns the updated software JSON.
immy_software_global details
immy_software_global details
[ImmyBot] Create a global software item. Provide a JSON object body (fieldsJson) with the software definition (name, install/detection method, etc.). For a quick minimal create use immy_software_global_fast_create; to upload the installer binary use immy_software_global_upload; add versions with immy_create_global_software_version. Returns the created software JSON.
immy_software_global_analyze details
immy_software_global_analyze details
[ImmyBot] Analyze a global software definition WITHOUT saving it — a read-only preview that returns detection/install evaluation for the supplied definition. Provide a JSON object body (fieldsJson) describing the software/version to analyze. POST is used only to carry the body; nothing is created. Returns the raw analysis JSON.
immy_software_global_fast_create details
immy_software_global_fast_create details
[ImmyBot] Fast-create a global software item from a minimal definition (ImmyBot infers install/detection defaults). Provide a JSON object body (fieldsJson) — typically just name and package/source hints. Use immy_software_global for full control. Returns the created software JSON.
immy_software_global_upload details
immy_software_global_upload details
[ImmyBot] Upload an installer binary for global software (multipart/form-data). Provide the file bytes base64-encoded (base64Content) and a fileName; the file is posted as the `file` form part. Returns the raw ImmyBot upload result JSON (reference the uploaded payload when creating a version with immy_create_global_software_version).
immy_software_local details
immy_software_local details
[ImmyBot] Create a local (instance-authored) software item. Provide a JSON object body (fieldsJson) with the software definition. For a quick minimal create use immy_software_local_fast_create; to upload the installer use immy_software_local_upload; add versions with immy_create_local_software_version. Returns the created software JSON.
immy_software_local_analyze details
immy_software_local_analyze details
[ImmyBot] Analyze a local software definition WITHOUT saving it — a read-only preview returning detection/install evaluation for the supplied definition. Provide a JSON object body (fieldsJson). POST is used only to carry the body; nothing is created. Returns the raw analysis JSON.
immy_software_local_authorization details
immy_software_local_authorization details
[ImmyBot] Set the authorization (tenant/scope access) for a local software item by softwareIdentifier. Provide a JSON object body (fieldsJson) describing which tenants/scopes may use it. Read the current config first with immy_list_software_local_authorization. Returns the raw ImmyBot result.
immy_software_local_fast_create details
immy_software_local_fast_create details
[ImmyBot] Fast-create a local software item from a minimal definition (ImmyBot infers install/detection defaults). Provide a JSON object body (fieldsJson) — typically just name and package/source hints. Use immy_software_local for full control. Returns the created software JSON.
immy_software_local_migrate_local_to_global details
immy_software_local_migrate_local_to_global details
[ImmyBot] Migrate a local software item to the global catalog by softwareIdentifier, making it shared across the instance. Preview the effect first with immy_list_software_local_migrate_local_to_global_what_if. The optional fieldsJson carries migration options (usually none — leave as ). Returns the raw ImmyBot result.
immy_software_local_upload details
immy_software_local_upload details
[ImmyBot] Upload an installer binary for local software (multipart/form-data). Provide the file bytes base64-encoded (base64Content) and a fileName; the file is posted as the `file` form part. Returns the raw ImmyBot upload result JSON (reference the uploaded payload when creating a version with immy_create_local_software_version).
Software Versions
immy_create_global_software_version details
immy_create_global_software_version details
[ImmyBot] Add a new version to a global software item (softwareIdentifier from immy_list_software_global). Provide a JSON object body (fieldsJson) with the semanticVersion, install/detection metadata, and payload reference. To upload the binary, use immy_software_global_upload. Returns the created version JSON.
immy_create_local_software_version details
immy_create_local_software_version details
[ImmyBot] Add a new version to a local software item (softwareIdentifier from immy_list_software_local). Provide a JSON object body (fieldsJson) with the semanticVersion, install/detection metadata, and payload reference. To upload the binary, use immy_software_local_upload. Returns the created version JSON.
immy_delete_software_global_versions details
immy_delete_software_global_versions details
[ImmyBot] Delete a version from a global software item (softwareIdentifier + semanticVersion). Deployments pinned to this version will no longer resolve. Cannot be undone. Returns the raw ImmyBot result.
immy_delete_software_local_versions details
immy_delete_software_local_versions details
[ImmyBot] Delete a version from a local software item (softwareIdentifier + semanticVersion). Deployments pinned to this version will no longer resolve. Cannot be undone. Returns the raw ImmyBot result.
immy_get_software_global_versions details
immy_get_software_global_versions details
[ImmyBot] Get a single global software version by softwareIdentifier + semanticVersion (both from immy_list_software_global_versions). Returns the raw ImmyBot version JSON, including install metadata.
immy_get_software_local_versions details
immy_get_software_local_versions details
[ImmyBot] Get a single local software version by softwareIdentifier + semanticVersion (both from immy_list_software_local_versions). Returns the raw ImmyBot version JSON, including install metadata.
immy_list_software_global_versions details
immy_list_software_global_versions details
[ImmyBot] List the versions of a global (shared/vendor) software item by its softwareIdentifier (from immy_list_software_global / immy_get_software_global). Returns raw ImmyBot JSON. Use immy_get_software_global_versions for one version, or immy_list_software_global_latest for the newest.
immy_list_software_global_versions_request_download details
immy_list_software_global_versions_request_download details
[ImmyBot] Request a download URL for a global software version's install payload by softwareIdentifier + semanticVersion. Returns a JSON body containing the URL string — a normal passthrough read, not a binary export. Fetch the URL out-of-band to retrieve the payload.
immy_list_software_local_versions details
immy_list_software_local_versions details
[ImmyBot] List the versions of a local (per-instance) software item by its softwareIdentifier (from immy_list_software_local / immy_get_software_local). Returns raw ImmyBot JSON. Use immy_get_software_local_versions for one version, or immy_list_software_local_latest for the newest.
immy_list_software_local_versions_request_download details
immy_list_software_local_versions_request_download details
[ImmyBot] Request a download URL for a local software version's install payload by softwareIdentifier + semanticVersion. Returns a JSON body containing the URL string — a normal passthrough read, not a binary export. Fetch the URL out-of-band to retrieve the payload.
immy_patch_software_global_versions details
immy_patch_software_global_versions details
[ImmyBot] Partially update a global software version (softwareIdentifier + semanticVersion). Provide a JSON object body (fieldsJson) with only the fields to change (JSON merge-patch semantics). Returns the updated version JSON.
immy_patch_software_local_versions details
immy_patch_software_local_versions details
[ImmyBot] Partially update a local software version (softwareIdentifier + semanticVersion). Provide a JSON object body (fieldsJson) with only the fields to change (JSON merge-patch semantics). Returns the updated version JSON.
Licenses
immy_delete_licenses details
immy_delete_licenses details
[ImmyBot] Delete a software license by id (from immy_list_licenses). This permanently removes the license and its stored key/file; deployments that reference it will no longer activate. Cannot be undone. Returns the raw ImmyBot result.
immy_get_licenses details
immy_get_licenses details
[ImmyBot] Get a single software license by id (from immy_list_licenses). Returns the raw ImmyBot license JSON. Use immy_list_licenses_request_download for a download URL to the license file, if any.
immy_licenses details
immy_licenses details
[ImmyBot] Create a software license. Provide a JSON object body (fieldsJson) — typically name, softwareId (from immy_list_software_global/immy_list_software_local), the license key/value, and any tenant/scope fields. To attach a license FILE, create the license then use immy_licenses_upload. Returns the created license JSON.
immy_licenses_upload details
immy_licenses_upload details
[ImmyBot] Upload a license file (multipart/form-data). Provide the file bytes base64-encoded (base64Content) and a fileName. The file is decoded and posted as the `file` form part. Returns the raw ImmyBot upload result JSON. Pair with immy_licenses to bind the uploaded file to a license record.
immy_list_chocolatey_find_packages_by_id details
immy_list_chocolatey_find_packages_by_id details
[ImmyBot] Look up Chocolatey community-feed packages by exact package id (e.g. "googlechrome", "7zip"). Use this when authoring a Chocolatey-backed global/local software item to confirm the package id and available versions. Returns the raw Chocolatey search JSON. See immy_list_chocolatey_search for a fuzzy term search.
immy_list_chocolatey_search details
immy_list_chocolatey_search details
[ImmyBot] Fuzzy-search the Chocolatey community feed by term (matches package id/title). Use this to discover the correct package id before authoring a Chocolatey-backed software item; then confirm with immy_list_chocolatey_find_packages_by_id. Returns the raw Chocolatey search JSON.
immy_list_licenses details
immy_list_licenses details
[ImmyBot] List software licenses, optionally filtered with a Sieve `filters` expression (e.g. "name@=Adobe"). Each license binds an activation key/file to software applied during deployment. Returns raw ImmyBot JSON. Use immy_list_licenses_dx for the grid/DevExtreme feed, or immy_get_licenses for a single license.
immy_list_licenses_dx details
immy_list_licenses_dx details
[ImmyBot] DevExtreme grid feed for the licenses table (skip/take paging plus DevExtreme filter/sort). This backs the ImmyBot UI grid; prefer immy_list_licenses for straightforward listing. Returns the raw DevExtreme envelope {data, totalCount}.
immy_list_licenses_request_download details
immy_list_licenses_request_download details
[ImmyBot] Request a download URL for a license's uploaded file by license id (from immy_list_licenses). Returns a JSON body containing the URL string — this is a normal passthrough read, not a binary export. Fetch the URL out-of-band to retrieve the file.
immy_update_licenses details
immy_update_licenses details
[ImmyBot] Update (full replace) a software license by id (from immy_list_licenses). Provide the complete JSON object body (fieldsJson) — omitted fields are cleared, so fetch with immy_get_licenses first and send the merged object. Returns the updated license JSON.
Script Catalog & Functions
immy_list_metascript_catalog_describe details
immy_list_metascript_catalog_describe details
[ImmyBot] List the metascript catalog with full descriptions — the reusable ImmyBot metascript building blocks available to compose scripts and maintenance tasks. Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Use immy_list_metascript_catalog_search for a lighter keyword search.
immy_list_metascript_catalog_search details
immy_list_metascript_catalog_search details
[ImmyBot] Search the metascript catalog by keyword. Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Use immy_list_metascript_catalog_describe for full catalog entry descriptions.
immy_list_scripts_functions details
immy_list_scripts_functions details
[ImmyBot] List the PowerShell/metascript functions exposed to scripts (the built-in function library scripts can call). Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Validate a function's PowerShell syntax with immy_scripts_functions_syntax.
immy_list_scripts_language_service_language details
immy_list_scripts_language_service_language details
[ImmyBot] Get the language/analysis state for an active script language-service terminal. terminalId comes from immy_scripts_language_service_start. Read-only editor support surface.
immy_scripts_functions_syntax details
immy_scripts_functions_syntax details
[ImmyBot] Analyze the syntax of a script function (read-only static analysis — a POST that inspects, not a write). Body carries the function source to check; returns parse/syntax diagnostics. No script is created or run.
immy_scripts_language_service_start details
immy_scripts_language_service_start details
[ImmyBot] Start a script language-service session (editor/analysis backend), returning a terminalId used by immy_list_scripts_language_service_language. Body carries the session/init options. This allocates a server-side session — a write.
Script Execution
immy_cancel_debug_script_run details
immy_cancel_debug_script_run details
[ImmyBot] Cancel an in-progress debug script run identified by cancellationId. This aborts a running execution — flagged Destructive because it terminates work in flight. Body carries any additional cancel options.
immy_list_scripts_disabled_preflight_scripts details
immy_list_scripts_disabled_preflight_scripts details
[ImmyBot] List the preflight scripts currently disabled (preflight scripts run before maintenance to decide applicability). Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Toggle enablement with immy_scripts_set_preflight_script_enablement.
immy_scripts_default_variables details
immy_scripts_default_variables details
[ImmyBot] Resolve the default variables ImmyBot would supply for a script (a POST that computes/reads defaults — it does not run the script or change state). Body carries the script/context to evaluate; returns the resolved variable set.
immy_scripts_does_script_have_param_block details
immy_scripts_does_script_have_param_block details
[ImmyBot] Inspect a script and report whether it declares a PowerShell param() block (read-only static analysis via POST). Body carries the script source; returns a boolean/analysis result. No script is created or run.
immy_scripts_run details
immy_scripts_run details
[ImmyBot] Execute a script against target computers/tenants. This RUNS PowerShell/metascript code on managed endpoints and can change system state — flagged Destructive so it requires explicit approval. Body carries the script reference, target selection, and parameters. Preview/validate first with immy_scripts_syntax_check and immy_scripts_validate_param_block_parameters.
immy_scripts_run_adhoc_metascript details
immy_scripts_run_adhoc_metascript details
[ImmyBot] Execute an ad-hoc metascript (inline PowerShell/metascript code, not a saved script) against targets. This RUNS arbitrary code on managed endpoints and can change system state — flagged Destructive so it requires explicit approval. Body carries the metascript source, target selection, and parameters.
immy_scripts_set_preflight_script_enablement details
immy_scripts_set_preflight_script_enablement details
[ImmyBot] Enable or disable a preflight script. Body carries the script identifier and desired enabled state. Changes which preflight checks run before maintenance — a configuration write. Use immy_list_scripts_disabled_preflight_scripts to see current state.
immy_scripts_syntax_check details
immy_scripts_syntax_check details
[ImmyBot] Static syntax check of a script (a POST that parses and returns diagnostics — it does not run the script). Body carries the script source; returns parse errors/warnings.
immy_scripts_validate_param_block_parameters details
immy_scripts_validate_param_block_parameters details
[ImmyBot] Validate a set of parameters against a script's param() block (read-only validation via POST — it checks, it does not persist anything). Body carries the param block and candidate parameter values; returns validation results. Note: immy_users_invalidate_cache is a DIFFERENT, write operation despite the similar name.
Scripts
immy_create_global_script details
immy_create_global_script details
[ImmyBot] Create a new global script (shared platform-wide). Body carries the script name, source, and metadata. Validate the source first with immy_scripts_syntax_check.
immy_create_local_script details
immy_create_local_script details
[ImmyBot] Create a new local script (tenant-scoped). Body carries the script name, source, and metadata. Validate the source first with immy_scripts_syntax_check.
immy_delete_scripts_global details
immy_delete_scripts_global details
[ImmyBot] Permanently delete a global script. Any maintenance task or deployment referencing it loses that script — this cannot be undone. scriptId comes from immy_list_scripts_global; check immy_list_scripts_global_references first.
immy_delete_scripts_local details
immy_delete_scripts_local details
[ImmyBot] Permanently delete a local script. Any maintenance task or deployment referencing it loses that script — this cannot be undone. scriptId comes from immy_list_scripts_local; check immy_list_scripts_local_references first.
immy_get_scripts_global details
immy_get_scripts_global details
[ImmyBot] Get a single global script by id, including its source and metadata. scriptId comes from immy_list_scripts_global.
immy_get_scripts_local details
immy_get_scripts_local details
[ImmyBot] Get a single local script by id, including its source and metadata. scriptId comes from immy_list_scripts_local.
immy_list_scripts_dx details
immy_list_scripts_dx details
[ImmyBot] List scripts via the DevExtreme grid feed (the data source behind the ImmyBot scripts grid). Uses DevExtreme paging: skip/take (take clamped to 100) plus optional filter/sort and requireTotalCount. For a standard list use immy_list_scripts_global or immy_list_scripts_local.
immy_list_scripts_global details
immy_list_scripts_global details
[ImmyBot] List global scripts (shared platform-wide). Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Each entry carries a scriptId used by immy_get_scripts_global, immy_update_global_script, and immy_delete_scripts_global.
immy_list_scripts_global_audit details
immy_list_scripts_global_audit details
[ImmyBot] List the audit history (change events) for a global script. scriptId comes from immy_list_scripts_global. Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Use immy_list_scripts_global_audit_summaries for a rolled-up view.
immy_list_scripts_global_audit_summaries details
immy_list_scripts_global_audit_summaries details
[ImmyBot] List rolled-up audit summaries for a global script (aggregated change events). scriptId comes from immy_list_scripts_global. Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100.
immy_list_scripts_global_names details
immy_list_scripts_global_names details
[ImmyBot] List just the id+name pairs of global scripts (a lightweight pick-list for referencing scripts). Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100.
immy_list_scripts_global_references details
immy_list_scripts_global_references details
[ImmyBot] List the entities (maintenance tasks, deployments, etc.) that reference a global script. scriptId comes from immy_list_scripts_global. Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Check references before deleting with immy_delete_scripts_global.
immy_list_scripts_local details
immy_list_scripts_local details
[ImmyBot] List local scripts (tenant-scoped). Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Each entry carries a scriptId used by immy_get_scripts_local, immy_update_local_script, and immy_delete_scripts_local.
immy_list_scripts_local_audit details
immy_list_scripts_local_audit details
[ImmyBot] List the audit history (change events) for a local script. scriptId comes from immy_list_scripts_local. Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Use immy_list_scripts_local_audit_summaries for a rolled-up view.
immy_list_scripts_local_audit_summaries details
immy_list_scripts_local_audit_summaries details
[ImmyBot] List rolled-up audit summaries for a local script (aggregated change events). scriptId comes from immy_list_scripts_local. Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100.
immy_list_scripts_local_authorization details
immy_list_scripts_local_authorization details
[ImmyBot] Get the authorization (who may view/run/edit) for a local script. scriptId comes from immy_list_scripts_local. Set authorization with immy_scripts_local_authorization.
immy_list_scripts_local_migrate_local_to_global_what_if details
immy_list_scripts_local_migrate_local_to_global_what_if details
[ImmyBot] Preview what would happen if a local script were migrated to a global script (a read-only what-if — nothing is migrated). scriptId comes from immy_list_scripts_local. Perform the migration with immy_scripts_local_migrate_local_to_global.
immy_list_scripts_local_names details
immy_list_scripts_local_names details
[ImmyBot] List just the id+name pairs of local scripts (a lightweight tenant-scoped pick-list). Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100.
immy_list_scripts_local_references details
immy_list_scripts_local_references details
[ImmyBot] List the entities that reference a local script. scriptId comes from immy_list_scripts_local. Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100. Check references before deleting with immy_delete_scripts_local.
immy_list_scripts_references_count details
immy_list_scripts_references_count details
[ImmyBot] Get the reference counts for scripts (how many maintenance tasks/deployments reference each script). No parameters. Use immy_list_scripts_global_references / immy_list_scripts_local_references for the detailed referencing entities of one script.
immy_list_scripts_search details
immy_list_scripts_search details
[ImmyBot] Search across scripts (global + local) by keyword. Sieve-paged (Page/pageSize/Filters/Sorts); pageSize is clamped to 100.
immy_scripts_duplicate details
immy_scripts_duplicate details
[ImmyBot] Duplicate an existing script into a new script. Body carries the source scriptId and any new-script overrides (e.g. name). Creates a new script — a write.
immy_scripts_local_authorization details
immy_scripts_local_authorization details
[ImmyBot] Set the authorization (who may view/run/edit) for a local script. scriptId comes from immy_list_scripts_local; body carries the authorization grants. Read current state with immy_list_scripts_local_authorization.
immy_scripts_local_migrate_local_to_global details
immy_scripts_local_migrate_local_to_global details
[ImmyBot] Migrate a local (tenant-scoped) script to a global (platform-wide) script. scriptId comes from immy_list_scripts_local; body carries migration options. Preview the effect first with immy_list_scripts_local_migrate_local_to_global_what_if.
immy_update_global_script details
immy_update_global_script details
[ImmyBot] Update an existing global script (POST-based update, not a PATCH). scriptId comes from immy_list_scripts_global; body carries the updated script fields. Validate the source first with immy_scripts_syntax_check.
immy_update_local_script details
immy_update_local_script details
[ImmyBot] Update an existing local script (POST-based update, not a PATCH). scriptId comes from immy_list_scripts_local; body carries the updated script fields. Validate the source first with immy_scripts_syntax_check.
Deployments
immy_delete_target_assignments details
immy_delete_target_assignments details
[ImmyBot] Permanently delete a deployment (target assignment) by its id (from immy_list_target_assignments). This removes the deployment and cannot be undone.
immy_delete_target_assignments_global details
immy_delete_target_assignments_global details
[ImmyBot] Permanently delete a global (cross-tenant) deployment by its id (from immy_list_target_assignments_global). This removes the deployment from every tenant it applied to and cannot be undone.
immy_get_computer_optional_target_assignment_approvals details
immy_get_computer_optional_target_assignment_approvals details
[ImmyBot] Get the optional (opt-in) deployment approvals available for a specific computer, by computerId (from immy_list_computers). Optional deployments require per-computer approval before they run; this shows which are pending/available. Grant one with immy_target_assignments_optional_target_assignment_approvals.
immy_get_target_assignments details
immy_get_target_assignments details
[ImmyBot] Get a single deployment (target assignment) by its id (from immy_list_target_assignments). Returns the full deployment definition — maintenance item, targets, desired state, schedule, and scope.
immy_get_target_assignments_global details
immy_get_target_assignments_global details
[ImmyBot] Get a single global (cross-tenant) deployment by its id (from immy_list_target_assignments_global). Returns the full deployment definition.
immy_list_target_assignments details
immy_list_target_assignments details
[ImmyBot] List deployments (target assignments) across the ImmyBot instance. A deployment binds a maintenance item (software/task/script) to targets (tenant, tag, computer, person, or MSP). Supports Sieve paging and filtering (Page, pageSize up to 100, Filters, Sorts). Use immy_get_target_assignments for one deployment, immy_list_target_assignments_global for cross-tenant deployments.
immy_list_target_assignments_global details
immy_list_target_assignments_global details
[ImmyBot] List global (cross-tenant) deployments — target assignments that apply across every tenant rather than to a single one. Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts). Use immy_get_target_assignments_global for one global deployment.
immy_list_target_assignments_global_type details
immy_list_target_assignments_global_type details
[ImmyBot] Get the maintenance-item type (software / maintenance task / script) of a global deployment by its id (from immy_list_target_assignments_global). Lightweight lookup used to disambiguate which item family the deployment targets.
immy_list_target_assignments_maintenance_item_orders details
immy_list_target_assignments_maintenance_item_orders details
[ImmyBot] List the ordering of maintenance items as resolved by deployments — the sequence in which items run during maintenance. Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts). Change the order with immy_target_assignments_update_maintenance_item_order.
immy_list_target_assignments_recommended_approvals details
immy_list_target_assignments_recommended_approvals details
[ImmyBot] List recommended deployment approvals — deployments ImmyBot recommends approving based on current state. Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts). Apply the recommendations with immy_target_assignments_recommended_approvals_update.
immy_list_target_assignments_type details
immy_list_target_assignments_type details
[ImmyBot] Get the maintenance-item type (software / maintenance task / script) of a deployment by its id (from immy_list_target_assignments). Lightweight lookup used to disambiguate which item family the deployment targets.
immy_patch_target_assignments_batch_update details
immy_patch_target_assignments_batch_update details
[ImmyBot] Batch-update multiple deployments in one call. Provide a JSON body containing the set of deployments and the fields to change on each. Use for bulk edits instead of many immy_update_target_assignments calls.
immy_target_assignment_migrate_to_superseding_what_if details
immy_target_assignment_migrate_to_superseding_what_if details
[ImmyBot] Preview (what-if, no changes made) migrating deployments onto a superseding target assignment — shows what would happen without applying it. POST-as-read: provide a JSON body describing the migration (source deployments and superseding target). Apply for real with immy_target_assignments_migrate_to_superseding_assignment.
immy_target_assignments details
immy_target_assignments details
[ImmyBot] Create a new deployment (target assignment). Provide a JSON object body defining the maintenance item, targets (tenant/tag/computer/person/MSP), desired state, and schedule. Preview the resolved targets first with immy_target_assignments_target_preview / _tenant_target_preview / _persons_target_preview.
immy_target_assignments_duplicate details
immy_target_assignments_duplicate details
[ImmyBot] Duplicate a single deployment (target assignment) into a new one. Provide a JSON body identifying the source deployment and any overrides for the copy. See immy_target_assignments_duplicates to duplicate several at once.
immy_target_assignments_duplicates details
immy_target_assignments_duplicates details
[ImmyBot] Duplicate multiple deployments (target assignments) in one call. Provide a JSON body identifying the source deployments and any overrides. See immy_target_assignments_duplicate for a single copy.
immy_target_assignments_global_create details
immy_target_assignments_global_create details
[ImmyBot] Create a new global (cross-tenant) deployment. Provide a JSON object body defining the maintenance item, cross-tenant targets, desired state, and schedule. List existing global deployments with immy_list_target_assignments_global.
immy_target_assignments_global_notes details
immy_target_assignments_global_notes details
[ImmyBot] Set or update the notes on a global (cross-tenant) deployment by its id (from immy_list_target_assignments_global). Provide a JSON body containing the notes text.
immy_target_assignments_global_override details
immy_target_assignments_global_override details
[ImmyBot] Apply an override to a global (cross-tenant) deployment by its id (from immy_list_target_assignments_global). Provide a JSON body describing the override (e.g. a tenant-level exception to the cross-tenant deployment).
immy_target_assignments_migrate_deployments_to_provider_links details
immy_target_assignments_migrate_deployments_to_provider_links details
[ImmyBot] Migrate deployments so their targeting is driven by provider-link (RMM/PSA integration) data instead of legacy targeting. Provide a JSON body identifying the deployments and target provider links.
immy_target_assignments_migrate_to_superseding_assignment details
immy_target_assignments_migrate_to_superseding_assignment details
[ImmyBot] Migrate deployments onto a superseding target assignment (applies the change). Provide a JSON body identifying the source deployments and the superseding target. Preview first with immy_target_assignment_migrate_to_superseding_what_if.
immy_target_assignments_notes details
immy_target_assignments_notes details
[ImmyBot] Set or update the notes on a deployment (target assignment) by its id (from immy_list_target_assignments). Provide a JSON body containing the notes text.
immy_target_assignments_optional_target_assignment_approvals details
immy_target_assignments_optional_target_assignment_approvals details
[ImmyBot] Approve (opt in) an optional deployment for a target, by the optional-approval id. Provide a JSON body with the approval decision. Discover available approvals with immy_get_computer_optional_target_assignment_approvals.
immy_target_assignments_override details
immy_target_assignments_override details
[ImmyBot] Apply an override to a deployment (target assignment) by its id (from immy_list_target_assignments). Provide a JSON body describing the override (e.g. a per-computer or per-tenant exception to the deployment).
immy_target_assignments_persons_target_preview details
immy_target_assignments_persons_target_preview details
[ImmyBot] Preview which persons a deployment target would resolve to (no changes made). POST-as-read: provide a JSON body describing the target criteria; returns the matching persons. See immy_target_assignments_target_preview (computers) and immy_target_assignments_tenant_target_preview (tenants).
immy_target_assignments_recommended_approvals_update details
immy_target_assignments_recommended_approvals_update details
[ImmyBot] Apply recommended deployment approvals. Provide a JSON body selecting which of the recommendations to approve/reject. List the recommendations first with immy_list_target_assignments_recommended_approvals.
immy_target_assignments_target_preview details
immy_target_assignments_target_preview details
[ImmyBot] Preview which computers a deployment target would resolve to (no changes made). POST-as-read: provide a JSON body describing the target criteria; returns the matching computers. See immy_target_assignments_tenant_target_preview and immy_target_assignments_persons_target_preview for tenant/person previews.
immy_target_assignments_tenant_target_preview details
immy_target_assignments_tenant_target_preview details
[ImmyBot] Preview which tenants a deployment target would resolve to (no changes made). POST-as-read: provide a JSON body describing the target criteria; returns the matching tenants. See immy_target_assignments_target_preview (computers) and immy_target_assignments_persons_target_preview (persons).
immy_target_assignments_update_maintenance_item_order details
immy_target_assignments_update_maintenance_item_order details
[ImmyBot] Update the run order of maintenance items resolved by deployments. Provide a JSON body containing the desired ordering. View the current order with immy_list_target_assignments_maintenance_item_orders.
immy_target_assignments_visibility details
immy_target_assignments_visibility details
[ImmyBot] Set the visibility of deployments (e.g. hide/show in tenant-facing views). Provide a JSON body identifying the deployments and the visibility setting.
immy_update_target_assignments details
immy_update_target_assignments details
[ImmyBot] Update (replace) a deployment (target assignment) by its id (from immy_list_target_assignments). Provide the full JSON deployment definition — this is a PUT/replace, so include all fields you want to keep. For bulk edits use immy_patch_target_assignments_batch_update.
immy_update_target_assignments_global details
immy_update_target_assignments_global details
[ImmyBot] Update (replace) a global (cross-tenant) deployment by its id (from immy_list_target_assignments_global). Provide the full JSON deployment definition — this is a PUT/replace, so include all fields you want to keep.
Deployment Change Requests
immy_apply_change_request details
immy_apply_change_request details
[ImmyBot] Apply a deployment change request by its changeRequestId (from immy_list_target_assignment_change_requests) — commits the proposed deployment edits. Provide a JSON body with any apply options. Review the diff (immy_list_target_assignments_change_request_diff) before applying.
immy_create_change_request details
immy_create_change_request details
[ImmyBot] Create an instance-wide deployment change request — a reviewable proposal of deployment edits. Provide a JSON body describing the proposed changes. Review its diff with immy_list_target_assignments_change_request_diff, then apply with immy_apply_change_request.
immy_create_deployment_change_request details
immy_create_deployment_change_request details
[ImmyBot] Create a change request scoped to a single deployment, by deploymentId (from immy_list_target_assignments). Provide a JSON body describing the proposed change to that deployment. List a deployment's change requests with immy_list_deployment_change_requests.
immy_get_target_assignments_change_request details
immy_get_target_assignments_change_request details
[ImmyBot] Get a single deployment change request by its changeRequestId (from immy_list_target_assignment_change_requests). Returns the proposed change to a deployment. Inspect what it would alter with immy_list_target_assignments_change_request_diff.
immy_list_deployment_change_requests details
immy_list_deployment_change_requests details
[ImmyBot] List the change requests scoped to a single deployment, by deploymentId (from immy_list_target_assignments). Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts). Create one with immy_create_deployment_change_request.
immy_list_target_assignment_change_requests details
immy_list_target_assignment_change_requests details
[ImmyBot] List deployment change requests across the instance. Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts). For change requests scoped to one deployment use immy_list_deployment_change_requests.
immy_list_target_assignments_change_request_diff details
immy_list_target_assignments_change_request_diff details
[ImmyBot] Get the diff of a deployment change request by its changeRequestId (from immy_list_target_assignment_change_requests) — the before/after of what applying it would change. Review this before immy_apply_change_request.
immy_update_deployment_change_request details
immy_update_deployment_change_request details
[ImmyBot] Update an existing change request scoped to a deployment, by deploymentId and changeRequestId (both from immy_list_deployment_change_requests). Provide a JSON body with the revised proposed change.
Maintenance Actions
immy_get_maintenance_actions_dx_for_computer details
immy_get_maintenance_actions_dx_for_computer details
[ImmyBot] DevExtreme grid feed of maintenance actions scoped to a single computer. Pass the computerId (from immy_list_computers). Uses skip/take paging (take max 100) plus optional DevExtreme filter/sort JSON and requireTotalCount. Returns raw ImmyBot JSON.
immy_get_maintenance_actions_latest_for_computer details
immy_get_maintenance_actions_latest_for_computer details
[ImmyBot] Get the latest maintenance actions for a single computer (from immy_list_computers). Returns raw ImmyBot JSON.
immy_get_maintenance_actions_latest_for_tenant details
immy_get_maintenance_actions_latest_for_tenant details
[ImmyBot] Get the latest maintenance actions for a single tenant (from immy_list_tenants). Returns raw ImmyBot JSON.
immy_get_tenant_latest_non_compliant_maintenance_actions details
immy_get_tenant_latest_non_compliant_maintenance_actions details
[ImmyBot] Get the latest non-compliant maintenance actions (action still required) for a single tenant (from immy_list_tenants). Returns raw ImmyBot JSON.
immy_list_maintenance_actions_computer_needs_attention details
immy_list_maintenance_actions_computer_needs_attention details
[ImmyBot] List the maintenance actions on one computer that currently need attention (non-compliant / action required). Pass the computerId (from immy_list_computers). Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Returns raw ImmyBot JSON.
immy_list_maintenance_actions_dx details
immy_list_maintenance_actions_dx details
[ImmyBot] DevExtreme grid feed of maintenance actions across the instance. Uses skip/take paging (take max 100) plus optional DevExtreme filter/sort JSON and requireTotalCount. Returns raw ImmyBot JSON.
immy_list_maintenance_actions_logs details
immy_list_maintenance_actions_logs details
[ImmyBot] List the execution logs for a single maintenance action. Pass the actionId (from a maintenance-actions listing or a session's actions). Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Returns raw ImmyBot JSON.
immy_list_maintenance_actions_maintenance_item details
immy_list_maintenance_actions_maintenance_item details
[ImmyBot] List maintenance actions grouped/filtered by maintenance item (software or task). Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Returns raw ImmyBot JSON.
immy_list_maintenance_actions_version details
immy_list_maintenance_actions_version details
[ImmyBot] Get the maintenance-actions version/metadata record used by the ImmyBot UI grid. Returns raw ImmyBot JSON.
immy_maintenance_actions_latest_action_for_computers details
immy_maintenance_actions_latest_action_for_computers details
[ImmyBot] Look up the latest maintenance action for a set of computers for one software item or maintenance task. This is a POST-as-read (read-only): provide a JSON object body — required: maintenanceIdentifier (string). Optional: maintenanceType ('Software' or 'MaintenanceTask'; must accompany maintenanceIdentifier), computerIds (array of computer ids), dateUtc (ISO timestamp to look back from). Returns raw ImmyBot JSON.
immy_maintenance_actions_latest_action_for_tenants details
immy_maintenance_actions_latest_action_for_tenants details
[ImmyBot] Look up the latest maintenance action for a set of tenants for one software item or maintenance task. This is a POST-as-read (read-only): provide a JSON object body — required: maintenanceIdentifier (string). Optional: maintenanceType ('Software' or 'MaintenanceTask'; must accompany maintenanceIdentifier), tenantIds (array of tenant ids), dateUtc (ISO timestamp to look back from). Returns raw ImmyBot JSON.
Maintenance Sessions
immy_cancel_all_maintenance_sessions details
immy_cancel_all_maintenance_sessions details
[ImmyBot] Cancel ALL currently-running maintenance sessions across the instance. Destructive and broad — it aborts every in-progress session; get user approval first. Takes no meaningful body (leave fieldsJson as ``). Returns raw ImmyBot JSON.
immy_cancel_maintenance_session details
immy_cancel_maintenance_session details
[ImmyBot] Cancel a single maintenance session by sessionId. Destructive — it aborts the in-progress session. This is a GET-verb action endpoint (not a read); pass the sessionId (from immy_list_maintenance_sessions_dx). Returns raw ImmyBot JSON.
immy_cancel_maintenance_sessions details
immy_cancel_maintenance_sessions details
[ImmyBot] Cancel a specific set of running maintenance sessions. Destructive — it aborts in-progress maintenance. Provide a JSON object body: sessionIds (array of maintenance session ids from immy_list_maintenance_sessions_dx). Returns raw ImmyBot JSON.
immy_cancel_maintenance_sessions_for_schedule details
immy_cancel_maintenance_sessions_for_schedule details
[ImmyBot] Cancel all maintenance sessions that were started by a given schedule. Destructive — it aborts in-progress sessions for that schedule. This is a GET-verb action endpoint (not a read); pass the scheduleId. Returns raw ImmyBot JSON.
immy_get_maintenance_sessions details
immy_get_maintenance_sessions details
[ImmyBot] Get a single maintenance session by sessionId (from immy_list_maintenance_sessions_dx), including its status, target, and actions. Returns raw ImmyBot JSON.
immy_list_maintenance_sessions_dx details
immy_list_maintenance_sessions_dx details
[ImmyBot] DevExtreme grid feed of maintenance sessions across the instance. Uses skip/take paging (take max 100) plus optional DevExtreme filter/sort JSON and requireTotalCount. Use this to find session IDs. Returns raw ImmyBot JSON.
immy_list_maintenance_sessions_last_log details
immy_list_maintenance_sessions_last_log details
[ImmyBot] Get the most recent log line for a maintenance session by sessionId — a lightweight way to poll live progress. Returns raw ImmyBot JSON.
immy_list_maintenance_sessions_logs details
immy_list_maintenance_sessions_logs details
[ImmyBot] List the full log stream for a maintenance session by sessionId. Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. For very old sessions whose logs were rolled off, use immy_list_maintenance_sessions_old_logs. Returns raw ImmyBot JSON.
immy_list_maintenance_sessions_old_logs details
immy_list_maintenance_sessions_old_logs details
[ImmyBot] List the archived/old log stream for a maintenance session by sessionId (the pre-rollover logs not returned by immy_list_maintenance_sessions_logs). Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Returns raw ImmyBot JSON.
immy_list_maintenance_sessions_phases details
immy_list_maintenance_sessions_phases details
[ImmyBot] List the phases (detection, resolution, follow-up, etc.) of a maintenance session by sessionId, with each phase's status and timing. Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Returns raw ImmyBot JSON.
immy_list_maintenance_sessions_status_counts details
immy_list_maintenance_sessions_status_counts details
[ImmyBot] Get the count of maintenance sessions in each status (e.g. running, completed, cancelled, failed). Useful for a dashboard summary. Returns raw ImmyBot JSON.
immy_maintenance_sessions_actions_rerun details
immy_maintenance_sessions_actions_rerun details
[ImmyBot] Re-run a single action within a maintenance session (re-executes just that one maintenance action). Pass the sessionId and the actionId (both from immy_get_maintenance_sessions). This endpoint takes no body — leave fieldsJson as ``. Returns raw ImmyBot JSON.
immy_maintenance_sessions_resume details
immy_maintenance_sessions_resume details
[ImmyBot] Resume a paused/waiting maintenance session by sessionId (e.g. one that stalled awaiting a reboot or user response). Pass the sessionId (from immy_list_maintenance_sessions_dx). This endpoint takes no body — leave fieldsJson as ``. Returns raw ImmyBot JSON.
immy_rerun_maintenance_session details
immy_rerun_maintenance_session details
[ImmyBot] Re-run a single maintenance session by sessionId (re-executes maintenance against its original target). Pass the sessionId (from immy_list_maintenance_sessions_dx). This endpoint takes no body — leave fieldsJson as ``. Returns raw ImmyBot JSON.
immy_rerun_maintenance_sessions details
immy_rerun_maintenance_sessions details
[ImmyBot] Re-run a set of maintenance sessions (re-executes maintenance against their original targets). Provide a JSON object body: sessionIds (array of maintenance session ids from immy_list_maintenance_sessions_dx). Returns raw ImmyBot JSON (new session IDs).
immy_run_immy_service details
immy_run_immy_service details
[ImmyBot] Enqueue one or more maintenance sessions and SYNCHRONOUSLY return the started session IDs. This can install/uninstall software, run maintenance tasks, and reboot endpoints, so it is destructive — get user approval before running. Provide a JSON object body: target with exactly one of computers, tenants, or persons (arrays; mutually exclusive). Optional: maintenanceParams (the software/task to run; omit for full maintenance), detectionOnly, resolutionOnly, inventoryOnly, fullMaintenance, cacheOnly, rebootPreference, licenseId, updateTime, timeZoneInfoId, and email/prompt options. For large fan-outs prefer immy_run_immy_service_new (background). Returns raw ImmyBot JSON (started session IDs).
immy_run_immy_service_new details
immy_run_immy_service_new details
[ImmyBot] Enqueue one or more maintenance sessions in the BACKGROUND and return immediately (202 Accepted) without waiting for the session IDs. Same target/body shape as immy_run_immy_service (exactly one of computers, tenants, or persons; optional maintenanceParams and options). Preferred for large fan-outs. Destructive — it executes maintenance (install/uninstall/reboot) on customer endpoints; get user approval first. Poll status with immy_list_maintenance_sessions_dx / immy_get_maintenance_sessions. Returns raw ImmyBot JSON.
Maintenance Tasks
immy_create_global_maintenance_task details
immy_create_global_maintenance_task details
[ImmyBot] Create a new GLOBAL (cross-tenant) maintenance task. Body (fieldsJson) is the task definition — typically name, description, the script/metascript body, execution context, and parameter definitions. Returns the created task JSON (including its assigned id).
immy_create_local_maintenance_task details
immy_create_local_maintenance_task details
[ImmyBot] Create a new LOCAL (tenant-scoped) maintenance task. Body (fieldsJson) is the task definition — typically name, description, script/metascript body, execution context, and parameter definitions. Returns the created task JSON (including its assigned id).
immy_delete_maintenance_tasks_global details
immy_delete_maintenance_tasks_global details
[ImmyBot] Permanently delete the global maintenance task identified by id — this cannot be undone and every deployment/target-assignment referencing it will lose that task. Check immy_list_maintenance_tasks_reference_count first. id comes from immy_list_maintenance_tasks_global.
immy_delete_maintenance_tasks_local details
immy_delete_maintenance_tasks_local details
[ImmyBot] Permanently delete the local maintenance task identified by id — this cannot be undone and any deployment referencing it will lose that task. id comes from immy_list_maintenance_tasks_local.
immy_get_maintenance_tasks_global details
immy_get_maintenance_tasks_global details
[ImmyBot] Get a single global maintenance task by id, including its script/metascript body and parameter definitions. id comes from immy_list_maintenance_tasks_global or immy_list_maintenance_tasks_search.
immy_get_maintenance_tasks_local details
immy_get_maintenance_tasks_local details
[ImmyBot] Get a single local maintenance task by id, including its script/metascript body and parameter definitions. id comes from immy_list_maintenance_tasks_local or immy_list_maintenance_tasks_search.
immy_list_maintenance_tasks_authorization details
immy_list_maintenance_tasks_authorization details
[ImmyBot] Get the authorization/access configuration for the maintenance task identified by id (which tenants/roles may see or run it). id comes from immy_list_maintenance_tasks_global/local. Change it with the write tool immy_maintenance_tasks_authorization.
immy_list_maintenance_tasks_global details
immy_list_maintenance_tasks_global details
[ImmyBot] List global (cross-tenant) maintenance tasks. Supports Sieve paging/filtering. Each entry carries an id used by immy_get_maintenance_tasks_global and the update/delete tools. `pageSize` is clamped to 100. `filters`/`sorts` accept Sieve expressions (e.g. filters="name@=defender", sorts="name").
immy_list_maintenance_tasks_local details
immy_list_maintenance_tasks_local details
[ImmyBot] List local (tenant-scoped) maintenance tasks. Supports Sieve paging/filtering. Each entry carries an id used by immy_get_maintenance_tasks_local and the update/delete tools. `pageSize` is clamped to 100. `filters`/`sorts` accept Sieve expressions.
immy_list_maintenance_tasks_reference_count details
immy_list_maintenance_tasks_reference_count details
[ImmyBot] Return the count of references to maintenance tasks (how many deployments/other objects point at each task) — used to gauge blast radius before editing or deleting a task. Takes no parameters.
immy_list_maintenance_tasks_search details
immy_list_maintenance_tasks_search details
[ImmyBot] Search across both global and local maintenance tasks. Supports Sieve paging/filtering — pass a Sieve `filters` expression to narrow by name/text. `pageSize` is clamped to 100. Results carry ids usable with the get/update/delete tools.
immy_maintenance_task_migrate_local_to_global_what_if details
immy_maintenance_task_migrate_local_to_global_what_if details
[ImmyBot] Preview (dry-run) what promoting the local maintenance task identified by id to a global task would do — surfaces conflicts, references, and the resulting shape without making any change. Pair with the write tool immy_maintenance_tasks_local_migrate_local_to_global to actually perform the migration. id comes from immy_list_maintenance_tasks_local.
immy_maintenance_tasks_authorization details
immy_maintenance_tasks_authorization details
[ImmyBot] Set the authorization/access configuration for the maintenance task identified by id (which tenants/roles may see or run it). id comes from immy_list_maintenance_tasks_global/local. Read the current config with immy_list_maintenance_tasks_authorization. Body (fieldsJson): the authorization definition.
immy_maintenance_tasks_duplicate details
immy_maintenance_tasks_duplicate details
[ImmyBot] Duplicate an existing maintenance task, creating an editable copy. Body (fieldsJson): identifies the source task (e.g. its id) and any overrides (e.g. new name). Returns the newly created task JSON.
immy_maintenance_tasks_global_param_block_from_parameters details
immy_maintenance_tasks_global_param_block_from_parameters details
[ImmyBot] Generate the PowerShell param() block text for the global maintenance task identified by id from a set of parameter definitions. This is a read-only preview/codegen helper (POST-as-read) — it computes and returns the param block and does NOT modify the task. id comes from immy_list_maintenance_tasks_global. Body (fieldsJson): the parameter definitions to render.
immy_maintenance_tasks_local_migrate_local_to_global details
immy_maintenance_tasks_local_migrate_local_to_global details
[ImmyBot] Promote the local maintenance task identified by id to a GLOBAL (cross-tenant) task, making it available to all tenants. Preview the effect first with immy_maintenance_task_migrate_local_to_global_what_if. id comes from immy_list_maintenance_tasks_local. Body (fieldsJson): migration options (may be an empty object).
immy_maintenance_tasks_local_param_block_from_parameters details
immy_maintenance_tasks_local_param_block_from_parameters details
[ImmyBot] Generate the PowerShell param() block text for the local maintenance task identified by id from a set of parameter definitions. This is a read-only preview/codegen helper (POST-as-read) — it computes and returns the param block and does NOT modify the task. id comes from immy_list_maintenance_tasks_local. Body (fieldsJson): the parameter definitions to render.
immy_maintenance_tasks_validate_param_block_parameters details
immy_maintenance_tasks_validate_param_block_parameters details
[ImmyBot] Validate a set of param-block parameter definitions for a maintenance task — checks types, required-ness, and default consistency and returns validation results. This is a read-only validation helper (POST-as-read) and does NOT persist anything. Body (fieldsJson): the parameter definitions to validate.
immy_update_global_maintenance_task details
immy_update_global_maintenance_task details
[ImmyBot] Update the global maintenance task identified by id. Body (fieldsJson) is the full task definition (replace semantics, not a partial patch). id comes from immy_list_maintenance_tasks_global. Editing a widely-referenced task affects every deployment that uses it — check immy_list_maintenance_tasks_reference_count first.
immy_update_local_maintenance_task details
immy_update_local_maintenance_task details
[ImmyBot] Update the local maintenance task identified by id. Body (fieldsJson) is the full task definition (replace semantics, not a partial patch). id comes from immy_list_maintenance_tasks_local.
Inventory Tasks
immy_create_local_inventory_task details
immy_create_local_inventory_task details
[ImmyBot] Create a new LOCAL (tenant-authored) inventory task. Body (fieldsJson) is the inventory-task definition — typically name, description, and the inventory scripts/keys it gathers. Returns the created task JSON (including its assigned id). Only local inventory tasks are editable; global ones are read-only vendor content. Attach collection scripts afterward with immy_inventory_tasks_local_scripts.
immy_delete_inventory_tasks_local details
immy_delete_inventory_tasks_local details
[ImmyBot] Permanently delete the local inventory task identified by id, along with its collection scripts — this cannot be undone and any detection/deployment logic referencing its inventory keys will lose that data source. id comes from immy_list_inventory_tasks. Only local inventory tasks can be deleted.
immy_delete_inventory_tasks_local_scripts details
immy_delete_inventory_tasks_local_scripts details
[ImmyBot] Permanently remove a single collection script (identified by inventoryKey) from the local inventory task identified by taskId — this cannot be undone. taskId comes from immy_list_inventory_tasks; inventoryKey identifies the specific script/inventory slot within that task.
immy_inventory_tasks_local_scripts details
immy_inventory_tasks_local_scripts details
[ImmyBot] Add or update a collection script on the local inventory task identified by id. Body (fieldsJson) describes the script and its inventory key (the named slot whose output this script produces). id comes from immy_list_inventory_tasks. Remove a script with immy_delete_inventory_tasks_local_scripts.
immy_list_inventory_tasks details
immy_list_inventory_tasks details
[ImmyBot] List all inventory tasks (global vendor + local tenant-authored) that collect custom inventory data from managed computers. Supports Sieve paging/filtering. Each entry carries an id used by the get/update/delete inventory-task tools. `pageSize` is clamped to 100. `filters`/`sorts` accept Sieve expressions (e.g. filters="name@=chrome", sorts="name").
immy_update_local_inventory_task details
immy_update_local_inventory_task details
[ImmyBot] Update the local inventory task identified by id. Body (fieldsJson) is the full inventory-task definition (this is a replace, not a partial patch). id comes from immy_list_inventory_tasks. Only local inventory tasks can be updated.
Tags
immy_create_tag details
immy_create_tag details
[ImmyBot] Create a tag. Provide a JSON object body — typically name (string) plus optional color/description. The created tag id can then be applied via immy_add_tags_to_computers / immy_add_tags_to_persons / immy_add_tags_to_tenants.
immy_delete_tags details
immy_delete_tags details
[ImmyBot] Permanently delete a tag by id (from immy_list_tags). This removes the tag from every computer/person/tenant it is applied to and cannot be undone.
immy_get_tags details
immy_get_tags details
[ImmyBot] Get a single tag by id (from immy_list_tags). Returns the tag's id, name, and configuration.
immy_list_tags details
immy_list_tags details
[ImmyBot] List tags defined in the ImmyBot instance. Tags label computers, persons, and tenants and can be used as deployment/role-assignment targets. Paginated via Sieve: page (1-based) + pageSize (max 100). filters/sorts accept Sieve expressions (e.g. filters="Name@=windows", sorts="Name"). Returns each tag's id and name; feed a tag id to immy_get_tags / immy_update_tag / immy_delete_tags.
immy_list_tags_authorization details
immy_list_tags_authorization details
[ImmyBot] Get the authorization (RBAC) settings for a tag by id (from immy_list_tags) — which roles/groups may act on resources carrying this tag. Update it with immy_tags_authorization.
immy_tags_authorization details
immy_tags_authorization details
[ImmyBot] Set the authorization (RBAC) settings for a tag by id (from immy_list_tags) — which roles/groups may act on resources carrying this tag. Provide a JSON object body describing the authorization. Read the current state with immy_list_tags_authorization first.
immy_update_tag details
immy_update_tag details
[ImmyBot] Update a tag by id (from immy_list_tags). Provide a JSON object body with the fields to change (e.g. name). Note: ImmyBot updates a tag via HTTP POST to /tags/, not PUT.
Tenants
immy_add_tags_to_tenants details
immy_add_tags_to_tenants details
[ImmyBot] Add one or more tags to one or more tenants. Provide a JSON object body identifying the tenant id(s) and tag id(s) (tags from immy_list_tags, tenants from immy_list_tenants). Remove them with immy_remove_tags_from_tenants.
immy_get_tenants details
immy_get_tenants details
[ImmyBot] Get a single tenant by id (from immy_list_tenants). Returns the tenant's full detail (name, parent tenant, Azure link, flags).
immy_get_tenants_azure_groups details
immy_get_tenants_azure_groups details
[ImmyBot] Get a single Azure (Entra) group for a tenant by tenant id (from immy_list_tenants) and group id (from immy_list_tenants_azure_groups). Returns the group's detail.
immy_get_tenants_software_from_inventory details
immy_get_tenants_software_from_inventory details
[ImmyBot] Get a single software-from-inventory record by id (from immy_list_tenants_software_from_inventory_dx). Returns the discovered software detail.
immy_list_tenants details
immy_list_tenants details
[ImmyBot] List the tenants (managed customer organizations) in the ImmyBot instance. Paginated via Sieve: page (1-based) + pageSize (max 100). filters/sorts accept Sieve expressions (e.g. filters="Name@=acme", sorts="Name"). Returns each tenant's id and name; feed a tenant id to immy_get_tenants and the tenant write tools.
immy_list_tenants_azure_groups details
immy_list_tenants_azure_groups details
[ImmyBot] List the Azure (Entra) groups for a tenant by tenant id (from immy_list_tenants). Requires the tenant to have a linked Azure tenant (see immy_tenants_update_azure_tenant_link). Paginated via Sieve: page + pageSize (max 100), plus optional filters/sorts. Get one group with immy_get_tenants_azure_groups.
immy_list_tenants_computer_counts details
immy_list_tenants_computer_counts details
[ImmyBot] List tenants with their managed-computer counts. Paginated via Sieve: page + pageSize (max 100), plus optional filters/sorts. Useful for a fleet-size overview per customer.
immy_list_tenants_computers_excluded_from_maintenance details
immy_list_tenants_computers_excluded_from_maintenance details
[ImmyBot] List a tenant's computers that are excluded from maintenance, by tenant id (from immy_list_tenants). Paginated via Sieve: page + pageSize (max 100), plus optional filters/sorts. Exclude/include individual computers with immy_computers_exclude_from_maintenance.
immy_list_tenants_excluded_from_cross_tenant_deployments details
immy_list_tenants_excluded_from_cross_tenant_deployments details
[ImmyBot] List tenants that are excluded from cross-tenant (global) deployments. Paginated via Sieve: page + pageSize (max 100), plus optional filters/sorts.
immy_list_tenants_software_from_inventory_dx details
immy_list_tenants_software_from_inventory_dx details
[ImmyBot] List software discovered across tenants from inventory, as a DevExtreme grid feed. Uses DevExtreme paging: skip + take (take max 100), with optional filter/sort (DevExtreme JSON expressions) and requireTotalCount. For a downloadable spreadsheet use immy_list_tenants_software_from_inventory_export.
immy_list_tenants_software_from_inventory_export details
immy_list_tenants_software_from_inventory_export details
[ImmyBot] Export the cross-tenant software-from-inventory report as an XLSX spreadsheet. Because the response is a binary spreadsheet (not JSON), this returns a short-lived read-only SAS URL envelope {sasUrl, contentType, suggestedFilename, sizeBytes, expiresAt} — download the spreadsheet from sasUrl out-of-band; do NOT decode the URL as content. Optional Sieve filters/sorts narrow the exported rows.
immy_patch_tenants_activate details
immy_patch_tenants_activate details
[ImmyBot] Activate a tenant by id (from immy_list_tenants). Sent as an HTTP PATCH to /tenants/activate/. The body is usually empty (); pass a JSON object only if the endpoint requires activation options.
immy_patch_tenants_deactivate details
immy_patch_tenants_deactivate details
[ImmyBot] Deactivate a tenant by id (from immy_list_tenants). Sent as an HTTP PATCH to /tenants/deactivate/. The body is usually empty (); pass a JSON object only if the endpoint requires deactivation options. Re-activate with immy_patch_tenants_activate.
immy_remove_tags_from_tenants details
immy_remove_tags_from_tenants details
[ImmyBot] Remove one or more tags from one or more tenants. Provide a JSON object body identifying the tenant id(s) and tag id(s) (tags from immy_list_tags, tenants from immy_list_tenants). Add them with immy_add_tags_to_tenants.
immy_tenants details
immy_tenants details
[ImmyBot] Create a tenant (managed customer organization). Provide a JSON object body — typically name plus optional parent-tenant and configuration fields. For creating many at once use immy_tenants_bulk_create.
immy_tenants_bulk_create details
immy_tenants_bulk_create details
[ImmyBot] Create multiple tenants in one call. Provide a JSON object body containing the array of tenants to create (each typically with a name). For a single tenant use immy_tenants.
immy_tenants_bulk_delete details
immy_tenants_bulk_delete details
[ImmyBot] Permanently delete multiple tenants in one call — irreversible. Provide a JSON object body with the array of tenant id(s) to delete (from immy_list_tenants). Deleting a tenant removes its managed computers/persons associations.
immy_tenants_bulk_merge details
immy_tenants_bulk_merge details
[ImmyBot] Merge tenants together — consolidates source tenants into a target and removes the sources; irreversible. Provide a JSON object body identifying the source and target tenant id(s) (from immy_list_tenants). Review affected tenants before merging.
immy_tenants_remove_parent_tenant details
immy_tenants_remove_parent_tenant details
[ImmyBot] Remove the parent-tenant link from one or more tenants, flattening them out of a parent/child hierarchy. Provide a JSON object body with the tenant id(s) (from immy_list_tenants). Set a parent with immy_tenants_set_parent_tenant.
immy_tenants_resolve_assignments_for_maintenance_item details
immy_tenants_resolve_assignments_for_maintenance_item details
[ImmyBot] Resolve which tenants a given maintenance item's deployments apply to (a read-only what-resolves query, sent as an HTTP POST). Provide a JSON object body describing the maintenance item / criteria. Returns the resolved tenant assignments; makes no changes.
immy_tenants_set_parent_tenant details
immy_tenants_set_parent_tenant details
[ImmyBot] Set the parent-tenant link on one or more tenants, placing them under a parent in the tenant hierarchy. Provide a JSON object body identifying the child tenant id(s) and the parent tenant id (from immy_list_tenants). Remove the link with immy_tenants_remove_parent_tenant.
immy_tenants_update_azure_tenant_link details
immy_tenants_update_azure_tenant_link details
[ImmyBot] Link (or update the link for) an ImmyBot tenant to a Microsoft Azure (Entra) tenant, enabling Azure-group inspection (immy_list_tenants_azure_groups) and Azure-scoped automation. Provide a JSON object body with the ImmyBot tenant id and the Azure tenant domain/GUID.
immy_update_tenants details
immy_update_tenants details
[ImmyBot] Update a tenant by id (from immy_list_tenants). Sent as an HTTP PUT to /tenants/ — provide the full JSON object body of tenant fields to set. For activation/parent-link changes use the dedicated tools (immy_patch_tenants_activate, immy_tenants_set_parent_tenant).
Provider Links
immy_delete_provider_links details
immy_delete_provider_links details
[ImmyBot] Permanently delete a provider link by its id (from immy_list_provider_links). This removes the integration and its client/asset mappings — destructive and not reversible. Confirm the id belongs to the link you intend to remove.
immy_get_provider_links details
immy_get_provider_links details
[ImmyBot] Get a single provider link by its id (from immy_list_provider_links). Returns the link's full configuration — provider type, name, credentials metadata, sync settings, and status.
immy_get_provider_links_tickets details
immy_get_provider_links_tickets details
[ImmyBot] Get a single ticket from the PSA provider behind a provider link (from immy_list_provider_links), identified by the provider's ticket id. Returns the ticket as the external provider reports it.
immy_get_rmm_links details
immy_get_rmm_links details
immy_installer_agent_rekey_request details
immy_installer_agent_rekey_request details
[ImmyBot] Request a rekey of an ImmyBot agent installer (rotate the agent's key material for re-enrollment). Provide the request parameters as a JSON object in bodyJson. This is a host-rooted installer endpoint (/installer/agent-rekey/request).
immy_list_provider_links details
immy_list_provider_links details
[ImmyBot] List the provider links (integrations to external RMM / PSA / documentation providers) configured in this ImmyBot instance. Returns each link's id, provider type, name, and status. Link ids feed immy_get_provider_links, immy_update_provider_links, immy_delete_provider_links, and every asset/client/agent tool. Sieve pagination: Page (1-based), pageSize (capped at 100), Filters, Sorts. See immy_list_provider_links_with_unmapped_clients for links that still have unmapped clients.
immy_list_provider_links_audits details
immy_list_provider_links_audits details
[ImmyBot] List the audit-log entries for a provider link (from immy_list_provider_links) — configuration changes, sync events, and errors over time. Sieve pagination: Page (1-based), pageSize (capped at 100), Filters, Sorts.
immy_list_provider_links_immy_field_samples details
immy_list_provider_links_immy_field_samples details
[ImmyBot] List sample values for the ImmyBot-side fields available when configuring asset field mappings on a provider link (from immy_list_provider_links). Use alongside immy_list_provider_links_asset_fields (the external side) to build field mappings via immy_provider_links_asset_field_mappings.
immy_list_provider_links_with_unmapped_clients details
immy_list_provider_links_with_unmapped_clients details
[ImmyBot] List provider links that still have external clients not yet mapped to an ImmyBot tenant. Use this to find links needing client-linking work (see immy_provider_links_clients_* in the Provider Clients group). Sieve pagination: Page (1-based), pageSize (capped at 100), Filters, Sorts.
immy_list_rmm_links details
immy_list_rmm_links details
[ImmyBot] List provider links filtered to the RMM-capable providers only (a filtered alias view over immy_list_provider_links). Sieve pagination: Page (1-based), pageSize (capped at 100), Filters, Sorts. Create/update RMM links via immy_rmm_links / immy_update_rmm_links.
immy_plugin_proxy_get details
immy_plugin_proxy_get details
[ImmyBot] Open-world proxy: forward a GET request to a provider plugin's own API under the given provider link (from immy_list_provider_links). The catchAll sub-path and optional raw query string are passed VERBATIM to the plugin (path is host-rooted at /plugins/api/v1//); the plugin defines its own routes and response shape. Use only when a dedicated ImmyBot tool does not cover the plugin capability you need.
immy_plugin_proxy_post details
immy_plugin_proxy_post details
[ImmyBot] Open-world proxy: forward a POST request to a provider plugin's own API under the given provider link (from immy_list_provider_links). The catchAll sub-path is passed VERBATIM (host-rooted at /plugins/api/v1//) and bodyJson becomes the request body; the plugin defines its own routes, semantics, and response shape. This can mutate provider-side state — use only when a dedicated ImmyBot tool does not cover the capability.
immy_provider_links details
immy_provider_links details
[ImmyBot] Create a provider link (a new integration to an external RMM / PSA / documentation provider). Provide the link definition as a JSON object in bodyJson — the required fields (provider type, name, credentials) depend on the provider; discover available provider types via immy_list_provider_types. For linking against an existing external provider reference, use immy_provider_links_create_with_external_provider_reference instead.
immy_provider_links_create_with_external_provider_reference details
immy_provider_links_create_with_external_provider_reference details
[ImmyBot] Create a provider link from an existing external provider reference (e.g. an Azure/partner reference already known to ImmyBot). Provide the reference and link settings as a JSON object in bodyJson. Use immy_provider_links_verify_with_external_provider_reference first to validate the reference resolves before creating.
immy_provider_links_reload details
immy_provider_links_reload details
[ImmyBot] Reload a provider link by its id (from immy_list_provider_links) — reinitialize the plugin/integration and refresh its cached state. Provide any reload options as a JSON object in bodyJson (send if none).
immy_provider_links_verify_with_external_provider_reference details
immy_provider_links_verify_with_external_provider_reference details
[ImmyBot] Verify that an external provider reference resolves and can back a provider link, WITHOUT creating anything. Provide the reference as a JSON object in bodyJson. This is a validation call that may perform an outbound check against the provider — classified as a write. Follow with immy_provider_links_create_with_external_provider_reference to persist the link.
immy_rmm_links details
immy_rmm_links details
[ImmyBot] Create an RMM provider link (the RMM-scoped create path; a provider link whose provider is an RMM). Provide the link definition as a JSON object in bodyJson. See immy_list_rmm_links for the filtered view of existing RMM links.
immy_update_provider_links details
immy_update_provider_links details
[ImmyBot] Update a provider link by its id (from immy_list_provider_links). Provide the full replacement definition as a JSON object in bodyJson (PUT semantics — send the complete link object, not a partial patch).
immy_update_rmm_links details
immy_update_rmm_links details
[ImmyBot] Update an RMM link by its id (from immy_list_rmm_links). Provide the full replacement definition as a JSON object in bodyJson (PUT semantics).
Provider Link Assets
immy_delete_provider_links_asset_field_mappings details
immy_delete_provider_links_asset_field_mappings details
[ImmyBot] Permanently delete an asset field mapping from a provider link. Identify it by the provider link id (from immy_list_provider_links) and the mapping id (from immy_list_provider_links_asset_field_mappings). Destructive and not reversible.
immy_delete_provider_links_asset_match_fields details
immy_delete_provider_links_asset_match_fields details
[ImmyBot] Permanently delete an asset match field from a provider link. Identify it by the provider link id (from immy_list_provider_links) and the match field id (from immy_list_provider_links_asset_match_fields). Destructive and not reversible — removing a matcher can change how future syncs match assets to computers.
immy_list_provider_links_asset_field_mappings details
immy_list_provider_links_asset_field_mappings details
[ImmyBot] List the asset field mappings configured on a provider link (from immy_list_provider_links) — each mapping ties an external provider field to an ImmyBot field. Mapping ids feed immy_update_provider_links_asset_field_mappings and immy_delete_provider_links_asset_field_mappings. Sieve pagination: Page (1-based), pageSize (capped at 100), Filters, Sorts.
immy_list_provider_links_asset_fields details
immy_list_provider_links_asset_fields details
[ImmyBot] List the external asset fields exposed by the provider behind a provider link (from immy_list_provider_links) — the source side of an asset field mapping. Each field's external id feeds immy_list_provider_links_asset_fields_samples. Sieve pagination: Page (1-based), pageSize (capped at 100), Filters, Sorts.
immy_list_provider_links_asset_fields_samples details
immy_list_provider_links_asset_fields_samples details
[ImmyBot] List sample values for a single external asset field on a provider link — helps you preview what data a field carries before mapping it. Identify the field by the provider link id (from immy_list_provider_links) and the external field id (from immy_list_provider_links_asset_fields).
immy_list_provider_links_asset_match_fields details
immy_list_provider_links_asset_match_fields details
[ImmyBot] List the asset match fields configured on a provider link (from immy_list_provider_links) — the fields used to match external assets to ImmyBot computers during sync. Match-field ids feed immy_update_provider_links_asset_match_fields and immy_delete_provider_links_asset_match_fields. See immy_list_provider_links_asset_match_fields_recommended for suggested matchers. Sieve pagination: Page (1-based), pageSize (capped at 100), Filters, Sorts.
immy_list_provider_links_asset_match_fields_recommended details
immy_list_provider_links_asset_match_fields_recommended details
[ImmyBot] List the recommended asset match fields for a provider link (from immy_list_provider_links) — ImmyBot's suggested matchers based on the provider's field schema. Use as a starting point before creating match fields via immy_provider_links_asset_match_fields.
immy_list_provider_links_assets_dx details
immy_list_provider_links_assets_dx details
[ImmyBot] List the synced assets for a provider link (from immy_list_provider_links) as a DevExtreme grid feed. Uses DevExtreme paging: skip + take (take capped at 100), with optional filter and sort passthrough and requireTotalCount. Each asset's external id feeds immy_list_provider_links_assets_url.
immy_list_provider_links_assets_job_state details
immy_list_provider_links_assets_job_state details
[ImmyBot] Get the current asset-sync job state for a provider link (from immy_list_provider_links) — whether a sync is running, queued, or idle, plus progress/last-result metadata. Trigger a sync with immy_provider_links_assets_trigger.
immy_list_provider_links_assets_schedule details
immy_list_provider_links_assets_schedule details
immy_list_provider_links_assets_url details
immy_list_provider_links_assets_url details
[ImmyBot] Get the external provider URL for a single synced asset — the deep link into the provider's UI for that asset. Identify it by the provider link id (from immy_list_provider_links) and the external asset id (from immy_list_provider_links_assets_dx).
immy_provider_links_asset_field_mappings details
immy_provider_links_asset_field_mappings details
[ImmyBot] Create an asset field mapping on a provider link (from immy_list_provider_links) — tie one external provider field to one ImmyBot field. Provide the mapping as a JSON object in bodyJson (external field id from immy_list_provider_links_asset_fields, ImmyBot field from immy_list_provider_links_immy_field_samples).
immy_provider_links_asset_match_fields details
immy_provider_links_asset_match_fields details
[ImmyBot] Create an asset match field on a provider link (from immy_list_provider_links) — a field used to match external assets to ImmyBot computers during sync. Provide the match field as a JSON object in bodyJson (see immy_list_provider_links_asset_match_fields_recommended for suggestions).
immy_provider_links_assets_trigger details
immy_provider_links_assets_trigger details
[ImmyBot] Trigger an on-demand asset sync for a provider link (from immy_list_provider_links) — pull the latest assets from the external provider now instead of waiting for the schedule. Provide any trigger options as a JSON object in bodyJson (send if none). Poll progress with immy_list_provider_links_assets_job_state.
immy_update_provider_links_asset_field_mappings details
immy_update_provider_links_asset_field_mappings details
[ImmyBot] Update an existing asset field mapping on a provider link. Identify it by the provider link id (from immy_list_provider_links) and the mapping id (from immy_list_provider_links_asset_field_mappings). Provide the full replacement mapping as a JSON object in bodyJson (PUT semantics).
immy_update_provider_links_asset_match_fields details
immy_update_provider_links_asset_match_fields details
[ImmyBot] Update an existing asset match field on a provider link. Identify it by the provider link id (from immy_list_provider_links) and the match field id (from immy_list_provider_links_asset_match_fields). Provide the full replacement definition as a JSON object in bodyJson (PUT semantics).
Provider Agents
immy_list_provider_agents_identification_logs details
immy_list_provider_agents_identification_logs details
[ImmyBot] List the identification logs for a single provider agent, by agentId (from immy_list_provider_agents_pending). Shows how ImmyBot attempted to match this agent to a computer/tenant and why it succeeded or failed — the primary evidence when resolving an identification failure with immy_provider_agents_resolve_failure. Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts).
immy_list_provider_agents_pending details
immy_list_provider_agents_pending details
[ImmyBot] List provider agents that are pending identification — agents discovered through a provider link (RMM/PSA integration) that ImmyBot has not yet matched to a managed computer/tenant. Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts). Match them with immy_provider_agents_identify, or clear them with immy_provider_agents_bulk_delete_pending. See immy_list_provider_agents_pending_counts for a quick total.
immy_list_provider_agents_pending_conflicts details
immy_list_provider_agents_pending_conflicts details
[ImmyBot] List the pending provider-agent conflicts for a specific computer, by computerId (from immy_list_computers). A conflict is when more than one pending provider agent could map to the same computer; this shows the competing candidates so you can pick the right one before identifying. Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts).
immy_list_provider_agents_pending_counts details
immy_list_provider_agents_pending_counts details
[ImmyBot] Get the count of provider agents pending identification, broken down (e.g. per provider link). A lightweight summary companion to immy_list_provider_agents_pending — use it to decide whether identification work is needed before paging the full list.
immy_provider_agents_bulk_delete_pending details
immy_provider_agents_bulk_delete_pending details
[ImmyBot] Permanently delete a set of pending (unidentified) provider agents in one call. Provide a JSON body listing the pending agent ids to remove. This clears them from the pending queue and cannot be undone — use it for stale/duplicate discoveries rather than agents you still intend to identify with immy_provider_agents_identify.
immy_provider_agents_identify details
immy_provider_agents_identify details
[ImmyBot] Identify one or more pending provider agents — match each discovered agent to a managed computer/tenant so ImmyBot can manage it. Provide a JSON body describing the agent(s) and the target computer/mapping. Review candidates first with immy_list_provider_agents_pending and immy_list_provider_agents_pending_conflicts.
immy_provider_agents_resolve_failure details
immy_provider_agents_resolve_failure details
[ImmyBot] Resolve a single provider-agent identification failure, by failureId. Provide a JSON body describing the resolution (e.g. the correct computer/tenant mapping to apply). Inspect the failure evidence first with immy_list_provider_agents_identification_logs. To resolve every failure at once use immy_resolve_provider_agent_failures; to resolve all failures for one agent use immy_resolve_agent_failures_for_agent.
immy_resolve_agent_failures_for_agent details
immy_resolve_agent_failures_for_agent details
[ImmyBot] Resolve all identification failures for one provider agent, by agentId (from immy_list_provider_agents_pending). Provide a JSON body describing the resolution. Scopes the fix to a single agent — for a specific failure use immy_provider_agents_resolve_failure, for every agent use immy_resolve_provider_agent_failures.
immy_resolve_provider_agent_failures details
immy_resolve_provider_agent_failures details
[ImmyBot] Resolve provider-agent identification failures in bulk. Provide a JSON body describing the resolution to apply across the failures. For a single failure use immy_provider_agents_resolve_failure; to scope resolution to one agent use immy_resolve_agent_failures_for_agent.
Provider Clients & Agents
immy_delete_provider_links_cross_references_delete details
immy_delete_provider_links_cross_references_delete details
[ImmyBot] Permanently delete a provider-link cross-reference, by provider-link id (from immy_list_provider_links) and externalLinkId. Removes the external link tying another system's records to this provider link and cannot be undone. Create one with immy_provider_links_cross_references_create.
immy_list_provider_links_clients details
immy_list_provider_links_clients details
[ImmyBot] List the external clients a provider link exposes, by provider-link id (from immy_list_provider_links, S8). These are the RMM/PSA-side customers/organizations available to map onto ImmyBot tenants. Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts). Map them with immy_provider_links_clients_link_to_tenant / _auto_link_to_tenants; see immy_list_provider_links_clients_statuses for linking state.
immy_list_provider_links_clients_statuses details
immy_list_provider_links_clients_statuses details
[ImmyBot] List the linking status of each client on a provider link, by provider-link id (from immy_list_provider_links). Shows which external clients are linked, unlinked, or in conflict with ImmyBot tenants — the state map you use before running a linking action. Companion to immy_list_provider_links_clients.
immy_list_provider_links_clients_types details
immy_list_provider_links_clients_types details
[ImmyBot] List the client types a provider link supports, by provider-link id (from immy_list_provider_links). Client types describe the categories of external client the integration can expose; use them to filter or interpret immy_list_provider_links_clients.
immy_provider_agent_onboarding_powershell_install_script details
immy_provider_agent_onboarding_powershell_install_script details
[ImmyBot] Generate a PowerShell (Windows) install script for the provider link's agent that also triggers ImmyBot onboarding on first run, by provider-link id (from immy_list_provider_links). Provide a JSON body with the script/target + onboarding options. Non-onboarding variant: immy_provider_links_agents_powershell_install_script.
immy_provider_agent_onboarding_provisioning_package_uri details
immy_provider_agent_onboarding_provisioning_package_uri details
[ImmyBot] Get a download URI for a Windows provisioning-package (.ppkg) installer for the provider link's agent that also triggers ImmyBot onboarding on first run, by provider-link id (from immy_list_provider_links). Provide a JSON body with the target + onboarding options. Non-onboarding variant: immy_provider_links_agents_provisioning_package_uri.
immy_provider_links_agents_bash_install_script details
immy_provider_links_agents_bash_install_script details
[ImmyBot] Generate a bash (macOS/Linux) install script for the provider link's agent, by provider-link id (from immy_list_provider_links). Provide a JSON body with the script/target options; returns the ready-to-run installer text. For the onboarding-enabled variant use immy_provider_links_agents_bash_install_script_with_onboarding; for Windows use immy_provider_links_agents_powershell_install_script.
immy_provider_links_agents_bash_install_script_with_onboarding details
immy_provider_links_agents_bash_install_script_with_onboarding details
[ImmyBot] Generate a bash (macOS/Linux) install script for the provider link's agent that also triggers ImmyBot onboarding on first run, by provider-link id (from immy_list_provider_links). Provide a JSON body with the script/target and onboarding options. Non-onboarding variant: immy_provider_links_agents_bash_install_script.
immy_provider_links_agents_delete_offline_agent_from_computer details
immy_provider_links_agents_delete_offline_agent_from_computer details
[ImmyBot] Permanently remove an offline provider agent from a computer, by provider-link id (from immy_list_provider_links) and agentId. Provide a JSON body identifying the computer/agent. This deletes the agent association on the RMM/PSA side for a device that is no longer online and cannot be undone — use it to clean up dead agents, not to temporarily pause management.
immy_provider_links_agents_executable_uri details
immy_provider_links_agents_executable_uri details
[ImmyBot] Get a download URI for the provider link's agent executable installer, by provider-link id (from immy_list_provider_links). Provide a JSON body with the target options; returns the URI to fetch the installer binary. For the onboarding-enabled variant use immy_provider_links_agents_executable_uri_with_onboarding.
immy_provider_links_agents_executable_uri_with_onboarding details
immy_provider_links_agents_executable_uri_with_onboarding details
[ImmyBot] Get a download URI for the provider link's agent executable installer that also triggers ImmyBot onboarding on first run, by provider-link id (from immy_list_provider_links). Provide a JSON body with the target + onboarding options. Non-onboarding variant: immy_provider_links_agents_executable_uri.
immy_provider_links_agents_external_agent_url details
immy_provider_links_agents_external_agent_url details
[ImmyBot] Get the external RMM/PSA console URL for a computer's agent, by provider-link id (from immy_list_provider_links) and computerId (from immy_list_computers). Provide a JSON body with any options; returns the deep-link into the provider's own portal for that device. A write in the API (it may resolve/refresh the link) though its purpose is retrieval.
immy_provider_links_agents_install_on_computer details
immy_provider_links_agents_install_on_computer details
[ImmyBot] Install the provider link's agent directly onto a specific managed computer, by provider-link id (from immy_list_provider_links) and computerId (from immy_list_computers). Provide a JSON body with the install options. Unlike the script/URI generators, this dispatches the install to the target computer.
immy_provider_links_agents_powershell_install_script details
immy_provider_links_agents_powershell_install_script details
[ImmyBot] Generate a PowerShell (Windows) install script for the provider link's agent, by provider-link id (from immy_list_provider_links). Provide a JSON body with the script/target options; returns the ready-to-run installer text. For the onboarding-enabled variant use immy_provider_agent_onboarding_powershell_install_script; for macOS/Linux use immy_provider_links_agents_bash_install_script.
immy_provider_links_agents_provisioning_package_uri details
immy_provider_links_agents_provisioning_package_uri details
[ImmyBot] Get a download URI for a Windows provisioning-package (.ppkg) installer for the provider link's agent, by provider-link id (from immy_list_provider_links). Provide a JSON body with the target options. For the onboarding-enabled variant use immy_provider_agent_onboarding_provisioning_package_uri.
immy_provider_links_agents_refresh_device_online_status details
immy_provider_links_agents_refresh_device_online_status details
[ImmyBot] Refresh the online/offline status of a provider agent's device, by provider-link id (from immy_list_provider_links) and agentId. Provide a JSON body identifying the device. Forces ImmyBot to re-check the RMM/PSA for the device's current connectivity rather than waiting for the next sync.
immy_provider_links_agents_sync details
immy_provider_links_agents_sync details
[ImmyBot] Trigger a sync of the provider link's agents, by provider-link id (from immy_list_provider_links). Provide a JSON body with any sync options. Pulls the current agent inventory from the RMM/PSA so ImmyBot's view is up to date; feeds the pending-identification queue (see immy_list_provider_agents_pending). See also immy_provider_links_clients_sync_agents to sync agents per linked client.
immy_provider_links_clients_auto_link_to_tenants details
immy_provider_links_clients_auto_link_to_tenants details
[ImmyBot] Automatically link a provider link's external clients to ImmyBot tenants using ImmyBot's matching heuristics, by provider-link id (from immy_list_provider_links). Provide a JSON body with the auto-link options. For a stricter exact-name match use immy_provider_links_clients_link_exact_match_clients; to map one client explicitly use immy_provider_links_clients_link_to_tenant.
immy_provider_links_clients_link_exact_match_clients details
immy_provider_links_clients_link_exact_match_clients details
[ImmyBot] Link only the provider clients whose names exactly match an existing ImmyBot tenant, by provider-link id (from immy_list_provider_links). Provide a JSON body with the options. A conservative alternative to immy_provider_links_clients_auto_link_to_tenants — links high-confidence matches and leaves ambiguous ones for manual mapping.
immy_provider_links_clients_link_to_new_tenant details
immy_provider_links_clients_link_to_new_tenant details
[ImmyBot] Create a new ImmyBot tenant and link a provider client to it in one step, by provider-link id (from immy_list_provider_links). Provide a JSON body identifying the client and the new tenant details. Use this when the external client has no matching ImmyBot tenant yet; to link to an existing tenant use immy_provider_links_clients_link_to_tenant.
immy_provider_links_clients_link_to_tenant details
immy_provider_links_clients_link_to_tenant details
[ImmyBot] Link a provider client to a specific existing ImmyBot tenant, by provider-link id (from immy_list_provider_links). Provide a JSON body identifying the client and target tenant (from immy_list_tenants). The explicit, one-to-one alternative to the auto/exact-match linkers. Reverse with immy_provider_links_clients_unlink_from_tenants.
immy_provider_links_clients_sync details
immy_provider_links_clients_sync details
[ImmyBot] Trigger a sync of the provider link's clients, by provider-link id (from immy_list_provider_links). Provide a JSON body with any sync options. Refreshes the external client list from the RMM/PSA so linking decisions act on current data; see immy_list_provider_links_clients for the result and immy_provider_links_clients_sync_agents to also sync agents.
immy_provider_links_clients_sync_agents details
immy_provider_links_clients_sync_agents details
[ImmyBot] Sync the agents belonging to the provider link's linked clients, by provider-link id (from immy_list_provider_links). Provide a JSON body with any options. Narrower than immy_provider_links_agents_sync — it refreshes agent inventory scoped to already-linked clients.
immy_provider_links_clients_unlink_from_tenants details
immy_provider_links_clients_unlink_from_tenants details
[ImmyBot] Unlink provider clients from their ImmyBot tenants, by provider-link id (from immy_list_provider_links). Provide a JSON body identifying which client links to remove. Reverses immy_provider_links_clients_link_to_tenant / _auto_link_to_tenants; the external clients remain but are no longer mapped to tenants.
immy_provider_links_cross_references_create details
immy_provider_links_cross_references_create details
[ImmyBot] Create a cross-reference on a provider link — an external link that ties another provider/system's records to this provider link, by provider-link id (from immy_list_provider_links). Provide a JSON body describing the external reference. Toggle its client-linking with immy_provider_links_cross_references_enable_client_linking / _disable_client_linking; remove it with immy_delete_provider_links_cross_references_delete.
immy_provider_links_cross_references_disable_client_linking details
immy_provider_links_cross_references_disable_client_linking details
[ImmyBot] Disable client linking for a provider-link cross-reference, by provider-link id (from immy_list_provider_links) and externalLinkId. Provide a JSON body with any options. Stops the cross-reference from driving client-to-tenant linking. Re-enable with immy_provider_links_cross_references_enable_client_linking.
immy_provider_links_cross_references_enable_client_linking details
immy_provider_links_cross_references_enable_client_linking details
[ImmyBot] Enable client linking for a provider-link cross-reference, by provider-link id (from immy_list_provider_links) and externalLinkId. Provide a JSON body with any options. Allows the cross-reference to drive client-to-tenant linking. Disable with immy_provider_links_cross_references_disable_client_linking.
immy_provider_links_cross_references_sync_clients details
immy_provider_links_cross_references_sync_clients details
[ImmyBot] Sync the clients associated with a provider-link cross-reference, by provider-link id (from immy_list_provider_links) and externalLinkId. Provide a JSON body with any options. Refreshes the client data flowing through this specific cross-reference; broader syncs are immy_provider_links_clients_sync.
Provider Types
immy_get_provider_types_form_dropdown_options details
immy_get_provider_types_form_dropdown_options details
[ImmyBot] Get the option set for a provider-type configuration-form dropdown, by its key. Provider-link configuration forms populate certain fields from server-side option lists; this returns the valid choices for one such field so you can supply a correct value when creating/updating a provider link (S8).
immy_list_provider_types details
immy_list_provider_types details
[ImmyBot] List the available provider types — the kinds of external RMM/PSA integration a provider link can be created against (e.g. the supported vendor integrations). Supports Sieve paging (Page, pageSize up to 100, Filters, Sorts). Use the returned type keys when creating a provider link with immy_provider_links (S8).
immy_list_provider_types_client_group_types_client_groups details
immy_list_provider_types_client_group_types_client_groups details
[ImmyBot] List the client groups available for a given client-group-type, by clientGroupTypeId (from immy_list_provider_types metadata). Client groups are how a provider type organizes its customer/tenant containers; use them when configuring how a provider link maps external clients to ImmyBot tenants.
immy_list_provider_types_device_group_types_device_groups details
immy_list_provider_types_device_group_types_device_groups details
[ImmyBot] List the device groups available for a given device-group-type, by deviceGroupTypeId (from immy_list_provider_types metadata). Device groups are how a provider type organizes its endpoint/device containers; use them when configuring how a provider link maps external devices to ImmyBot computers.
immy_provider_types_bind_parameters details
immy_provider_types_bind_parameters details
[ImmyBot] Preview how a set of configuration parameters binds for a given provider type, by providerType. POST-as-read: provide a JSON body of the parameter values; ImmyBot resolves/validates them and returns the bound result without saving anything. Use it to sanity-check provider-link configuration before creating the link with immy_provider_links (S8).
Personal Access Tokens
immy_delete_personal_access_tokens details
immy_delete_personal_access_tokens details
[ImmyBot] Permanently revoke the personal access token identified by id (from immy_list_personal_access_tokens / immy_list_personal_access_tokens_all). Any integration still using the token immediately loses API access; this cannot be undone.
immy_list_personal_access_tokens details
immy_list_personal_access_tokens details
[ImmyBot] List the personal access tokens (PATs) belonging to the current user. Paginated via Sieve: page (1-based) + pageSize (max 100); filters/sorts accept Sieve expressions. To see every user's PATs across the instance (admin view) use immy_list_personal_access_tokens_all. Create a PAT with immy_personal_access_tokens; revoke one with immy_delete_personal_access_tokens.
immy_list_personal_access_tokens_all details
immy_list_personal_access_tokens_all details
[ImmyBot] List ALL personal access tokens across every user in the instance (administrator view) — use this to audit outstanding API tokens. For only the current user's tokens use immy_list_personal_access_tokens. Paginated via Sieve: page + pageSize (max 100), filters/sorts accept Sieve expressions.
immy_personal_access_tokens details
immy_personal_access_tokens details
[ImmyBot] Create a new personal access token (PAT). Provide a JSON object body — typically a name/description and optional expiration. The response includes the generated token secret, which is shown only once; store it securely. Revoke with immy_delete_personal_access_tokens.
Persons
immy_add_tags_to_persons details
immy_add_tags_to_persons details
[ImmyBot] Add one or more tags to one or more persons in bulk. Provide a JSON object body naming the target person ids and the tag ids to apply (discover tag ids with immy_list_tags, person ids with immy_list_persons). Remove tags with immy_remove_tags_from_persons.
immy_delete_persons details
immy_delete_persons details
[ImmyBot] Permanently delete the person identified by id (from immy_list_persons). This removes the person record and their computer/tag affinities; it cannot be undone. It does NOT delete the person's computers.
immy_get_persons details
immy_get_persons details
[ImmyBot] Get a single person by id (from immy_list_persons). Returns the person's profile — name, email, tenant, tags, owned-computer affinities, and access state.
immy_list_persons details
immy_list_persons details
[ImmyBot] List persons (managed end-users) known to the ImmyBot instance. Paginated via Sieve: page (1-based) + pageSize (max 100); filters/sorts accept Sieve expressions (e.g. filters="EmailAddress@=@contoso.com", sorts="DisplayName"). For the DevExtreme grid feed use immy_list_persons_dx. Feed a person id to immy_get_persons / immy_update_persons / immy_delete_persons.
immy_list_persons_detected_software details
immy_list_persons_detected_software details
[ImmyBot] List the software detected across the computers associated with the person identified by personId (from immy_list_persons). Paginated via Sieve: page + pageSize (max 100), filters/sorts accept Sieve expressions.
immy_list_persons_dx details
immy_list_persons_dx details
[ImmyBot] List persons via the DevExtreme grid feed (the shape the ImmyBot UI person grid consumes). Uses skip/take paging (take max 100) plus optional DevExtreme filter/sort expressions and requireTotalCount. For standard Sieve paging use immy_list_persons.
immy_list_persons_requesting_access details
immy_list_persons_requesting_access details
[ImmyBot] List persons who have requested self-service portal access and are awaiting a decision. Approve a request with immy_persons_grant_access or reject it with immy_persons_deny_access. Paginated via Sieve: page + pageSize (max 100), filters/sorts accept Sieve expressions.
immy_list_persons_self_service details
immy_list_persons_self_service details
immy_persons details
immy_persons details
[ImmyBot] Create a person (managed end-user). Provide a JSON object body — typically displayName, emailAddress, and the owning tenantId. Returns the created person JSON including its assigned id. Update it later with immy_update_persons; attach tags with immy_add_tags_to_persons.
immy_persons_deny_access details
immy_persons_deny_access details
[ImmyBot] Deny or revoke self-service portal access for the person identified by personId (from immy_list_persons / immy_list_persons_requesting_access). Provide a JSON object body with any options. Grant access with immy_persons_grant_access.
immy_persons_grant_access details
immy_persons_grant_access details
[ImmyBot] Grant self-service portal access to the person identified by personId (from immy_list_persons / immy_list_persons_requesting_access). Provide a JSON object body with any access options. Revoke with immy_persons_deny_access.
immy_remove_tags_from_persons details
immy_remove_tags_from_persons details
[ImmyBot] Remove one or more tags from one or more persons in bulk. Provide a JSON object body naming the target person ids and the tag ids to remove. Add tags with immy_add_tags_to_persons.
immy_update_persons details
immy_update_persons details
[ImmyBot] Update the person identified by id (from immy_list_persons). Body (fieldsJson) is the person definition to apply (replace semantics). Use immy_add_tags_to_persons / immy_remove_tags_from_persons for tag membership rather than editing tags here.
Users
immy_bulk_delete_users details
immy_bulk_delete_users details
[ImmyBot] Permanently delete multiple ImmyBot console users in one call. Provide a JSON object/array body naming the user ids to delete (from immy_list_users). This is sent as an HTTP DELETE with a request body; it cannot be undone. Deleted users immediately lose console access.
immy_delete_users details
immy_delete_users details
[ImmyBot] Permanently delete the ImmyBot console user identified by userId (from immy_list_users). The user immediately loses console access; this cannot be undone. To remove several users at once use immy_bulk_delete_users.
immy_get_users details
immy_get_users details
[ImmyBot] Get a single ImmyBot console user by userId (from immy_list_users). Returns the user's profile, status, and expiration. See their group memberships with immy_list_users_groups and role assignments with immy_get_user_role_assignments_users.
immy_list_users details
immy_list_users details
[ImmyBot] List ImmyBot console users (operators/technicians). Paginated via Sieve: page (1-based) + pageSize (max 100); filters/sorts accept Sieve expressions (e.g. filters="Email@=@msp.com", sorts="Email"). Feed a user id to immy_get_users, immy_list_users_groups, immy_users (update), or immy_delete_users. For the person (end-user) directory use immy_list_persons instead.
immy_list_users_claims details
immy_list_users_claims details
[ImmyBot] Get the identity claims for the currently authenticated caller — the claim set the ImmyBot backend associates with this session/token. Useful for confirming which identity and roles the connector is acting as.
immy_list_users_groups details
immy_list_users_groups details
[ImmyBot] List the RBAC groups the user identified by userId (from immy_list_users) belongs to. Paginated via Sieve: page + pageSize (max 100), filters/sorts accept Sieve expressions. Manage group membership with immy_groups_members / immy_delete_groups_members (RBAC slice).
immy_users details
immy_users details
[ImmyBot] Update the ImmyBot console user identified by userId (from immy_list_users). Body (fieldsJson) is the user definition to apply. Note: ImmyBot updates a user via HTTP POST to /users/, not PUT. Adjust the user's expiration separately with immy_users_update_expiration and role/group membership via the RBAC tools.
immy_users_bulk_create details
immy_users_bulk_create details
[ImmyBot] Create multiple ImmyBot console users in one call. Provide a JSON object/array body describing the users to create (typically each with email and role/group assignments). Returns the created users. Delete users in bulk with immy_bulk_delete_users.
immy_users_impersonate details
immy_users_impersonate details
[ImmyBot] Begin impersonating the ImmyBot console user identified by userId (from immy_list_users) — subsequent actions are performed as that user, for support/troubleshooting. Provide a JSON object body with any impersonation options (may be ). End the session with immy_users_stop_impersonating.
immy_users_invalidate_cache details
immy_users_invalidate_cache details
[ImmyBot] Invalidate the server-side user/permission cache so identity and RBAC changes take effect immediately. Provide a JSON object body with any scope options (may be ). Despite the name this is a state-changing operation, not a validation read.
immy_users_stop_impersonating details
immy_users_stop_impersonating details
[ImmyBot] End the current user-impersonation session started by immy_users_impersonate, returning to the caller's own identity. Provide a JSON object body with any options (may be ).
immy_users_submit_feedback details
immy_users_submit_feedback details
[ImmyBot] Submit product feedback to ImmyBot on behalf of the current user. Provide a JSON object body with the feedback content (e.g. message/category).
immy_users_update_expiration details
immy_users_update_expiration details
[ImmyBot] Set or change the expiration for one or more ImmyBot console users. Provide a JSON object body naming the target user id(s) and the new expiration (or clearing it). Expired users lose console access at the given time.
Roles, Groups & Permissions
immy_delete_groups details
immy_delete_groups details
[ImmyBot] Permanently delete an RBAC group by id (from immy_list_groups). This removes the group and its role assignments; members lose any access granted through it. Cannot be undone.
immy_delete_groups_members details
immy_delete_groups_members details
[ImmyBot] Remove a user from a group. Provide the group id (from immy_list_groups) and the user id (from immy_list_groups_members / immy_list_users). The user loses any access granted through this group. Cannot be undone (re-add with immy_groups_members).
immy_delete_roles details
immy_delete_roles details
[ImmyBot] Permanently delete a role by id (from immy_list_roles). This removes the role and revokes it from every user/group it is assigned to (see immy_list_roles_assignments). Cannot be undone.
immy_effective_permissions_groups_evaluate_all_assignments details
immy_effective_permissions_groups_evaluate_all_assignments details
[ImmyBot] Evaluate the effective permissions a group would have across ALL of its role assignments (POST-as-read what-if — nothing is changed). Provide the group id (from immy_list_groups) plus a JSON body describing the evaluation context. Use the resource/tenant variants (immy_effective_permissions_groups_evaluate_resource / _tenant) to scope the evaluation.
immy_effective_permissions_groups_evaluate_resource details
immy_effective_permissions_groups_evaluate_resource details
[ImmyBot] Evaluate a group's effective permissions against a specific resource (POST-as-read what-if — nothing is changed). Provide the group id (from immy_list_groups) plus a JSON body identifying the resource. See immy_effective_permissions_groups_evaluate_tenant for tenant-scoped and immy_effective_permissions_groups_evaluate_all_assignments for the full picture.
immy_effective_permissions_groups_evaluate_tenant details
immy_effective_permissions_groups_evaluate_tenant details
[ImmyBot] Evaluate a group's effective permissions within a specific tenant (POST-as-read what-if — nothing is changed). Provide the group id (from immy_list_groups) plus a JSON body identifying the tenant. See immy_effective_permissions_groups_evaluate_resource for resource-scoped evaluation.
immy_effective_permissions_users_evaluate_all_assignments details
immy_effective_permissions_users_evaluate_all_assignments details
[ImmyBot] Evaluate the effective permissions a user would have across ALL of their role assignments (POST-as-read what-if — nothing is changed). Provide the user id (from immy_list_users) plus a JSON body describing the evaluation context. Use the resource/tenant variants (immy_effective_permissions_users_evaluate_resource / _tenant) to scope the evaluation.
immy_effective_permissions_users_evaluate_resource details
immy_effective_permissions_users_evaluate_resource details
[ImmyBot] Evaluate a user's effective permissions against a specific resource (POST-as-read what-if — nothing is changed). Provide the user id (from immy_list_users) plus a JSON body identifying the resource. See immy_effective_permissions_users_evaluate_tenant for tenant-scoped and immy_effective_permissions_users_evaluate_all_assignments for the full picture.
immy_effective_permissions_users_evaluate_tenant details
immy_effective_permissions_users_evaluate_tenant details
[ImmyBot] Evaluate a user's effective permissions within a specific tenant (POST-as-read what-if — nothing is changed). Provide the user id (from immy_list_users) plus a JSON body identifying the tenant. See immy_effective_permissions_users_evaluate_resource for resource-scoped evaluation.
immy_get_groups details
immy_get_groups details
[ImmyBot] Get a single RBAC group by id (from immy_list_groups). Returns the group's id, name, and configuration. List its members with immy_list_groups_members and its role assignments with immy_list_groups_role_assignments.
immy_get_roles details
immy_get_roles details
[ImmyBot] Get a single role by id (from immy_list_roles). Returns the role's id, name, and the permissions it grants. List where the role is assigned with immy_list_roles_assignments.
immy_groups details
immy_groups details
[ImmyBot] Create an RBAC group. Provide a JSON object body — typically name (string) plus optional description. The created group id can then take members (immy_groups_members) and role assignments.
immy_groups_members details
immy_groups_members details
[ImmyBot] Add a member to a group by id (from immy_list_groups). Provide a JSON object body identifying the user to add (e.g. { "userId": ... }). To add several at once use immy_groups_members_bulk; to remove one use immy_delete_groups_members.
immy_groups_members_bulk details
immy_groups_members_bulk details
[ImmyBot] Add multiple members to a group by id (from immy_list_groups) in one call. Provide a JSON body containing the collection of users to add. For a single member use immy_groups_members.
immy_list_groups details
immy_list_groups details
[ImmyBot] List RBAC groups. Groups bundle users and carry role assignments. Paginated via Sieve: page (1-based) + pageSize (max 100); filters/sorts accept Sieve expressions. Feed a group id to immy_get_groups, immy_list_groups_members, immy_list_groups_role_assignments, immy_update_groups, or immy_delete_groups.
immy_list_groups_members details
immy_list_groups_members details
[ImmyBot] List the users that belong to a group by id (from immy_list_groups). Paginated via Sieve (page, pageSize up to 100, filters, sorts). Add members with immy_groups_members (single) / immy_groups_members_bulk (many) and remove one with immy_delete_groups_members.
immy_list_groups_role_assignments details
immy_list_groups_role_assignments details
[ImmyBot] List the role assignments attached to a group by id (from immy_list_groups) — which roles the group grants and at what scope. Paginated via Sieve (page, pageSize up to 100, filters, sorts). Create user/group role assignments with the immy_user_role_assignments_*_create family.
immy_list_roles details
immy_list_roles details
[ImmyBot] List RBAC roles. A role bundles a set of permissions (enumerate the full permission catalog with immy_list_roles_permissions). Paginated via Sieve (page, pageSize up to 100, filters, sorts). Feed a role id to immy_get_roles, immy_list_roles_assignments, immy_update_roles, immy_roles_clone, or immy_delete_roles.
immy_list_roles_assignments details
immy_list_roles_assignments details
[ImmyBot] List the assignments of a role by id (from immy_list_roles) — which users/groups hold this role and at what scope. Paginated via Sieve (page, pageSize up to 100, filters, sorts). Create assignments with the immy_user_role_assignments_*_create family.
immy_list_roles_permissions details
immy_list_roles_permissions details
[ImmyBot] List the full catalog of permissions that roles can grant (the building blocks referenced when creating/updating a role with immy_roles / immy_update_roles). Paginated via Sieve (page, pageSize up to 100, filters, sorts). This is the permission universe, not the permissions of one role.
immy_roles details
immy_roles details
[ImmyBot] Create an RBAC role. Provide a JSON object body — typically name plus the collection of permissions it grants (enumerate valid permissions with immy_list_roles_permissions). To copy an existing role instead, use immy_roles_clone.
immy_roles_clone details
immy_roles_clone details
[ImmyBot] Clone an existing role by id (from immy_list_roles) into a new role. Provide a JSON object body for the clone (typically the new name plus any overrides). The source role is unchanged.
immy_update_groups details
immy_update_groups details
[ImmyBot] Update a group by id (from immy_list_groups) via HTTP PUT. Provide a JSON object body with the fields to change (e.g. name, description).
immy_update_roles details
immy_update_roles details
[ImmyBot] Update a role by id (from immy_list_roles) via HTTP PUT. Provide a JSON object body with the fields to change (e.g. name, permissions). Valid permission identifiers come from immy_list_roles_permissions.
User Role Assignments
immy_delete_user_role_assignment details
immy_delete_user_role_assignment details
[ImmyBot] Delete (revoke) a user-role assignment. This is an HTTP DELETE that carries a JSON body identifying the assignment to remove (as returned by immy_list_user_role_assignments / immy_get_user_role_assignments_users). The affected user/group loses the access that assignment granted. Cannot be undone (recreate with the matching immy_user_role_assignments_*_create tool).
immy_get_user_role_assignments_users details
immy_get_user_role_assignments_users details
[ImmyBot] Get all role assignments for a single user by id (from immy_list_users). Returns each role bound to the user and its scope. Count them with immy_list_user_role_assignments_users_count.
immy_list_user_role_assignments details
immy_list_user_role_assignments details
[ImmyBot] List user-role assignments across the instance — the bindings of roles to users/groups at their scopes. Paginated via Sieve (page, pageSize up to 100, filters, sorts). For a single user use immy_get_user_role_assignments_users; create assignments with the immy_user_role_assignments_*_create family; remove one with immy_delete_user_role_assignment.
immy_list_user_role_assignments_users_count details
immy_list_user_role_assignments_users_count details
[ImmyBot] Get the number of role assignments a single user has, by user id (from immy_list_users). Enumerate the assignments themselves with immy_get_user_role_assignments_users.
immy_user_role_assignments_category_resource_create details
immy_user_role_assignments_category_resource_create details
[ImmyBot] Create a role assignment scoped to a CATEGORY of resources — grants a role to a user/group over an entire resource category. Provide a JSON object body identifying the user/group, the role (from immy_list_roles), and the resource category. For a single resource use immy_user_role_assignments_specific_resource_create.
immy_user_role_assignments_msp_create details
immy_user_role_assignments_msp_create details
[ImmyBot] Create an MSP-WIDE role assignment — grants a role to a user/group across the entire MSP (all tenants). Provide a JSON object body identifying the user/group and the role (from immy_list_roles). This is the broadest scope; prefer a narrower create tool (specific-tenant/specific-resource/tag) where possible.
immy_user_role_assignments_owner_create details
immy_user_role_assignments_owner_create details
[ImmyBot] Create an OWNER-scoped role assignment — grants a role to a user/group at the owner (instance-owner) scope. Provide a JSON object body identifying the user/group and the role (from immy_list_roles). This is a high-privilege grant; use deliberately.
immy_user_role_assignments_specific_resource_create details
immy_user_role_assignments_specific_resource_create details
[ImmyBot] Create a role assignment scoped to a SPECIFIC resource — grants a role to a user/group on one identified resource only. Provide a JSON object body identifying the user/group, the role (from immy_list_roles), and the target resource. For a category of resources use immy_user_role_assignments_category_resource_create; for tag-matched resources use immy_user_role_assignments_tag_resource_create.
immy_user_role_assignments_specific_tenant_create details
immy_user_role_assignments_specific_tenant_create details
[ImmyBot] Create a role assignment scoped to a SPECIFIC tenant — grants a role to a user/group within one tenant only. Provide a JSON object body identifying the user/group, the role (from immy_list_roles), and the tenant (from immy_list_tenants). For all tenants sharing a tag use immy_user_role_assignments_tenant_tag_create.
immy_user_role_assignments_tag_resource_create details
immy_user_role_assignments_tag_resource_create details
[ImmyBot] Create a role assignment scoped to every resource carrying a given TAG — grants a role to a user/group over all resources with that tag. Provide a JSON object body identifying the user/group, the role (from immy_list_roles), and the resource tag (from immy_list_tags). For a single resource use immy_user_role_assignments_specific_resource_create.
immy_user_role_assignments_tenant_tag_create details
immy_user_role_assignments_tenant_tag_create details
[ImmyBot] Create a role assignment scoped to every tenant carrying a given TAG — grants a role to a user/group across all tenants with that tag. Provide a JSON object body identifying the user/group, the role (from immy_list_roles), and the tenant tag (from immy_list_tags). For a single tenant use immy_user_role_assignments_specific_tenant_create.
immy_user_role_assignments_user_tenant_create details
immy_user_role_assignments_user_tenant_create details
[ImmyBot] Create a user-tenant role assignment — associates a user with a tenant and grants the accompanying role. Provide a JSON object body identifying the user (from immy_list_users), the tenant (from immy_list_tenants), and the role (from immy_list_roles).
Identity & Azure
immy_auth_delete_azure_tenant_auth_details details
immy_auth_delete_azure_tenant_auth_details details
[ImmyBot] Permanently remove the stored Azure/Entra auth details (app registration link + consent) for one or more Azure tenants. This severs ImmyBot's ability to sync users/details for those tenants until re-consented and cannot be undone. Provide a JSON body identifying the Azure tenant(s). Read the current state with immy_get_auth_get_azure_tenant_auth_details first.
immy_auth_request_access details
immy_auth_request_access details
[ImmyBot] Submit an access request for the calling identity (e.g. to gain access to a tenant/resource requiring approval). Provide a JSON body describing the requested access. Persons awaiting access approval can be listed via immy_list_persons_requesting_access.
immy_auth_update_azure_tenant_auth_details details
immy_auth_update_azure_tenant_auth_details details
[ImmyBot] Create or update the stored Azure/Entra auth details for an Azure tenant (app registration, client credentials reference, delegated scopes). Provide a JSON body with the fields to set. Read the current state with immy_get_auth_get_azure_tenant_auth_details first; remove with immy_auth_delete_azure_tenant_auth_details.
immy_azure_disambiguate_azure_tenant_type details
immy_azure_disambiguate_azure_tenant_type details
[ImmyBot] Resolve/record whether an Azure tenant is a partner (CSP) tenant, a customer tenant, or standalone — used when ImmyBot cannot infer the tenant type automatically. Provide a JSON body identifying the tenant and the chosen type. This mutates stored tenant-type classification, so it is a write.
immy_azure_preconsent_customer_tenants details
immy_azure_preconsent_customer_tenants details
[ImmyBot] Preconsent ImmyBot's app registration into one or more CSP customer tenants (grants the app the permissions it needs without visiting each tenant's consent screen). Provide a JSON body identifying the customer tenants (discover them via immy_get_azure_partner_tenant_customers). Follow with immy_azure_sync_details_from_azure_tenants / immy_azure_sync_users_from_azure_tenants to pull data.
immy_azure_sync_details_from_azure_tenants details
immy_azure_sync_details_from_azure_tenants details
[ImmyBot] Trigger a sync of tenant detail/metadata from the linked Azure/Entra tenants into ImmyBot. Provide a JSON body scoping which Azure tenants to sync (or pass the documented all-tenants shape). To sync user accounts instead use immy_azure_sync_users_from_azure_tenants. Sync failures surface in immy_list_azure_errors_dx.
immy_azure_sync_users_from_azure_tenants details
immy_azure_sync_users_from_azure_tenants details
[ImmyBot] Trigger a sync of user accounts from the linked Azure/Entra tenants into ImmyBot persons. Provide a JSON body scoping which Azure tenants to sync. Related: immy_syncs_azure_user_sync (the generic user-sync trigger) and immy_azure_sync_details_from_azure_tenants (tenant metadata). Failures surface in immy_list_azure_errors_dx.
immy_azure_tenant_consented details
immy_azure_tenant_consented details
[ImmyBot] Notify ImmyBot that an Azure/Entra tenant has completed admin consent for its app registration (the callback that finalizes the consent handshake). Provide a JSON body identifying the tenant and consent result. Typically follows immy_azure_preconsent_customer_tenants or a manual consent flow.
immy_get_auth_get_azure_tenant_auth_details details
immy_get_auth_get_azure_tenant_auth_details details
[ImmyBot] Get the stored Azure/Entra auth details (app registration, consent state, delegated permissions) for a single Azure tenant, keyed by its Azure tenant principal id. Update these details with immy_auth_update_azure_tenant_auth_details or remove them with immy_auth_delete_azure_tenant_auth_details.
immy_get_azure_partner_tenant_customers details
immy_get_azure_partner_tenant_customers details
[ImmyBot] List the CSP customer tenants under a partner (reseller) Azure tenant, keyed by the partner's Azure principal id. Use immy_list_azure_partner_tenant_infos to discover partner tenants first. These customers can then be preconsented via immy_azure_preconsent_customer_tenants.
immy_list_auth details
immy_list_auth details
[ImmyBot] List the auth context / linked Azure-tenant auth records for the ImmyBot instance. Paginated via Sieve: page (1-based) + pageSize (max 100). filters/sorts accept Sieve expressions. For the calling identity's effective permissions use immy_list_me_permissions; for a single Azure tenant's auth details use immy_get_auth_get_azure_tenant_auth_details.
immy_list_auth_me_permissions_tenants details
immy_list_auth_me_permissions_tenants details
[ImmyBot] List the tenants the calling identity holds a given permission type against (i.e. the scope of one permission across tenants). permissionType is an ImmyBot permission key. Paginated via Sieve: page + pageSize (max 100), filters/sorts optional. For the full permission map use immy_list_me_permissions.
immy_list_azure_app_registration_options details
immy_list_azure_app_registration_options details
[ImmyBot] List the available Azure app-registration options / templates ImmyBot can use when wiring up Azure/Entra integration for a tenant (e.g. the permission sets and consent URLs it offers). Read-only discovery of what can be configured.
immy_list_azure_errors_dx details
immy_list_azure_errors_dx details
[ImmyBot] List Azure/Entra integration errors across all tenants as a DevExtreme grid feed (failed consents, throttled Graph calls, sync failures). Uses DevExtreme paging: skip + take (take max 100), with optional filter/sort (DevExtreme JSON expressions) and requireTotalCount. For a single tenant's errors use immy_list_azure_errors_for_tenant_dx.
immy_list_azure_errors_for_tenant_dx details
immy_list_azure_errors_for_tenant_dx details
[ImmyBot] List Azure/Entra integration errors for a single tenant (by Azure tenant principal id) as a DevExtreme grid feed. Uses DevExtreme paging: skip + take (take max 100), with optional filter/sort and requireTotalCount. For all tenants at once use immy_list_azure_errors_dx.
immy_list_azure_partner_tenant_infos details
immy_list_azure_partner_tenant_infos details
[ImmyBot] List the partner (CSP/reseller) Azure tenants known to ImmyBot. Paginated via Sieve: page + pageSize (max 100), filters/sorts optional. Feed a partner principal id to immy_get_azure_partner_tenant_customers to enumerate that partner's customer tenants.
immy_list_me_permissions details
immy_list_me_permissions details
[ImmyBot] Get the effective permission map for the calling identity (the app registration StackJack authenticates with). Returns which actions/roles are granted. To see the tenant scope of a single permission, use immy_list_auth_me_permissions_tenants.
OAuth & Syncs
immy_auth_login details
immy_auth_login details
[ImmyBot] Hit the host-rooted /auth/login endpoint (initiates the interactive sign-in redirect). StackJack authenticates with an app-only Azure Bearer token, so this returns the login challenge/redirect metadata rather than establishing an interactive session. Primarily useful for inspecting the instance's sign-in configuration.
immy_auth_logout details
immy_auth_logout details
[ImmyBot] Hit the host-rooted /auth/logout endpoint. Under StackJack's app-only Azure Bearer auth there is no interactive session to terminate, so this is effectively inert — it returns the logout redirect metadata. Exposed for completeness of the auth surface.
immy_auth_me details
immy_auth_me details
[ImmyBot] Hit the host-rooted /auth/me endpoint — returns the current caller's identity as ImmyBot sees it (the app registration under StackJack's app-only Azure Bearer auth). For the granular permission map use immy_list_me_permissions.
immy_delete_oauth_oauth_access_tokens details
immy_delete_oauth_oauth_access_tokens details
[ImmyBot] Permanently revoke/delete an OAuth access-token record by id (from immy_list_oauth_oauth_access_tokens). Any integration relying on this token will lose access until re-authorized and this cannot be undone. To renew instead of revoke, use immy_oauth_oauth_access_tokens_refresh.
immy_get_oauth_oauth_access_tokens details
immy_get_oauth_oauth_access_tokens details
[ImmyBot] Get a single OAuth access-token record by its composite key (id + accessTokenId, both from immy_list_oauth_oauth_access_tokens). Returns the token's provider/scope/expiry metadata.
immy_list_oauth_oauth_access_tokens details
immy_list_oauth_oauth_access_tokens details
[ImmyBot] List the OAuth access tokens ImmyBot holds for its provider integrations (metadata: provider, scopes, expiry, status — not the raw secret). Paginated via Sieve: page + pageSize (max 100), filters/sorts optional. Fetch one with immy_get_oauth_oauth_access_tokens, refresh with immy_oauth_oauth_access_tokens_refresh, or revoke with immy_delete_oauth_oauth_access_tokens.
immy_oauth_begin_auth_code_flow details
immy_oauth_begin_auth_code_flow details
[ImmyBot] Begin an OAuth authorization-code flow so ImmyBot can obtain a delegated token from a third-party provider. Returns the authorization URL / flow state the operator must complete. Provide a JSON body describing the provider and requested scopes. Complete the flow with immy_oauth_finish_auth_code_flow (success) or immy_oauth_fail_auth_code_flow (error/abort).
immy_oauth_fail_auth_code_flow details
immy_oauth_fail_auth_code_flow details
[ImmyBot] Report that an in-progress OAuth authorization-code flow failed or was aborted (records the error and clears the pending flow state). Provide a JSON body with the flow id and error details. The paired success callback is immy_oauth_finish_auth_code_flow; start a flow with immy_oauth_begin_auth_code_flow.
immy_oauth_finish_auth_code_flow details
immy_oauth_finish_auth_code_flow details
[ImmyBot] Complete an OAuth authorization-code flow by redeeming the returned code for a token (the success callback). Provide a JSON body with the flow id, authorization code, and state. Started by immy_oauth_begin_auth_code_flow; the failure callback is immy_oauth_fail_auth_code_flow.
immy_oauth_oauth_access_tokens_refresh details
immy_oauth_oauth_access_tokens_refresh details
[ImmyBot] Refresh (renew) an OAuth access token by id (from immy_list_oauth_oauth_access_tokens) using its stored refresh token. Most refreshes need no body — pass (the default). This endpoint takes no parameters unless the provider requires extra fields.
immy_syncs_azure_user_sync details
immy_syncs_azure_user_sync details
[ImmyBot] Trigger an Azure/Entra user sync job (pulls users from linked Azure tenants into ImmyBot persons). Most invocations take no body — pass (the default) — or supply a JSON body to scope the sync. For a tenant-scoped variant use immy_azure_sync_users_from_azure_tenants. Failures surface in immy_list_azure_errors_dx.
immy_syncs_expire_pending_sessions details
immy_syncs_expire_pending_sessions details
[ImmyBot] Trigger the housekeeping job that expires stale pending maintenance sessions (clears sessions stuck in a pending state). Most invocations take no body — pass (the default). Inspect sessions first with immy_list_maintenance_sessions_dx / immy_list_maintenance_sessions_status_counts.
immy_syncs_trigger_user_affinity_sync details
immy_syncs_trigger_user_affinity_sync details
[ImmyBot] Trigger a user-affinity sync (recomputes which persons are associated with which computers, e.g. primary/additional users). Most invocations take no body — pass (the default). Per-computer affinity is managed via immy_computers_update_primary_person / immy_computers_update_additional_persons.
Media
immy_delete_media_global details
immy_delete_media_global details
[ImmyBot] Delete a GLOBAL media asset by id (from immy_list_media_global). This permanently removes the asset instance-wide; software items or branding that reference it will lose the image. Cannot be undone. Returns the raw ImmyBot result.
immy_delete_media_local details
immy_delete_media_local details
[ImmyBot] Delete a LOCAL media asset by id (from immy_list_media_local). This permanently removes the tenant-owned asset; anything referencing it will lose the image. Cannot be undone. Returns the raw ImmyBot result.
immy_get_media_global details
immy_get_media_global details
[ImmyBot] Get a single GLOBAL media asset by id (from immy_list_media_global). Returns the raw ImmyBot media JSON (metadata, category, dimensions). Use immy_list_media_global_download_url to resolve a URL for the underlying file.
immy_get_media_local details
immy_get_media_local details
[ImmyBot] Get a single LOCAL media asset by id (from immy_list_media_local). Returns the raw ImmyBot media JSON. Use immy_list_media_local_download_url for a file URL and immy_list_media_local_authorization to inspect access scope.
immy_list_media_global details
immy_list_media_global details
[ImmyBot] List GLOBAL media assets (shared across every tenant on the instance) via the DevExtreme grid feed. Despite the plain path this endpoint pages with skip/take, not Sieve. Optionally narrow to a media `category` (e.g. "SoftwareIcon"). Returns the raw DevExtreme envelope {data, totalCount}. See immy_list_media_local for tenant-owned assets and immy_list_media_search for a simple Sieve search.
immy_list_media_global_download_url details
immy_list_media_global_download_url details
[ImmyBot] Resolve a download URL for a GLOBAL media asset's file by id (from immy_list_media_global). Returns a JSON body containing the URL string — this is a normal passthrough read, not a binary blob export. Fetch the URL out-of-band to retrieve the file bytes.
immy_list_media_local details
immy_list_media_local details
[ImmyBot] List LOCAL media assets (owned by a single tenant) via the DevExtreme grid feed. Despite the plain path this endpoint pages with skip/take, not Sieve. Optionally narrow to a media `category` (e.g. "SoftwareIcon"). Returns the raw DevExtreme envelope {data, totalCount}. See immy_list_media_global for instance-shared assets.
immy_list_media_local_authorization details
immy_list_media_local_authorization details
[ImmyBot] Get the authorization/access scope for a LOCAL media asset by id (from immy_list_media_local) — which tenants/roles may use it. Returns the raw ImmyBot authorization JSON. Change it with immy_media_local_authorization.
immy_list_media_local_download_url details
immy_list_media_local_download_url details
[ImmyBot] Resolve a download URL for a LOCAL media asset's file by id (from immy_list_media_local). Returns a JSON body containing the URL string — this is a normal passthrough read, not a binary blob export. Fetch the URL out-of-band to retrieve the file bytes.
immy_list_media_search details
immy_list_media_search details
[ImmyBot] Search media assets with a Sieve page window (Page/pageSize/Filters/Sorts), optionally restricted to global-scope assets via globalOnly. Unlike the DevExtreme grid feeds (immy_list_media_global / immy_list_media_local) this spans both scopes by default. Returns raw ImmyBot JSON.
immy_media_global details
immy_media_global details
[ImmyBot] Update a GLOBAL media asset's metadata by id (from immy_list_media_global). Provide a JSON object body (fieldsJson) with the fields to set (e.g. name, category). Returns the updated media JSON. This updates metadata only — replace the file bytes with immy_media_global_upload.
immy_media_global_upload details
immy_media_global_upload details
[ImmyBot] Upload a GLOBAL media asset (multipart/form-data) — shared across every tenant on the instance. Provide the file bytes base64-encoded (base64Content) and a fileName; the file is decoded and posted as the `file` form part. Optionally forward the endpoint's `mediaId` form field (an existing media record id); omit it for a standard new upload. Returns the raw ImmyBot upload result JSON (including the new media id). Use immy_media_global to update an asset's metadata afterward.
immy_media_local details
immy_media_local details
[ImmyBot] Update a LOCAL media asset's metadata by id (from immy_list_media_local). Provide a JSON object body (fieldsJson) with the fields to set (e.g. name, category). Returns the updated media JSON. This updates metadata only — replace the file bytes with immy_media_local_upload.
immy_media_local_authorization details
immy_media_local_authorization details
[ImmyBot] Set the authorization/access scope for a LOCAL media asset by id (from immy_list_media_local) — which tenants/roles may use it. Provide a JSON object body (fieldsJson) describing the desired authorization. Returns the raw ImmyBot result. Inspect the current scope first with immy_list_media_local_authorization.
immy_media_local_upload details
immy_media_local_upload details
[ImmyBot] Upload a LOCAL media asset (multipart/form-data) — owned by a single tenant. Provide the file bytes base64-encoded (base64Content) and a fileName; the file is decoded and posted as the `file` form part. Optionally forward the endpoint's `mediaId` form field (an existing media record id); omit it for a standard new upload. Returns the raw ImmyBot upload result JSON (including the new media id). Update its metadata with immy_media_local.
immy_media_requestFileDownloadUrl details
immy_media_requestFileDownloadUrl details
[ImmyBot] Request a download URL for a media file (POST-as-read). Provide a JSON object body (fieldsJson) identifying the file (e.g. a media/file reference). Returns a JSON body containing the URL string — normal passthrough, not a binary export. This is a read despite the POST verb.
immy_media_support_upload details
immy_media_support_upload details
[ImmyBot] Upload a SUPPORT media file (multipart/form-data) — e.g. a screenshot or log attached to an ImmyBot support request. Provide the file bytes base64-encoded (base64Content) and a fileName; the file is decoded and posted as the `file` form part. Returns the raw ImmyBot upload result JSON.
Schedules
immy_cancel_schedule details
immy_cancel_schedule details
[ImmyBot] Cancel a running maintenance schedule by id (from immy_list_schedules or immy_list_schedules_running_schedule_ids), stopping its in-flight maintenance session. This interrupts automation mid-run and cannot be undone. This endpoint takes no parameters — leave fieldsJson as ``. Returns the raw ImmyBot result.
immy_delete_schedules details
immy_delete_schedules details
[ImmyBot] Delete a maintenance schedule by id (from immy_list_schedules). This permanently removes the schedule and its future automation; running sessions are not rolled back. Cannot be undone. To only pause it, disable it via immy_patch_schedules_bulk_update_status instead. Returns the raw ImmyBot result.
immy_get_schedules details
immy_get_schedules details
[ImmyBot] Get a single maintenance schedule by id (from immy_list_schedules). Returns the raw ImmyBot schedule JSON (target, trigger/recurrence, maintenance items). Update it with immy_update_schedules.
immy_list_schedules details
immy_list_schedules details
[ImmyBot] List maintenance schedules, optionally filtered to a single tenant. Each schedule declares when a maintenance session runs against a target. Returns raw ImmyBot JSON. Use immy_list_schedules_running_schedule_ids to see which are executing right now, or immy_get_schedules for one schedule's detail.
immy_list_schedules_running_schedule_ids details
immy_list_schedules_running_schedule_ids details
[ImmyBot] List the ids of schedules that are currently executing (have a maintenance session in flight). Returns raw ImmyBot JSON (an id array). Cross-reference with immy_list_schedules; use immy_cancel_schedule to stop one.
immy_patch_schedules_bulk_update_status details
immy_patch_schedules_bulk_update_status details
[ImmyBot] Bulk enable/disable schedules. Provide a JSON object body (fieldsJson) with the target schedule ids and the desired status (e.g. enabled/disabled). Disabling stops future runs without deleting the schedule. Returns the raw ImmyBot result.
immy_schedules details
immy_schedules details
[ImmyBot] Create a maintenance schedule. Provide a JSON object body (fieldsJson) — typically name, the target (tenant/computer/tag), the trigger/recurrence, and the maintenance items to run. Returns the created schedule JSON. Duplicate an existing one instead with immy_schedules_duplicate.
immy_schedules_bulk_cancel details
immy_schedules_bulk_cancel details
[ImmyBot] Bulk-cancel running maintenance schedules, stopping their in-flight maintenance sessions. Provide a JSON object body (fieldsJson) naming the target schedule ids. This interrupts automation mid-run and cannot be undone. Returns the raw ImmyBot result.
immy_schedules_bulk_delete details
immy_schedules_bulk_delete details
[ImmyBot] Bulk-delete maintenance schedules. Provide a JSON object body (fieldsJson) naming the target schedule ids. This permanently removes the schedules and their future automation; cannot be undone. To only pause them, use immy_patch_schedules_bulk_update_status. Returns the raw ImmyBot result.
immy_schedules_bulk_run_now details
immy_schedules_bulk_run_now details
[ImmyBot] Trigger multiple maintenance schedules to run immediately. Provide a JSON object body (fieldsJson) naming the target schedule ids. Each starts its maintenance session now. Returns the raw ImmyBot result. Single-schedule variant: immy_schedules_run_now.
immy_schedules_duplicate details
immy_schedules_duplicate details
[ImmyBot] Duplicate a maintenance schedule by id (from immy_list_schedules), creating a new schedule copied from it. This endpoint takes no parameters — leave fieldsJson as `` unless overrides are supported. Returns the new schedule JSON.
immy_schedules_run_now details
immy_schedules_run_now details
[ImmyBot] Trigger a maintenance schedule to run immediately by id (from immy_list_schedules), starting its maintenance session now instead of at the next scheduled time. This endpoint takes no parameters — leave fieldsJson as ``. Returns the raw ImmyBot result. Bulk variant: immy_schedules_bulk_run_now.
immy_update_schedules details
immy_update_schedules details
[ImmyBot] Update (full replace) a maintenance schedule by id (from immy_list_schedules). Provide the complete JSON object body (fieldsJson) — omitted fields are cleared, so fetch with immy_get_schedules first and send the merged object. Returns the updated schedule JSON.
Dynamic Provider Types
immy_create_global_dynamic_provider_type details
immy_create_global_dynamic_provider_type details
[ImmyBot] Create a new GLOBAL (cross-tenant) dynamic provider type. Body (fieldsJson) is the provider-type definition — typically name, the provider script/definition, and its configuration-form schema. Returns the created provider type JSON (including its assigned id).
immy_create_local_dynamic_provider_type details
immy_create_local_dynamic_provider_type details
[ImmyBot] Create a new LOCAL (tenant-scoped) dynamic provider type. Body (fieldsJson) is the provider-type definition — typically name, the provider script/definition, and its configuration-form schema. Returns the created provider type JSON (including its assigned id).
immy_delete_dynamic_provider_types_global details
immy_delete_dynamic_provider_types_global details
[ImmyBot] Permanently delete the GLOBAL dynamic provider type identified by id — this cannot be undone and any provider link built on it will break. Confirm nothing depends on it first (check immy_list_provider_links). id comes from immy_list_dynamic_provider_types.
immy_delete_dynamic_provider_types_local details
immy_delete_dynamic_provider_types_local details
[ImmyBot] Permanently delete the LOCAL dynamic provider type identified by id — this cannot be undone and any provider link built on it will break. Confirm nothing depends on it first (check immy_list_provider_links). id comes from immy_list_dynamic_provider_types.
immy_delete_dynamic_provider_types_test_environment details
immy_delete_dynamic_provider_types_test_environment details
[ImmyBot] Tear down (dispose) the interactive terminal test environment identified by terminalId, releasing its terminal/session resources. This ends any in-progress test session on that terminal. terminalId comes from immy_dynamic_provider_types_test_environment.
immy_dynamic_provider_type_test_bind_config_form details
immy_dynamic_provider_type_test_bind_config_form details
[ImmyBot] Bind (render/evaluate) the configuration form for a dynamic provider type inside an interactive terminal test environment. This is a POST-as-read (read-only) — it evaluates the form against the supplied values without persisting anything. Pass the terminalId (from immy_dynamic_provider_types_test_environment) and a JSON object body with the current form values/parameters. Returns raw ImmyBot JSON (the bound form model).
immy_dynamic_provider_types_global_reload details
immy_dynamic_provider_types_global_reload details
[ImmyBot] Reload (recompile/re-evaluate) the GLOBAL dynamic provider type identified by id so running provider links pick up its latest definition. id comes from immy_list_dynamic_provider_types. Body (fieldsJson) carries any reload options — pass `` for a plain reload. Returns raw ImmyBot JSON.
immy_dynamic_provider_types_local_reload details
immy_dynamic_provider_types_local_reload details
[ImmyBot] Reload (recompile/re-evaluate) the LOCAL dynamic provider type identified by id so running provider links pick up its latest definition. id comes from immy_list_dynamic_provider_types. Body (fieldsJson) carries any reload options — pass `` for a plain reload. Returns raw ImmyBot JSON.
immy_dynamic_provider_types_reload details
immy_dynamic_provider_types_reload details
[ImmyBot] Reload ALL dynamic provider types on the instance (recompile/re-evaluate every dynamic integration definition). Use after bulk edits. Body (fieldsJson) carries any reload options — pass `` for a plain reload-all. Returns raw ImmyBot JSON.
immy_dynamic_provider_types_test_environment details
immy_dynamic_provider_types_test_environment details
[ImmyBot] Start (provision) an interactive terminal test environment for developing/debugging a dynamic provider type, and get back its terminalId. Pass a JSON object body describing the environment to spin up (typically the provider-type definition/reference and any bootstrap parameters). Use the returned terminalId with immy_dynamic_provider_type_test_bind_config_form and immy_dynamic_provider_types_test_environment_execute_method, then tear it down with immy_delete_dynamic_provider_types_test_environment. Returns raw ImmyBot JSON.
immy_dynamic_provider_types_test_environment_execute_method details
immy_dynamic_provider_types_test_environment_execute_method details
[ImmyBot] Invoke a named provider method inside the interactive terminal test environment while developing a dynamic provider type. Pass the terminalId (from immy_dynamic_provider_types_test_environment), the method name to execute, and a JSON object body with the method arguments. Runs provider code in the test terminal — get user approval before executing. Returns raw ImmyBot JSON (the method result).
immy_get_dynamic_provider_types_global details
immy_get_dynamic_provider_types_global details
[ImmyBot] Get a single GLOBAL (cross-tenant) dynamic provider type by id (from immy_list_dynamic_provider_types), including its definition/script and configuration schema. Returns raw ImmyBot JSON.
immy_get_dynamic_provider_types_local details
immy_get_dynamic_provider_types_local details
[ImmyBot] Get a single LOCAL (tenant-scoped) dynamic provider type by id (from immy_list_dynamic_provider_types), including its definition/script and configuration schema. Returns raw ImmyBot JSON.
immy_list_dynamic_provider_types details
immy_list_dynamic_provider_types details
[ImmyBot] List the dynamic (code-defined) integration provider types configured on the instance (both global and local). Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Use the returned ids with immy_get_dynamic_provider_types_global / immy_get_dynamic_provider_types_local. Returns raw ImmyBot JSON.
immy_update_global_dynamic_provider_type details
immy_update_global_dynamic_provider_type details
[ImmyBot] Update the GLOBAL dynamic provider type identified by id (from immy_list_dynamic_provider_types). Body (fieldsJson) is the full provider-type definition (replace semantics, not a partial patch). Editing a provider type affects every provider link built on it — reload afterwards with immy_dynamic_provider_types_global_reload so running links pick up the change. Returns the updated provider type JSON.
immy_update_local_dynamic_provider_type details
immy_update_local_dynamic_provider_type details
[ImmyBot] Update the LOCAL dynamic provider type identified by id (from immy_list_dynamic_provider_types). Body (fieldsJson) is the full provider-type definition (replace semantics, not a partial patch). Reload afterwards with immy_dynamic_provider_types_local_reload so running links pick up the change. Returns the updated provider type JSON.
Diagnostics & Metrics
immy_application_locks_request_cancellation details
immy_application_locks_request_cancellation details
[ImmyBot] Request cancellation of the operation holding an application lock (a cooperative cancel — it signals the running operation to stop, releasing its lock). Pass a JSON object body identifying the lock/operation to cancel (typically the lock key/id from immy_list_application_locks). Returns raw ImmyBot JSON.
immy_application_logs_source_context details
immy_application_logs_source_context details
[ImmyBot] Set (override) the minimum log level for one application-log source context — raise verbosity on a subsystem while diagnosing, e.g. to Debug/Verbose. Pass a JSON object body with the source context and desired level (see immy_list_application_logs_source_contexts for valid contexts). Clear it later with immy_application_logs_source_context_clear. Returns raw ImmyBot JSON.
immy_application_logs_source_context_clear details
immy_application_logs_source_context_clear details
[ImmyBot] Clear the log-level override for a single application-log source context, returning it to the instance default. Pass a JSON object body identifying the source context to clear (from immy_list_application_logs_source_contexts). Returns raw ImmyBot JSON.
immy_application_logs_source_context_clear_all details
immy_application_logs_source_context_clear_all details
[ImmyBot] Clear ALL application-log source-context level overrides at once, returning every subsystem to the instance default log level. Body (fieldsJson) carries any options — pass `` for a plain clear-all. Returns raw ImmyBot JSON.
immy_application_logs_streaming details
immy_application_logs_streaming details
[ImmyBot] Start/stop or configure live application-log streaming (the diagnostic log tail the ImmyBot UI opens). Pass a JSON object body with the streaming options (e.g. enable/disable, minimum level, source-context filter). Returns raw ImmyBot JSON.
immy_list_application_locks details
immy_list_application_locks details
[ImmyBot] List the currently held application locks (the concurrency guards ImmyBot uses to serialize instance-level operations). Useful for diagnosing why an operation is queued/blocked. Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Returns raw ImmyBot JSON.
immy_list_application_locks_realtime_event_stream details
immy_list_application_locks_realtime_event_stream details
[ImmyBot] Get the realtime event-stream snapshot for application locks — the feed the ImmyBot UI subscribes to for live lock acquire/release events. Read-only diagnostic. Returns raw ImmyBot JSON.
immy_list_application_logs_source_contexts details
immy_list_application_logs_source_contexts details
[ImmyBot] List the known application-log source contexts (the logger source-context categories, e.g. per subsystem) and their current log-level overrides. Use these values with immy_application_logs_source_context to raise/lower verbosity. Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Returns raw ImmyBot JSON.
immy_list_audits_global_dx details
immy_list_audits_global_dx details
[ImmyBot] DevExtreme grid feed of GLOBAL (instance-wide) audit records — who changed what across the instance. Uses skip/take paging (take max 100) plus optional DevExtreme filter/sort JSON and requireTotalCount. Returns raw ImmyBot JSON.
immy_list_audits_local_dx details
immy_list_audits_local_dx details
[ImmyBot] DevExtreme grid feed of LOCAL (tenant-scoped) audit records — who changed what within the current tenant scope. Uses skip/take paging (take max 100) plus optional DevExtreme filter/sort JSON and requireTotalCount. Returns raw ImmyBot JSON.
immy_list_metrics_circuit_breakers details
immy_list_metrics_circuit_breakers details
[ImmyBot] List the provider-link circuit breakers and their current state (closed/open/half-open) — ImmyBot opens a breaker to stop hammering a failing integration. Use this to spot degraded provider links before isolating/resetting one. Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Returns raw ImmyBot JSON.
immy_list_metrics_provider_links details
immy_list_metrics_provider_links details
[ImmyBot] List per-provider-link metrics (throughput, error, and rate-limit health for each integration link). Sieve-paginated: Page + pageSize (max 100) + optional Filters/Sorts. Drill into one link with immy_list_metrics_provider_links_rate_limit_statistics. Returns raw ImmyBot JSON.
immy_list_metrics_provider_links_rate_limit_statistics details
immy_list_metrics_provider_links_rate_limit_statistics details
[ImmyBot] Get the rate-limit statistics for a single provider link (requests, throttles, and backoff windows) by providerLinkId (from immy_list_provider_links or immy_list_metrics_provider_links). Returns raw ImmyBot JSON.
immy_metrics_circuit_breakers_isolate details
immy_metrics_circuit_breakers_isolate details
[ImmyBot] Force a provider-link circuit breaker OPEN (isolate it), immediately halting all traffic to that integration until it is reset. Destructive — it takes the integration offline; get user approval first. Pass a JSON object body identifying the breaker/provider link to isolate (from immy_list_metrics_circuit_breakers). Undo with immy_metrics_circuit_breakers_reset. Returns raw ImmyBot JSON.
immy_metrics_circuit_breakers_reset details
immy_metrics_circuit_breakers_reset details
[ImmyBot] Reset a provider-link circuit breaker back to closed (healthy), resuming traffic to the integration — the counterpart to immy_metrics_circuit_breakers_isolate and the recovery for a breaker that tripped on failures. Pass a JSON object body identifying the breaker/provider link to reset (from immy_list_metrics_circuit_breakers). Returns raw ImmyBot JSON.
Brandings
immy_brandings details
immy_brandings details
[ImmyBot] Create a new branding profile. Provide a JSON object body describing the branding (typically name, logo references, colors, support contact, date/time format). Preview it first with immy_brandings_send_test_email.
immy_brandings_global_default details
immy_brandings_global_default details
[ImmyBot] Promote a branding profile (by id, from immy_list_brandings) to the system-wide default used when no more-specific branding applies. Takes only the branding id in the path; no body.
immy_brandings_send_test_email details
immy_brandings_send_test_email details
[ImmyBot] Send a preview email using the supplied branding values WITHOUT persisting them — useful to visually verify a branding before creating/updating it. Provide a JSON object body with the branding values plus the recipient/preview details. To test SMTP connectivity instead, use immy_smtp_configs_send_test_email.
immy_brandings_validate_time_format details
immy_brandings_validate_time_format details
[ImmyBot] Validate a .NET date-time format string by formatting the current time with it, and return the formatted result. Read-only despite being an HTTP POST — nothing is persisted. The format string travels in the URL path (e.g. timeFormat="yyyy-MM-dd HH:mm"). Use before saving a branding profile's date/time format.
immy_delete_brandings details
immy_delete_brandings details
[ImmyBot] Permanently delete a branding profile by id (from immy_list_brandings). Cannot be undone. If the profile is the global default or referenced by tenants, reassign those first (immy_brandings_global_default).
immy_get_brandings details
immy_get_brandings details
[ImmyBot] Fetch a single branding profile by id (from immy_list_brandings). Returns the full branding configuration (name, logos, colors, support contact, date/time format).
immy_list_brandings details
immy_list_brandings details
[ImmyBot] List all branding profiles visible to the caller. Paginated via Sieve: page (1-based) + pageSize (max 100); filters/sorts accept Sieve expressions. Feed a branding id to immy_get_brandings / immy_update_brandings / immy_delete_brandings, or promote one with immy_brandings_global_default.
immy_list_brandings_support_branding details
immy_list_brandings_support_branding details
[ImmyBot] Fetch the support-sidebar branding override published by the active dynamic provider (the branding shown to end users in the support experience). Takes no parameters.
immy_update_brandings details
immy_update_brandings details
[ImmyBot] Replace a branding profile by id (from immy_list_brandings). Provide the full JSON object body — ImmyBot replaces the profile (HTTP PUT), so include all fields, not just the ones you are changing. Read the current profile with immy_get_brandings first.
Maintenance Email Jobs
immy_maintenance_email_reboot_now details
immy_maintenance_email_reboot_now details
[ImmyBot] Reboot the target computer immediately for a maintenance email (the 'reboot now' link recipients click). DESTRUCTIVE — it forces an immediate reboot of the end user's machine, despite being an HTTP GET. Identify the email by its GUID.
immy_postpone_maintenance_email_job details
immy_postpone_maintenance_email_job details
[ImmyBot] Postpone the scheduled maintenance linked to a maintenance email (the 'postpone' link recipients click). An ACTION despite being an HTTP GET — it reschedules the job. Identify the email by its GUID.
immy_run_maintenance_email_job_now details
immy_run_maintenance_email_job_now details
[ImmyBot] Trigger the scheduled maintenance action linked to a maintenance email to run immediately (the 'run now' link recipients click). This is an ACTION, not a read, despite being an HTTP GET — it starts maintenance on the target computer. Identify the email by its GUID (from a maintenance-email record).
Notifications
immy_delete_notifications_unsilence details
immy_delete_notifications_unsilence details
[ImmyBot] Remove one of the current user's notification silences by its silence id (from immy_list_notifications) — future notifications of that type/object will alert again. Flagged destructive as it deletes the silence record. To create a silence use immy_notifications_silence.
immy_list_notifications details
immy_list_notifications details
[ImmyBot] List the current user's ACTIVE notification silences (the notification types/objects currently muted). Paginated via Sieve: page + pageSize (max 100), filters/sorts. To list the notifications themselves use immy_list_notifications_dx or immy_list_notifications_unacknowledged; add a silence with immy_notifications_silence and remove one with immy_delete_notifications_unsilence.
immy_list_notifications_dx details
immy_list_notifications_dx details
[ImmyBot] List notifications visible to the current user, formatted for the DevExtreme data grid. Paginated via DevExtreme skip + take (take max 100); filter/sort accept DevExtreme expressions; requireTotalCount adds a total. This is the primary read for the notification feed itself.
immy_list_notifications_unacknowledged details
immy_list_notifications_unacknowledged details
[ImmyBot] List the current user's unacknowledged, unresolved notifications, newest first. Optionally cap the result count with limit. Acknowledge them with immy_notifications_acknowledge.
immy_notifications_acknowledge details
immy_notifications_acknowledge details
[ImmyBot] Acknowledge a batch of notifications on behalf of the current user. Provide a JSON body identifying the notifications to acknowledge (typically an array of notification ids or an object wrapping one). List candidates with immy_list_notifications_unacknowledged.
immy_notifications_silence details
immy_notifications_silence details
[ImmyBot] Silence future notifications of a given type for the current user, optionally narrowed to a specific object. type is the notification type (path). Provide objectId to silence only notifications for that object, or omit it to silence the whole type. Remove a silence with immy_delete_notifications_unsilence.
Notification Preferences
immy_get_preferences_tenants details
immy_get_preferences_tenants details
[ImmyBot] Fetch the preferences for a specific tenant by tenant id (from immy_list_tenants). Update them with immy_patch_preferences_tenants.
immy_list_preferences details
immy_list_preferences details
[ImmyBot] Fetch the bundled application, tenant, and user preferences for the current user. Paginated via Sieve params where applicable. Update scopes with immy_patch_preferences_application / immy_patch_preferences_my / immy_patch_preferences_tenants.
immy_patch_preferences_application details
immy_patch_preferences_application details
[ImmyBot] Apply a JSON Patch document to the application-wide (instance) preferences. Provide a JSON Patch array, e.g. [{"op":"replace","path":"/someSetting","value":true}]. Read the current values with immy_list_preferences first.
immy_patch_preferences_my details
immy_patch_preferences_my details
[ImmyBot] Apply a JSON Patch document to the calling user's own preferences. Provide a JSON Patch array, e.g. [{"op":"replace","path":"/emailNotifications","value":false}].
immy_patch_preferences_tenants details
immy_patch_preferences_tenants details
[ImmyBot] Apply a JSON Patch document to a specific tenant's preferences (tenant id from immy_list_tenants). Provide a JSON Patch array, e.g. [{"op":"replace","path":"/someSetting","value":123}]. Read the current values with immy_get_preferences_tenants first.
SMTP Configuration
immy_create_smtp_config details
immy_create_smtp_config details
[ImmyBot] Create the SMTP configuration for a tenant. Provide a JSON object body with the outbound mail settings (host, port, credentials, from-address, TLS, and the tenant id). Verify it first with immy_smtp_configs_send_test_email.
immy_delete_smtp_configs details
immy_delete_smtp_configs details
[ImmyBot] Remove the SMTP configuration for a specific tenant (by tenant id from immy_list_tenants). Destructive — after removal that tenant falls back to inherited/default mail settings until a new config is created.
immy_get_smtp_configs details
immy_get_smtp_configs details
[ImmyBot] Fetch the SMTP configuration for a specific tenant by tenant id (from immy_list_tenants). Returns the outbound mail settings for that tenant.
immy_list_smtp_configs details
immy_list_smtp_configs details
[ImmyBot] List all SMTP configurations visible to the caller (per-tenant outbound mail settings). Paginated via Sieve: page + pageSize (max 100), filters/sorts. Fetch one with immy_get_smtp_configs and test connectivity with immy_smtp_configs_send_test_email.
immy_list_smtp_configs_delivery_logs_dx details
immy_list_smtp_configs_delivery_logs_dx details
[ImmyBot] List SMTP delivery logs for a specific tenant (by tenant id from immy_list_tenants), formatted for the DevExtreme data grid. Paginated via DevExtreme skip + take (take max 100); filter/sort accept DevExtreme expressions; requireTotalCount adds a total. Use to diagnose failed/queued outbound mail.
immy_replace_tenant_smtp_config details
immy_replace_tenant_smtp_config details
[ImmyBot] Replace the SMTP configuration for a specific tenant (by tenant id from immy_list_tenants). Provide the full JSON object body with the outbound mail settings — this replaces the tenant's existing configuration. Read the current one with immy_get_smtp_configs first.
immy_smtp_configs_send_test_email details
immy_smtp_configs_send_test_email details
[ImmyBot] Send a test email using the supplied SMTP settings to verify connectivity — settings are used for the test only. Provide a JSON object body with the SMTP settings and the test recipient. To preview branding instead, use immy_brandings_send_test_email.
Billing
immy_billing_billing_information details
immy_billing_billing_information details
[ImmyBot] Update the billing contact/account information for this ImmyBot instance (billing address, contact, tax details). Provide a JSON object body with the fields to set. Read the current values first with immy_list_billing_information.
immy_billing_cancel_subscription details
immy_billing_cancel_subscription details
[ImmyBot] Cancel this ImmyBot instance's subscription — a billing state change that can end service at the term boundary or immediately depending on the options. The body is usually empty (); pass a JSON object only if the endpoint accepts cancellation options. Reverse with immy_billing_reactivate_subscription.
immy_billing_reactivate_subscription details
immy_billing_reactivate_subscription details
[ImmyBot] Reactivate a cancelled/paused subscription for this ImmyBot instance. The body is usually empty (); pass a JSON object only if the endpoint accepts reactivation options. Inverse of immy_billing_cancel_subscription.
immy_billing_update_addon details
immy_billing_update_addon details
[ImmyBot] Add, remove, or change the quantity of a subscription add-on for this ImmyBot instance. Provide a JSON object body identifying the add-on and its target quantity/state. Review current usage with immy_list_billing_feature_usage_counts and the plan with immy_list_billing_subscription_details.
immy_billing_update_subscription details
immy_billing_update_subscription details
[ImmyBot] Change this ImmyBot instance's subscription (plan/term/quantities). Provide a JSON object body describing the target subscription. Read the current state with immy_list_billing_subscription_details first; to remove the subscription entirely use immy_billing_cancel_subscription.
immy_delete_billing_payment_sources details
immy_delete_billing_payment_sources details
[ImmyBot] Permanently remove a payment source (credit card) from this ImmyBot instance's billing account, by payment-source id (from immy_list_billing_credit_cards). Irreversible — removing the only active payment source may interrupt renewal.
immy_list_billing_billing_platform_details details
immy_list_billing_billing_platform_details details
[ImmyBot] Get the billing-platform details for this ImmyBot instance (which billing provider/platform backs the subscription and its configuration). Read-only. See also immy_list_billing_information and immy_list_billing_subscription_details.
immy_list_billing_credit_cards details
immy_list_billing_credit_cards details
[ImmyBot] List the credit cards / payment sources on file for this ImmyBot instance's subscription. Paginated via Sieve: page (1-based) + pageSize (max 100), plus optional filters/sorts. Remove a payment source with immy_delete_billing_payment_sources.
immy_list_billing_download_invoice details
immy_list_billing_download_invoice details
[ImmyBot] Get a download reference for a billing invoice. Optionally pass invoiceId to target a specific invoice; omit it for the default/latest. Returns a JSON payload (e.g. a download URL / invoice metadata) — this is a normal JSON read, not a binary stream.
immy_list_billing_feature_usage_counts details
immy_list_billing_feature_usage_counts details
[ImmyBot] Get the metered feature-usage counts for this ImmyBot instance (the quantities that drive add-on / subscription billing). Read-only. Adjust add-ons with immy_billing_update_addon.
immy_list_billing_information details
immy_list_billing_information details
[ImmyBot] Get the billing contact/account information on file for this ImmyBot instance (billing address, contact, tax details). Read-only. Update it with immy_billing_billing_information.
immy_list_billing_product_catalog details
immy_list_billing_product_catalog details
[ImmyBot] Get the billing product catalog — the plans/products available for this ImmyBot instance's subscription. Read-only. For the individual line items use immy_list_billing_product_catalog_items.
immy_list_billing_product_catalog_items details
immy_list_billing_product_catalog_items details
[ImmyBot] List the individual items in the billing product catalog (the purchasable products/add-ons and their pricing). Paginated via Sieve: page + pageSize (max 100), plus optional filters/sorts. For the catalog summary use immy_list_billing_product_catalog.
immy_list_billing_subscription_details details
immy_list_billing_subscription_details details
[ImmyBot] Get the current subscription details for this ImmyBot instance (plan, status, term, add-ons, renewal). Read-only. Change it with immy_billing_update_subscription / immy_billing_update_addon, or cancel with immy_billing_cancel_subscription.
System
immy_change_requests_approve details
immy_change_requests_approve details
[ImmyBot] Approve a deployment change-request by id (from immy_list_change_requests_dx), applying the proposed target-assignment edit. The body is usually empty (); pass a JSON object only if the endpoint accepts approval options.
immy_change_requests_comment details
immy_change_requests_comment details
[ImmyBot] Add a comment to a deployment change-request by id (from immy_list_change_requests_dx) without changing its approval state. Provide a JSON object body with the comment text.
immy_change_requests_deny details
immy_change_requests_deny details
[ImmyBot] Deny (reject) a deployment change-request by id (from immy_list_change_requests_dx), declining to apply the proposed edit. The body is usually empty (); pass a JSON object only if the endpoint accepts a denial reason. To request revisions instead use immy_change_requests_require_changes.
immy_change_requests_require_changes details
immy_change_requests_require_changes details
[ImmyBot] Send a deployment change-request back for revision by id (from immy_list_change_requests_dx) — neither approving nor denying, but requesting changes from the submitter. The body is usually empty (); pass a JSON object only if the endpoint accepts requested-change details.
immy_delete_change_requests details
immy_delete_change_requests details
[ImmyBot] Permanently delete a deployment change-request by id (from immy_list_change_requests_dx), discarding the proposed change without applying it. Irreversible. To reject-but-keep for revision use immy_change_requests_deny or immy_change_requests_require_changes.
immy_get_ephemeral_session details
immy_get_ephemeral_session details
[ImmyBot] Get the state of a specific ephemeral-agent session, keyed by ephemeral-session id, agent-instance id, and provider-agent id (all from the ephemeral-agent launch flow — see immy_launch_ephemeral_agent / immy_list_computers_ephemeral_agent). Read-only.
immy_get_webhooks details
immy_get_webhooks details
[ImmyBot] Get a webhook configuration by id. Returns the webhook's target URL, events, and settings. Update it with immy_webhooks.
immy_list_change_requests_dx details
immy_list_change_requests_dx details
[ImmyBot] List deployment change-requests (proposed edits to target-assignments awaiting approval) as a DevExtreme grid feed. Uses DevExtreme paging: skip + take (take max 100), with optional filter/sort (DevExtreme JSON expressions) and requireTotalCount. Act on a change-request with immy_change_requests_approve / immy_change_requests_deny / immy_change_requests_require_changes / immy_change_requests_comment.
immy_list_change_requests_open_count details
immy_list_change_requests_open_count details
[ImmyBot] Get the count of open (pending) deployment change-requests. Read-only — a quick badge/summary value. List the requests themselves with immy_list_change_requests_dx.
immy_list_ephemeral_session_development_latest_ephemeral_binary details
immy_list_ephemeral_session_development_latest_ephemeral_binary details
[ImmyBot] Get metadata for the latest development ephemeral-agent binary (version/hash/reference used to launch ephemeral agents). Read-only JSON — not a binary stream. Related: immy_launch_ephemeral_agent, immy_get_ephemeral_session.
immy_list_immy_agent_metadata_agent_hash details
immy_list_immy_agent_metadata_agent_hash details
[ImmyBot] Get the current Immy-agent binary hash/metadata (the version fingerprint managed endpoints are expected to run). Read-only — useful for verifying agent currency across the fleet.
immy_list_system_immy_support_access_grant_details details
immy_list_system_immy_support_access_grant_details details
[ImmyBot] Get the details of any current Immy (vendor) support-access grant on this instance — who was granted access and until when. Read-only. Toggle access with immy_system_enable_immy_support_access / immy_system_disable_immy_support_access.
immy_list_system_releases details
immy_list_system_releases details
[ImmyBot] List the available ImmyBot platform releases (versions on the update channels). Paginated via Sieve: page + pageSize (max 100), plus optional filters/sorts. Change which channel this instance follows with immy_system_update_release_channel; apply an update with immy_system_pull_update.
immy_list_system_timezones details
immy_list_system_timezones details
[ImmyBot] List the timezones known to this ImmyBot instance (the valid identifiers used by schedules and maintenance windows). Read-only reference lookup.
immy_system_disable_immy_support_access details
immy_system_disable_immy_support_access details
[ImmyBot] Revoke Immy (vendor) support access to this instance. The body is usually empty (); pass a JSON object only if the endpoint accepts options. Re-grant with immy_system_enable_immy_support_access; inspect current state with immy_list_system_immy_support_access_grant_details.
immy_system_enable_immy_support_access details
immy_system_enable_immy_support_access details
[ImmyBot] Grant Immy (vendor) support access to this instance, letting ImmyBot support staff assist. Provide a JSON object body if the endpoint accepts grant options (e.g. a duration); otherwise send an empty object (). Revoke with immy_system_disable_immy_support_access.
immy_system_is_immy_support_access_granted details
immy_system_is_immy_support_access_granted details
[ImmyBot] Check whether Immy (vendor) support access is currently granted on this instance (a read-only status check, sent as an HTTP POST — it makes no changes). The body is usually empty (); pass a JSON object only if the endpoint accepts query options. For the full grant record use immy_list_system_immy_support_access_grant_details.
immy_system_pull_update details
immy_system_pull_update details
[ImmyBot] Trigger this ImmyBot instance to pull and apply a platform update — a disruptive maintenance action that can restart backend services and briefly interrupt the instance. The body is usually empty (); pass a JSON object only to target a specific release. Review available releases with immy_list_system_releases first.
immy_system_request_form_support details
immy_system_request_form_support details
[ImmyBot] Submit a support request via the in-product support form. Provide a JSON object body with the request details (subject/description/contact). Sends the request to ImmyBot support.
immy_system_request_session_support details
immy_system_request_session_support details
[ImmyBot] Request a live support session (interactive assistance) from ImmyBot support. Provide a JSON object body with the session-request details. Often paired with immy_system_enable_immy_support_access so support staff can connect.
immy_system_restart_backend details
immy_system_restart_backend details
[ImmyBot] Restart this ImmyBot instance's backend services — disruptive: in-flight maintenance sessions and API calls can be interrupted while services cycle. The body is usually empty (); pass a JSON object only if the endpoint accepts restart options. Use with care.
immy_system_update_release_channel details
immy_system_update_release_channel details
[ImmyBot] Change which release channel this ImmyBot instance follows (e.g. stable vs preview). Provide a JSON object body naming the target channel. This governs which releases immy_system_pull_update will offer; list releases with immy_list_system_releases.
immy_webhooks details
immy_webhooks details
[ImmyBot] Update a webhook configuration by id (sent as an HTTP POST to /webhooks/). Provide a JSON object body with the webhook fields to set (target URL, subscribed events, settings). Read the current state first with immy_get_webhooks.
More in Tools Reference
Atera ToolsAuvik ToolsAvanan (Check Point Harmony Email) ToolsConnectWise Sell ToolsStill need help? Ask the team