Connection, Endpoints and Sandboxes
The aprity package in your org talks to the aprity service over HTTPS. This page explains how that connection is set up, which addresses are involved, and how to handle sandbox refreshes.
How the package reaches aprity
- The package ships a Remote Site Setting for the aprity API, so Salesforce allows the callouts. It does not use Named Credentials.
- The environment your org talks to is set at registration, from your activation code. The setup wizard shows it before you register (This org will be registered on: …). The default environment is Europe (France).
- At registration, aprity issues a signing secret unique to your installation. The package stores it in a protected setting that neither admins nor custom Apex can read, and signs every call with it.
You do not need to configure any endpoint by hand.
Addresses used by aprity
For the default environment:
| Address | Used for |
|---|---|
https://api.aprity.ai | Calls from the aprity package (registration, analyses, status) |
https://<your-slug>.app.aprity.ai | The web portal, opened in your users' browsers |
https://mcp.aprity.ai | The Remote MCP server used by AI clients (Intelligence and Trial) |
https://help.aprity.ai | This help centre |
If your company filters outbound web traffic, allow these addresses for your users' browsers. The package's own callouts leave from Salesforce, not from your network.
The package also contains two CSP Trusted Sites for components that are no longer used. They are inactive; leave them as they are.
Remote Site Settings
| Name | URL | Status |
|---|---|---|
FR_Aprity_API | https://api.aprity.ai | Active. Used by every org on the default environment. |
FR_Aprity_API_Dev | https://api.dev.aprity.ai | Active. Used only by orgs registered with an aprity internal-environment code. |
Do not deactivate or edit FR_Aprity_API: every call from the package would fail. See Service Starting Up.
Sandbox refresh
A sandbox refresh gives the sandbox a new Salesforce org ID and copies the aprity settings from the source org, including the source org's registration and signing secret. aprity treats a refreshed sandbox as a new org:
- The package checks the current org ID before every call. A copied registration no longer matches, so the sandbox cannot act as the source org.
- The aprity tab goes back to the setup wizard, with the message This installation belongs to another organization or its identity cannot be verified. An administrator clicks Reset this local connection. This removes the copied connection and signing key from the sandbox only; the source org is not changed.
- Register the sandbox with a new activation code, then create its External Client App: External Client Apps do not survive a refresh.
Clean up automatically at refresh
The package includes an Apex class, aprity Sandbox Post Copy, that clears the copied aprity connection when the sandbox is created or refreshed. Salesforce runs it only if you select it:
Setup > Sandboxes > Create or Refresh > Apex Class > aprity Sandbox Post Copy
It never contacts aprity and never affects the source org. You still need a new activation code to register the sandbox.
Because a refreshed sandbox is registered as a new org, its documentation history starts again with its first analysis. For questions about a refreshed sandbox, contact contact@aprity.ai.