Use the archived client remote API references

Archived instructions for existing Fusion Owned installations; labels and available controls depend on the installed build.

Original reference links

The legacy **Client Remote API** article was headed **Updated V2** and linked to:

- [Run the archived collection in Postman](https://app.getpostman.com/run-collection/23443351-b06ea235-ab57-4234-a15e-a27de8258e89?action=collection%2Ffork&collection-url=entityId%3D23443351-b06ea235-ab57-4234-a15e-a27de8258e89%26entityType%3Dcollection%26workspaceId%3D2257c4db-6d2b-424b-86d6-ed1bac2e4fc4).

- [Archived PHP example reference: api.zip](https://downloads.dhru.com/io/afaebd49-abef-4a83-8e6b-7a0ba338ea30/8fb6bc21-1d1c-4d74-952f-a4351eea9773_api.zip).

These are the original article's reference URLs; the archive does not include their files or verify their present availability. The heading Updated V2 refers to that legacy API reference, not the current DHRU V2 platform.

Match examples to the installed build

Identify the Fusion Owned build and the required operation before running an example. Inspect downloaded code and replace its sample connection values only in a private test configuration. Do not assume a current Fusion PRO or DHRU V2 endpoint accepts the same fields or authentication.

Prepare an integration question

If the collection or sample does not match your installation, provide the operation name, HTTP method and endpoint path, expected result and a redacted error. Include the order reference when relevant. Remove authorization headers, API keys, passwords and customer data from examples; ask for the build-specific request contract rather than guessing parameters.