HighBond API domain change FAQ

Diligent One is migrating all HighBond API traffic from highbond.com to the Diligent One Platform domain, diligentoneplatform.com.

For customers in commercial regions, the current planned cutoff date for HighBond API endpoints using the legacy highbond.com domain is December 16, 2026, subject to final confirmation.

For scripts running within the Robots application, no action is required from you. Diligent One will automatically update references from highbond.com to the corresponding diligentoneplatform.com references.

Make sure your firewall rules, allowlists, and network configurations for Robots Agent servers are updated to allow the applicable Diligent One Platform hosts. You should also update any external scripts or applications that directly call HighBond API endpoints to use the Diligent One Platform domain, to ensure continued connectivity after the legacy domain is retired.

1. What is changing?

HighBond API requests that currently use a highbond.com host will move to the corresponding diligentoneplatform.com host.

For example:

https://apis-us.highbond.com/v1/orgs/11594/robots

will become:

https://apis-us.diligentoneplatform.com/v1/orgs/11594/robots

Only the hostname is changing. The region, API version, organization ID, endpoint path, query string, request method, headers, payload, and authentication are intended to remain the same.

2. Do I need to edit my ACL Robot scripts?

You do not need to edit the Robot source script solely because of this hostname change. Diligent One will automatically detect highbond.com API references in ACL Robot scripts and update them to the corresponding diligentoneplatform.com references.

The updated script will be saved as a new version and activated for the Robot.

You should:

  • Validate your critical ACL Robot jobs.

  • Review any network controls that could block the new domain.

  • Use the updated script version as the starting point for any future script edits.

Avoid activating or editing from an older script version that still references the highbond.com domain, as those references may fail after the API migration is implemented.

3. Do I need to edit my HighBond Robot scripts?

You do not need to edit the Robot source script solely because of this hostname change. . Diligent One will automatically detect highbond.com API references in HighBond Robot scripts and update them to the corresponding diligentoneplatform.com references.

The updated script will be saved as a new version and activated for the Robot.

You should:

  • Test your critical jobs.

  • Review any strict proxy, firewall, TLS-inspection, private-connectivity, or domain-allowlist rules.

  • Use the automatically updated script version as the starting point for any future script edits.

Avoid activating or editing from an older script version that still references the highbond.com domain, as those references may fail after the migration is implemented.

4. Do I need to edit my Workflow Robot scripts?

You do not need to edit the Robot source script solely because of this hostname change. . Diligent One will automatically detect highbond.com API references in Workflow Robot scripts and update them to the corresponding diligentoneplatform.com references.

The updated script will be saved as a new version and activated for the Robot.

You should:

  • Test your critical jobs.

  • Review any strict proxy, firewall, TLS-inspection, private-connectivity, or domain-allowlist rules.

  • Use the automatically updated script version as the starting point for any future script edits.

Avoid activating or editing from an older script version that still references the highbond.com domain, as those references may fail after the migration is implemented.

5. Will Diligent One change my Robot source code?

Diligent will systematically detect highbond.com API references in ACL, HighBond, and Workflow Robot scripts and update them to the corresponding diligentoneplatform.com references.

The updated script will be saved as a new version and activated for the Robot. You do not need to edit the script yourself.

Your existing script version will remain available.

6. Do I need a new API token or password?

No new token is expected solely because the API hostname is changing. Existing authentication, password definitions, and request credentials are intended to continue working.

You should still test authentication and confirm that your network controls allow requests to the new API host.

7. Which API commands are included in the migration?

The documented migration scope includes the API command family used by Analytics and ACL scripts that can run in Robots:

  • HB_API_GET

  • HB_API_POST

  • HB_API_PUT

  • HB_API_PATCH

  • HB_API_DELETE

Validate any direct HTTP calls or custom API wrappers separately, as these are outside the documented automatic Robot script update scope.

8. What do I need to update outside Robots?

Automatic Robot script updates do not update your network controls or external integrations.

Make sure you update integrations that call HighBond APIs outside the Robots execution path, including:

  • ACL Desktop scripts

  • External schedulers

  • Custom applications

  • Middleware or integration platforms

  • Direct API clients and scripts

  • Firewall, proxy, TLS-inspection, private-connectivity, and domain-allowlist configurations

For strict allowlists, use the Diligent One Platform hostnames applicable to your organization and region. A wildcard such as *.diligentoneplatform.com on port 443 may be suitable for some environments, subject to your security policy.

9. Why are firewall, proxy, TLS-inspection, private-connectivity, and allowlist updates important?

Automatic Robot script updates change the API hostname in the script, but they do not change your organization's network controls.

If the new Diligent One Platform hostname is not permitted, Robot requests may fail even though the script has been updated successfully.

Before the migration, confirm that every network path used by your Robots can reach the applicable Diligent One Platform API and Robot hosts over HTTPS on port 443.

Review and update:

  • Outbound firewall rules

  • Proxy configuration and authentication

  • TLS-inspection policies and certificate handling

  • Private-connectivity routes

  • Domain and URL allowlists

Validate these settings from each applicable execution path, including cloud and on-premises agents and each supported commercial API region.

If your security policy does not allow wildcards, allow the exact Diligent One Platform hostnames for your organization and region.

10. What should I do now?

Use the following checklist to prepare for the migration:

Inventory ACL, HighBond, and Workflow Robots that call HighBond APIs.

Identify API calls that run outside the Robots execution path.

Update direct integrations to use the Diligent One Platform API host.

Review firewall, proxy, TLS-inspection, private-connectivity, and domain-allowlist rules.

Run and validate critical Robot jobs before the confirmed cutoff date.

Confirm that scheduled tasks, retries, linked Robots, authentication, response handling, and audit history behavior continue to work as expected.

11. Will my data or environment change?

The domain migration changes the URL used to access the service and API. Your data and underlying environment are not expected to change as a result of the hostname migration.

12. Does this apply to every region?

The current planned cutoff applies to commercial regions.

GovCloud and FedRAMP environments follow separate timelines and should not use the commercial-region cutoff without confirmation from Diligent One.

13. Does this change ACL Analytics activation?

ACL Analytics activation is a separate consideration from Robot API calls.

Some older ACL Analytics versions have separate domain and activation timelines and may require an upgrade or an alternative activation method, such as token or offline activation.

Contact Diligent Support or your Diligent representative for guidance based on your ACL Analytics version and hosting environment.

14. Do I need to update bookmarks or login settings?

This FAQ focuses on Robot and API behavior.

As part of the broader domain migration, you should also:

  • Update relevant bookmarks.

  • Review your Diligent One Platform SSO configuration.

  • Ensure users can access the Diligent One Platform domain.

15. Do I need to open a support ticket in advance?

There is no need to open a support ticket solely to track this migration.

Contact Diligent Support if:

  • A Robot run fails.

  • A request is not translated as expected.

  • A legacy host is skipped.

  • Authentication fails.

  • Your environment has a network or compatibility exception.

16. Important timing note

The December 16, 2026 commercial-region API cutoff and the automatic Robot script-update behavior are based on the current planned migration guidance.

Diligent will confirm the final date, supported Robot scope, and any exceptions before publishing final customer communications.