Linking Veracode as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Veracode connector syncs applications, sandboxes, findings, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Connect Veracode with an API service account's API ID and secret key, generated under Account settings → API credentials in the Veracode Platform. Requests are signed with Veracode's HMAC scheme.
The service account needs the Results API and Applications API roles to read the application portfolio and findings. Pick the region your Veracode account lives in - data is isolated per region.
You'll be asked for:
- API ID
- API secret key
- Region: choose between US commercial (api.veracode.com), European (api.veracode.eu) and US federal (api.veracode.us).
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Veracode tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API ID | password | Yes |
API secret key | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
applications | An application profile in the Veracode portfolio, including its policy-compliance state and scan history. | Incremental, Full refresh | modified | — |
sandboxes | A development sandbox belonging to an application, used to scan code before it is promoted to a policy scan. | Full refresh | — | — |
findings | Static, dynamic, and manual security findings for an application, with severity, CWE, and remediation status. | Full refresh | — | — |
sca_findings | Software Composition Analysis findings for an application: vulnerabilities in open-source and third-party components. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API ID is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.