Custom API Source Connector
The Custom API source connector in DataSync lets you connect to any programming interface (API) for data extraction and integration. This connector supports APIs by uploading an API Profile file (.apip) and/or table definitions (.rsd files), then specifying connection properties as needed.
To define an API, you only need to upload the API Profile file (.apip extension) and/or Tables (.rsd files) and specify the properties (connection strings) by manually adding them through the Additional Connection Properties section.
After creating all required source connections, configure your destination source to complete the connection setup.
You need to create API profiles (.apip or .rsd files) before you can configure a Custom API source connection. For details, see Understand API Profile Structure, and follow the steps in Build a Custom API Profile.
Create a source connection in DataSync
- Log in to DataSync.
- From the welcome screen, select Connections.
- Next to Source Connections, click New.
- Select Custom API.
- In the Connection Properties panel, enter the connection properties.
- (Optional) In the Additional Connection Properties panel, select Add property and enter the parameters for each property.
- In the Advanced Settings panel, configure the settings, including the Tracking Type and other values according to your requirements.
- Click Save.
Parameters
Connection properties
| Parameter | Description |
|---|---|
| Description | Unique name for the API connection. Example: Custom API |
| Authentication Type | Authentication method used by the API:
|
| Verbosity |
|
| API Profile | Upload location for API profile or table definitions. |
Additional connection properties
Additional connection string properties not specified in the Connection Properties panel. For each property added, you can choose Visible or Encrypted. Selecting Encrypted hides the value from the interface and stores it encrypted in the back end, such as when defining passwords. Typical properties depend on the authentication type used.
| Property | Value |
|---|---|
Other | Name-value pair for extra API provider options. Common examples:
|
ProfileSettings | Semicolon-separated list of settings required by the data source. Used with HTTP (Basic) authentication. Example: ProfileSettings='User=EmailId;Password=key';'Other=Domain=YourDomain'. |
CallbackURL | Redirect URL for OAuth2 authentication. This must match the callback URL specified in app settings. Example: https://.../OAuthCallback/CallbackUrl/... |
OAuthClientId | Identifier assigned by the OAuth2 authorization server. Example: `OAuthClientId=Unique Identifier key. |
OAuthClientSecret | Secret value assigned by the OAuth2 authorization server. Example: OAuthClientSecret=password |
Scope | Action or permission scope for the application with OAuth2 authentication. Example: Forms=Read |
Advanced settings
Advanced settings control how the Custom API connector tracks changes, handles regional and time configuration, and processes data batches during extraction. These options allow fine‑tuning for performance and accuracy, and should be configured according to your system environment and operational requirements.
| Setting | Description |
|---|---|
| Tracking Type | Method for tracking changes: None or Date. |
| Region | Region setting for the connector, if required by your setup. |
| Time Zone | Time zone matching the Custom API application server. This must be identical to the profile time zone in Custom API to avoid data mismatches. |
| Time Offset | Refresh offset in seconds to compensate for timing issues in record selection. Minimum value is 0; maximum is 3600 seconds. |
| Batch Size | Quantity of records processed in each batch during extraction. Larger batch sizes increase memory usage but can improve performance up to a point. The default value is 2000 and the maximum should not exceed 10000 records. Adjust according to your network speed and disk performance; in most cases the default (2000) works best. |