Singular Partner Config
Overview
The Singular Partner Config source connector extracts partner configuration data from Singular. This is useful for auditing configuration state over time and tracking updates made to partner settings.
Setup
Prerequisites
- Access to a Singular account with permission to read partner configuration data.
- Singular API credentials (see Authentication).
Authentication
Configure the connector using your Singular API credentials.
Typical requirements:
- API Key (or token)
- API Secret (if applicable)
Provide these values in the connector configuration. If your Singular workspace uses additional access controls (for example, IP allowlists), ensure your data platform can reach the Singular API.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
api_key | string | ✅ | Singular API key (or access token) used to authenticate requests. |
api_secret | string | ⛔️/✅ | Singular API secret, if required by your Singular authentication method. |
start_date | string | ⛔️ | Earliest date to begin extracting data (ISO 8601, e.g. 2024-01-01). If omitted, the connector uses the default behavior for the API/stream. |
end_date | string | ⛔️ | Optional end date (ISO 8601). If omitted, the connector extracts up to the most recent available data. |
If your workspace uses a single-token auth flow (API key only),
api_secretmay not be required.
Streams
partner_config_changes (new)
A change-log style stream that captures updates to partner configuration over time.
Use this stream to:
- Audit when partner configuration values changed
- Identify who/what initiated changes (when available from the API)
- Reconstruct configuration state transitions
Primary key
This stream is expected to include a stable identifier per change event (for example, a change/event id). The exact primary key fields depend on the Singular API response.
Incremental behavior
This stream is typically incremental based on a timestamp or change sequence (depending on what Singular exposes). If your connector configuration includes start_date / end_date, those bounds are applied to limit the extracted change history.
Notes and troubleshooting
- If you see authentication errors, confirm the API key/secret are valid and have access to the relevant Singular workspace.
- If the stream returns no records, verify the date range and confirm that partner configuration changes exist in the selected period.