sanctions.io Sandbox Setup for Salesforce

This guide explains how sanctions.io API tokens work within your Salesforce integration, and how to set up a proper testing environment using Salesforce Sandbox alongside the sanctions.io Sandbox token.

API Token Types

sanctions.io provides two types of API tokens. Both are compatible with any Salesforce environment, whether production or a sandbox. The distinction between token types refers to the sanctions.io database being queried, not your Salesforce environment.

Sandbox Token

The Sandbox token queries a dedicated sanctions.io sandbox database, separate from live sanctions data. It is designed for testing and integration validation.

Key characteristics:

Fetches records only from the sanctions.io sandbox database
Does not count against your screening package usage
Use the names available in the sandbox data when querying records
Test data is available as a CSV file with Sandbox Data (provided separately)

Production Token

The Production token queries live, real-world sanctions data.

Key characteristics:

Fetches records from the live sanctions database
Counts against your screening package usage regardless of which Salesforce environment it is used in
Should only be used when you are ready to go live

Set up a Testing Environment

To test your integration without affecting production metrics or consuming package usage, use the following combination:

Salesforce Sandbox + sanctions.io Sandbox Token

This pairing ensures:

No impact on your production Salesforce data, workflows, or app metrics
No API calls consumed from your sanctions.io subscription package
A realistic testing environment that mirrors production behavior

It is important to understand that using a Salesforce Sandbox alone is not sufficient to avoid consuming API credits. If a production sanctions.io token is used — even in a Salesforce Sandbox environment — those calls will count against your package. Always pair the Salesforce Sandbox with the sanctions.io Sandbox token during testing.

Token and Environment Compatibility

Salesforce Environment	sanctions.io Token	Counts Against Package?	Queries Live Data?
Production	Production	✅ Yes	✅ Yes
Production	Sandbox	❌ No	❌ No
Sandbox	Production	✅ Yes	✅ Yes
Sandbox	Sandbox	❌ No	❌ No

Generate a Sandbox Token via Dashboard

Log in to app.sanctions.io.
From the left-side menu, go to Settings → API & Webhooks → API tokens
Click Create token in the top-right corner.
In the Create API token dialog, enter a Name for the token. Toggle Sandbox, then click Create token.
Copy your token and add it to your Salesforce sandbox Instance.
Download the sanctions.io sandbox dataset to start testing.

Download Sample Records for Testing

Download the sandbox dataset (CSV) here. It contains sample Individuals and Companies pulled from real screening lists, so you can test both workflows:

- Individuals → add as Contacts or Leads
- Companies/Entities → add as Accounts

Each record includes a data_source column (e.g. SDN, UK-SANCTIONS, PEP, INTERPOL, FBI, AUL, CFSP, CANADA-SEMA, SWISS-SECO). You can enable all the data sources shown in the CSV at once, or enable them one at a time as you test specific records; See Enabled Data Sources for how to configure this.

Note: Requests using data outside this dataset won't return any results. Your Sandbox token only works with this Sandbox dataset. It cannot be used with production data.

How to Install the App in Your Sandbox Environment

To install the sanctions.io app in your Salesforce Sandbox environment, contact us at help@sanctions.io to receive your installation link.

We're here to help!

We offer hands-on onboarding support to guide you through configuring the integration to match your specific use case.

For any additional questions or further assistance, please don’t hesitate to reach out to our support team.

Chat: Available directly in the portal and Help Center page
Email: help@sanctions.io