# Scan Targets

Fetches detailed information about specific entities within your organization that Snyk monitors for vulnerabilities. Collects data such as target IDs, creation dates, display names, and resource URLs

**Sync Type: Full Synchronisation**

## Requirements
- You can follow the steps outlined in Snyk's documentation to create a [Snyk service account](https://docs.snyk.io/enterprise-configuration/service-accounts).
- The role you will select depends on which Snyk level you are connecting at:
- If connecting at the Snyk group level, select the Group Admin role.
- If connecting at the Snyk organization level, select the Org Admin role.
- For the name of the account, we recommend Monad Service.
- Once you have successfully created the service account, be sure to copy the token that Snyk generates. Make sure to save this token to your secrets tool or password manager before you navigate away from the page, since it will not be displayed again.

## Details
Monad uses the `updated_after` filter on the [api](https://docs.snyk.io/snyk-api/reference/issues) to determine which issues to display. This field is updated every time a request to get issues is successful with the last time a request to get issues was initiated. If this was the first time requesting for issues, a full sync of the data is performed.

## Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.

#### Settings

| Setting | Type | Required | Description |
|---------|------|----------|-------------|
| Backfill Start Time | string | No | The date to start fetching data from. If not specified, no past records will be fetched. |
| API Rate Limit | object | No | Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See [API Rate Limiting](../../../guides/rate-limiting) for the field format, limits, and how to choose a value. |

#### Secrets

| Secret | Type | Required | Description |
|---------|------|----------|-------------|
| API Key | string | Yes | API Key for the Synk API. This is required to authenticate requests. |

## Custom Schema Handling

If the source data doesn't align with any of the [OpenSecurityControlFramework (OSCF) schemas](https://schema.ocsf.io/), you can create a custom transformation using our JQ transform pipeline. For example:

```jq
{
  metadata: {
    schema_version: "1.0.0",
    custom_framework: "my_framework"
  },
  controls: .[]
}
```

For more information on JQ and how to write your own JQ transformations see the JQ docs [here](https://jqlang.github.io/jq/).

If you believe this data source should be included in the standard OSCF schema set, please reach out to our team at [support@monad.com](mailto:support@monad.com). We're always looking to expand our coverage of security control frameworks based on community needs.


## Related Articles
- [https://docs.snyk.io/snyk-admin/structure-account-for-high-application-performance/service-accounts](https://docs.snyk.io/snyk-admin/structure-account-for-high-application-performance/service-accounts)
- [https://docs.snyk.io/snyk-api/reference/targets](https://docs.snyk.io/snyk-api/reference/targets)
## Sample Record

```json
{
  "attributes": {
    "created_at": "2025-08-11T23:46:47.084513Z",
    "display_name": "snyk-fixtures/goof",
    "is_private": false,
    "url": "http://github.com/snyk/local-foo"
  },
  "id": "49dcdcc1-fd80-174a-d0de-75f4c0b0e0c8",
  "relationships": {
    "integration": {
      "data": {
        "attributes": {
          "integration_type": "gitlab"
        },
        "id": "5a3e220e-6c4b-63cb-ecbb-9c3f8f0401e4",
        "type": "integration"
      }
    },
    "organization": {
      "data": {
        "id": "364d4557-40e8-bf91-52ba-7522deee34ca",
        "type": "organization"
      }
    }
  },
  "type": "target"
}
```