Skip to main content

Organization Metadata

Collects detailed information about your organization, including access request settings, creation and update timestamps, group ID, organization name, and member roles.

Sync Type: Full Synchronisation

Requirements​

  • You can follow the steps outlined in Snyk's documentation to create a Snyk service account.
  • 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 cron field to run this input on specific intervals and returns all organizations, performing a full sync of data each time.

Configuration​

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

Settings​

SettingTypeRequiredDescription
CronstringYesCron string for scheduling tasks. Ex: '0 0 * * *' for daily execution at midnight.

Secrets​

SecretTypeRequiredDescription
API KeystringYesAPI Key for the Snyk API. This is required to authenticate requests.

Custom Schema Handling​

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

{
  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.

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. We're always looking to expand our coverage of security control frameworks based on community needs.

Sample Record​

{
  "id": "da8dd77e-1217-ddc9-0ab6-b0ba89c06aee",
  "type": "org",
  "attributes": {
    "is_personal": false,
    "name": "enterprise-org",
    "slug": "personal-org",
    "created_at": "2025-08-11T23:46:47Z",
    "updated_at": "2025-08-11T23:46:47Z"
  },
  "relationships": {
    "member_role": {
      "data": {
        "id": "994891d5-4c26-7b1d-017b-c865a9350e02",
        "type": "org_role"
      }
    }
  }
}