We’ve extended the List Subscriptions endpoints to return Deal Based subscriptions together with Total Volume subscriptions.

All endpoints for listing subscriptions and Get subscription by the key now return both subscription types. (Deal Based and Total Volume). This means the Commercial API allows you to get everything that belongs to a specified reseller.

Key capabilities:

• Retrieve Deal Based and Total Volume subscriptions together for a given reseller

We’ve extended the documentation with the list of Deal Based product codes.

The documentation now lists the Deal Based product codes that may be returned by the API, in addition to the existing Total Volume codes. We’ve also introduced a fallback product code, W99999, which may be returned for non-commercial products or when a product code cannot be identified from the available data.

For more details, please refer the Commercial API documentation.

The latest Elements API release adds new fields to the invitations object returned by the Send new device invitations and List invitations endpoints (POST and GET /invitations/v1/invitations). These fields provide the caller with the urls sent with the invite.

This is an additive, backward-compatible change. Existing integrations continue to work without modification. New fields are populated when they are present in the invitation. The actual urls are invite specific.

New top-level fields

In both service’s responses:

• androidLink (string): Link to the android installer
• iosLink (string): Link to the iOS installer
• windowsLink (string): Link to the Windows installer
• macLink (string): Link to the Mac installer

See the full Elements API specification for details: 

https://connect.withsecure.com/api-reference/elements#get-/invitations/v1/invitations

The latest Elements API release brings a new audit log listing operation.

This service exports the same data as you see in the elements UI when you go to the audit logs section. The data can be localized to all the languages our portal supports.

See the full Elements API specification from here

Automated subscription provisioning for Halo PSA and Autotask PSA

No more manual subscription setup. If you manage WithSecure™ Elements for your customers through Halo PSA or Autotask PSA, you can now skip the manual work of creating and updating customer organizations and subscriptions in the Partner Portal entirely — it happens automatically from the billing tools you already use.

What’s new

• Organizations and subscriptions provision themselves. Add a WithSecure™ product to a customer’s recurring invoice (Halo PSA) or recurring service contract (Autotask PSA), and the matching Elements subscription (and organization) is created automatically — no separate step in the Partner Portal or interaction with WithSecure’s support
• Seat counts stay in sync. The quantity/units you set on the invoice or contract line item controls the number of seats available for that customer. Need to add or remove seats later? Just update the quantity
• One less system to reconcile. Because provisioning is driven by your PSA’s billing data, your customer subscriptions and your invoicing stay aligned by default, cutting down on mismatches between what you’re billing and what’s actually provisioned.
• Fast turnaround. New subscriptions and seat changes are picked up automatically within 15 minutes — or trigger it instantly with a one-click “Sync sites” action in the Elements Security Center if you don’t want to wait.
• Clear visibility when something needs attention. If a customer is missing required billing details (like address or a billing contact), provisioning simply won’t happen for that account, and you can see exactly why in the integration logs — no silent failures.

Why it matters

Previously, keeping WithSecure™ subscriptions in sync with what you’d sold a customer meant maintaining them twice: once in your PSA for billing, and once in the Partner Portal for provisioning. That’s manual effort and a chance for the two to drift out of sync. Now your recurring invoices and contracts are the single source of truth — set it up once, and every new customer, upsell, or seat change flows straight through.

Availability

Available now to WithSecure Partners using the Halo PSA or Autotask PSA integrations in the Elements Security Center. Just turn on Provisioning in the integration configuration to get started. Not available for free trials or company-managed subscriptions.

Learn how to set it up: Halo PSA Integration · Autotask PSA Integration

Request for feedback

As this is the first release of automated provisioning, we’d be delighted to hear your feedback on how to improve it.

You can now check the RMM integration logs in the Elements Security Center when new Elements agent installations are made through the integration. This helps you verify that the integration is working.
The logs can be found for each integration under Management > Integrations, and via “Logs” for each active integration.

We’ve introduced a new endpoint to update the information of a licensee:

Change Company Information

POST /company?existing_buyer_assigned_account_id={existing_buyer_assigned_account_id}

This endpoint allows you to update the details of a licensee, including its name, buyer assigned account ID, and legal entity information (VAT number and postal address).

Key capabilities:

• Update the licensee’s official name
• Update the partner’s internal reference ID (buyer assigned account ID) for the licensee
• Update the licensee’s legal entity information, including VAT number and postal address

For full endpoint details, refer to the API documentation.

We’ve extended the response of the Get Total Volume Resellers endpoint with additional reseller details:

The response now includes new fields for each reseller, giving distributors a richer view of their contracted resellers. In additional to that, Deal Based resellers now returned in the API and can be tracked as well

New fields per reseller:

• total_volume – Indicates whether the reseller has an active Total Volume Frame Agreement allowing to work in the Total Volume model
• deal_based – Indicates whether the reseller has active Partner Deal Terms allowing to act in the Deal Based model
• partner_portal_enabled – Indicates whether the reseller is a Partner Portal user
• address – Reseller’s billing address, including street, city, postal code, state code, and country

Important notes:

• reseller_name and reseller_account_id remain required fields within each reseller entry
• New fields are optional and may not be present for all resellers depends on available data

For full response details, refer to the API documentation.

You can now control which kinds of security events create tickets in your PSA tool. Previously every supported event automatically opened a ticket; now each PSA integration can be configured to receive only the ticket types you care about.

The currently supported event types are:

* BCD — broad context detections
* XM — Exposure management recommendations

You will find the configuration from the Elements Security Center under “integrations” → Configure for your PSA.

We have released integration logs for evaluating how the PSA/RMM integration is working. This can be helpful in debugging your PSA/RMM integration health.

You will find the integration logs from Elements Security Center, Management → Integrations .→ Logs, next to your PSA/RMM item.

The latest Elements API release adds new fields to the computer device object returned by the Query devices endpoint (GET /devices/v1/devices). These fields provide richer visibility into device security posture, BitLocker encryption status, and policy configuration.

This is an additive, backward-compatible change. Existing integrations continue to work without modification. New fields are populated when reported by the agent on the device and may be absent on older agents or non-applicable platforms.

New top-level fields

Security policy and tamper protection (reported by the Windows agent):

• allowUsersToTurnOffSecurityFeatures (boolean): Whether users are allowed to turn off security features on the device
• allowUsersToUninstallProduct (boolean): Whether local users are allowed to uninstall the security product
• tamperProtectionEnabled (boolean): Whether tamper protection is enabled
• uninstallationPasswordSet (boolean): Whether an uninstallation password has been configured
• uninstallationPasswordEmpty (boolean): Whether the uninstallation password is empty (not configured or blank)

BitLocker and disk encryption (reported by the Windows agent):

• bitlockerOverallProtectionStatus (string): Overall BitLocker protection status (all, some, or none)
• bitlockerRecoveryKeysCollectionEnabled (boolean): Whether BitLocker recovery key collection is enabled in the device’s policy
• bitlockerRecoveryKeysCollectionSuccess (boolean): Whether the most recent BitLocker recovery key collection completed successfully
• diskEncryptionPolicy (string): Disk encryption policy (profile protection setting) applied to the device
• policyUseTpm (string): Policy setting for using the Trusted Platform Module (TPM)
• policyUseTpmWithStartupPin (string): Policy setting for using TPM with a startup PIN
• tpmAvailable (boolean): Whether a TPM chip is available on the device
• encryptedDrives (array): List of drives and their BitLocker encryption status (see below)

Device lifecycle (reported by the agent):

• lastRestartTime (string, date-time): Date and time of the last device restart (ISO 8601 format)

New fields in encryptedDrives items

Each entry in the encryptedDrives array includes:

• drive (string): Drive letter designation (for example c:)
• driveType (string): Drive type (system, fixed, or removable)
• systemDrive (boolean): Whether this is the system drive
• encryptionStatus (string): Current status (fully_decrypted, fully_encrypted, encryption_in_progress, decryption_in_progress, encryption_paused, or decryption_paused)
• encryptionPercentage (integer): Percentage of the drive that is encrypted (0–100)
• encryptionMethod (string): Encryption algorithm and key size (for example xts_aes_256, aes_128, hardware_encryption)
• protectionStatus (boolean): Whether BitLocker protection is active on the drive
• protectors (array of strings): Key protector types configured (for example tpm, numeric_password, tpm_and_pin)
• bitlockerRecoveryKeyId (string): BitLocker recovery key identifier in Windows GUID format
• autounlock (boolean): Whether auto-unlock is enabled for this drive
• autounlockStored (boolean): Whether an auto-unlock key for another drive is stored on this drive
• pinRequested (boolean): Whether a BitLocker PIN has been requested
• pinPostponed (boolean): Whether the user has postponed setting a BitLocker PIN

See the full Elements API specification for details: Query devices