InterAction Cloud supports programmatic data imports through a fully code-driven and authenticated API flow. This allows firms to upload data without requiring a user to manually log in and upload a file through the InterAction UI.
The API flow is designed to support both one-time imports and recurring, automated imports.
For recurring imports, the client's development team will set up an automated process that runs on their desired schedule, generates the import file, and submits it to InterAction through the API.
How Data Imports Work via API
The overall process has five main steps:
Figure: End-to-end API import flow, from credential creation through scheduled processing.
Step 1 — Create API credentials
A firm administrator creates a client ID and secret in Firm Settings in the InterAction UI.
These credentials are specific to the firm/tenant and can be securely shared with the firm's development or integration team. Multiple credentials can be created for a firm if needed.
The credentials are created once and can then be reused for future imports.
Step 2 — Get an OAuth 2.0 access token
The client's application uses the client ID and secret, along with the appropriate tenant information, to authenticate through the OAuth 2.0 provider. InterAction returns a short-lived bearer token.
The client application uses this token when making authenticated API requests.
Step 3 — Request an upload URL
Using the bearer token, the client's application calls the import API and provides the information needed for the import, such as:
- Object type
- Template ID
- Folder ID, where applicable
- Scheduled processing time
InterAction returns a pre-signed upload URL and an import job ID.
Step 4 — Upload the file
The client's application uses the pre-signed URL to upload the CSV file directly to InterAction's storage.
No browser interaction or manual upload is required.
The upload itself does not require an authorization header because the pre-signed URL provides the necessary access.
Step 5 — Process the import
Once the file is uploaded, InterAction processes it at the scheduled time using the selected template and applicable business rules.
The client can use the import job ID and History & Logs to track the status of the import and identify any errors.
Recurring Import Requirements at a Glance
Because the API flow is push-based, InterAction never reaches into a client's environment to retrieve a file — the client's own system initiates every step and pushes the file to InterAction. The table below summarizes what must be true on the client side for a recurring import to run on its own.
| Requirement | What It Means |
| API credentials | A client ID and secret created once in Firm Settings; reused for every scheduled run. |
| Client-side scheduler | The client runs its own scheduling tool (cron job, cloud scheduler, or integration platform) to trigger the import at the desired time. |
| File generation & hosting | The client generates the CSV file on its own systems at run time. InterAction does not need — or have — direct access to the client's servers or file storage. |
| Fresh OAuth 2.0 token | A new bearer token is requested for each run using the existing credentials; no new credentials are needed. |
| New pre-signed upload URL | A new upload URL and import job ID are requested for every run; the client's application pushes the file to that URL rather than InterAction pulling it. |
| Monitoring | The client retains the import job ID and checks History & Logs to confirm success or catch failures. |
Bottom line: a recurring import can exist even if InterAction has no access to the client's server — the model is push, not pull. The client's automated process must generate the file and send it to InterAction on schedule; InterAction cannot go fetch it on its own.
How Recurring Imports Work
For recurring imports, the client will need to automate the API flow on their side. For example, a client may want to send updated contact data to InterAction every night at 2:00 AM. The client would set up a scheduled job in their environment that runs the import process automatically.
What the client needs to do
Set up a recurring schedule
The client creates a scheduled job using their existing scheduling or automation technology. This could be a cron job, cloud-based scheduler, integration platform, or another enterprise scheduling tool.
For example: Run the contact import every night at 2:00 AM.
Generate the import file
At the scheduled time, the client's system retrieves the latest data from their source system and creates a CSV file using the required InterAction or custom template and format.
Authenticate
The application uses the firm's existing client ID and secret to obtain a new OAuth 2.0 bearer token.
The client does not need to create new credentials for each import.
Request a new upload URL
For each import, the application calls the import API and requests a new pre-signed upload URL.
The application provides the appropriate object type, template, destination, and scheduled processing time.
Upload the file
The application uploads the newly generated file to the pre-signed URL.
Monitor the import
The application should retain the import job ID and monitor the result of the import. The client can use this information to identify successful imports or failures and determine whether additional action is needed.