Listing manifest reference¶

Creating Snowflake listings programmatically requires a manifest, written in YAML (https://yaml.org/spec/ (https://yaml.org/spec/)). Use the information provided here to learn about the manifest format and its individual sections.

See also:: CREATE LISTING, ALTER LISTING, DESCRIBE LISTING, SHOW LISTINGS, DROP LISTING

Note

Fields can be any of:

Optional - Optional for either marketplace listings or private listings.
Required - Required for either marketplace listings or private listings.
Qualified - requirements differ for marketplace listings or private listings and optional vs required is qualified by listing type. For example optional for private listings, but required for marketplace listings.

The general format of a listing manifest is:

#
# Listing prefix
#
title: <listing title>
subtitle: <Optional listing subtitle>
description: <listing description>
profile : <Optional name of the provider profile>

listing_terms:
  - # Required listing terms that the consumer must sign.
targets:
  - # Required <List> Consumer accounts to target with this private listing.
auto_fulfillment:
  - # Required when the target accounts are outside the provider's region, otherwise optional.
business_needs:
  - # Optional <List> BusinessNeed elements; maximum 6.
categories:
  - # Optional <List> The category or area the listing belongs to, maximum 1.
compliance_badges:
  - # Optional <List> Compliance badges; maximum 3.
data_attributes:
  - # Optional <Name Value pairs> DataAttributes elements; maximum 1.
data_dictionary:
  - # Required for public listings and optional for all other listing types.
data_preview:
  - # Required for public listings and optional for all other listing types.
draft_access_type:
  - # Required <String> for "by request" listings.
locations:
  - # Optional list of regions to share into.
monetization_display_order:
  - # Optional <List> MonetizationDisplayOrder elements.
offers:
  - # Optional <List> Offer elements; maximum 100.
pricing_plans:
  - # Optional <List> PricingPlan elements; maximum 100.
resources:
  - # Optional for private listings; required for marketplace listings, <Name Value pairs> Resources elements such as documentation and media.
trial_details:
  - # Optional <Name Value pairs> Provides details about a trial listing.
usage_examples:
  - # Optional <List> UsageExample elements; maximum 10.

Copy

The following sections detail each listing manifest field and child field and provide associated examples.

Listing prefix¶

Each listing manifest starts with the following fields:

title (String, required, maximum length 110): Listing title.
subtitle (String, optional for private, required for marketplace listings, maximum length 110): Listing subtitle.
description (String, required, maximum length 7500): Listing description. Markdown syntax is supported.
custom_contact (String, optional): Email. Must be a valid, well formed email address.
profile (String, optional for private listings, required for marketplace listings): Name of an approved provider profile.

For more information, refer to: Provider basic information.

Note

Values for profile can be found by executing show profiles in data exchange SNOWFLAKE_DATA_MARKETPLACE;.

Listing prefix example¶

title: Weather information
subtitle: Historical weather by postcode.
description: This listing includes historical weather data by post code.
profile: My provider profile

Copy

`listing_terms`¶

The required listing_terms (required) field contains the following name value pairs:

listing_terms.type (enum, required): must be one of:
- STANDARD - Refers to the Standard Agreement for Marketplace Products.
- OFFLINE - Indicates that terms are negotiated offline by the parties.
- CUSTOM - When specified, must specify a value for listing_terms.link.
listing_terms.link (required when type is CUSTOM): A fully qualified link to the provider’s listing terms, must start with http or https.

For more information, refer to Terms of Service in the table in Basic information.

Note

Consumers can accept listing terms programmatically. For more information contact Snowflake Support.

`listing_terms` example¶

. . .
listing_terms:
  type: "CUSTOM"
  link: "http://example.com/my/listing/terms"
. . .

Copy

`targets`¶

Note

This field can only be used with V1 listings.

The targets field is required for marketplace and private listings.

Contains a list, maximum of 100 elements:

targets.accounts (Required if targets.region not present): List of accounts with which to share the listing.

Each target account must be in <OrgName>.<AccountName> format, where:
- OrgName can be obtained using SELECT CURRENT_ORGANIZATION_NAME();.
- AccountName can be obtained from account_name using SHOW ACCOUNTS or using Snowsight.

targets.regions (Required if targets.accounts not present):

List of regions with which to share the listing.

Each target region must be of the form “region_groups_type.snowflake_region”. In addition, “ALL” is supported for including all regions.

For example “PUBLIC.AWS_US_EAST_1”.

For a complete list of region group types and Snowflake regions execute:
```
SHOW REGIONS IN DATA EXCHANGE SNOWFLAKE_DATA_MARKETPLACE;
```
Copy

For more information, see Business needs.

`targets` examples¶

Define a set of target accounts for this listing.

. . .
targets:
   accounts: ["Org1.Account1", "Org2.Account2"]
. . .

Copy

Define a set of target regions for this listing.

. . .
targets:
   regions: ["PUBLIC.AWS_US_EAST_1", "PUBLIC.AZURE_WESTUS2"]
. . .

Copy

`auto_fulfillment`¶

Cross-Cloud Auto-fulfillment allows the data product associated with a listing to be automatically fulfilled to other Snowflake regions. The auto_fulfillment field defines how that auto-fulfillment takes place.

For more information on Cross-Cloud Auto-fulfillment, see Auto-fulfillment for listings.

Auto-fulfillment is only required if you’re sharing data to multiple regions. Do not enable it if you are sharing to accounts in the same region.

If you share data across multiple regions, the auto_fulfillment is:

Required if your data product is an application package.
Required if your data product is shared through a private listing.
Recommended if your data product is shared through a public listing.

Contains the following name value pairs:

auto_fulfillment.refresh_schedule
- <num> MINUTE - Number of minutes. Minimum 10 minutes, maximum 8 days, or 11520 minutes.
  
  If refresh_type is specified as SUB_DATABASE_WITH_REFERENCE_USAGE, do not include this setting. The refresh schedule for application packages must be defined at the account level and cannot specified at the listing level.
  
  For more information see Set the account-level refresh interval.

USING CRON <expression> - Defines the data product auto-fulfillment refresh schedule.

The syntax for USING CRON and REPLICATION SCHEDULE are the same. See Parameters.
auto_fulfillment.refresh_type (required when using auto_fulfillment): Must be one of -
- SUB_DATABASE - database replication (object level) - recommended.
- SUB_DATABASE_WITH_REFERENCE_USAGE - application package.
- FULL_DATABASE - database replication (for the entire database)
auto_fulfillment.refresh_schedule_override (optional): Overrides the defined update refresh frequency for all listings that use the same database. When this value is FALSE, listing updates fail when multiple listings sharing the same database have different refresh frequencies.
- TRUE - enables the refresh frequency override.
- FALSE - (default) disables the refresh frequency override.

`auto_fulfillment.refresh_schedule` examples¶

The following example refreshes the data product associated with a listing every 10 minutes:

. . .
listing_terms: . . .
. . .
auto_fulfillment:
  refresh_schedule: 10 MINUTE
  refresh_type: SUB_DATABASE
. . .

Copy

The following example refreshes the data product associated with a listing on specific days and times in specific regions:

. . .
listing_terms: . . .
. . .
auto_fulfillment:
  refresh_schedule: USING CRON  0 17 * * MON-FRI Europe/London
  refresh_type: SUB_DATABASE
. . .

Copy

The following example enables the refresh frequency override for listings that share the same database but have different refresh frequencies:

. . .
listing_terms: . . .
. . .
auto_fulfillment:
  refresh_schedule: 10 MINUTE
  refresh_type: SUB_DATABASE
  refresh_schedule_override: TRUE
. . .

Copy

Snowflake Native App `auto_fulfillment` example¶

SUB_DATABASE_WITH_REFERENCE_USAGE can only be used with application packages and cannot be combined with auto_fulfillment.refresh_schedule.

. . .
listing_terms: . . .
. . .
auto_fulfillment:
  refresh_type: SUB_DATABASE_WITH_REFERENCE_USAGE
. . .

Copy

Object level `auto_fulfillment` example¶

. . .
listing_terms: . . .
. . .
auto_fulfillment:
  refresh_type: SUB_DATABASE
. . .

Copy

`business_needs`¶

Listings are grouped by business needs for easy discovery. Business need is a describes how a specific listing meets a given business need. For more information, see Business needs.

STANDARD business needs¶

business_needs.name (required when using business_needs):

Valid values include:
- “360-Degree Customer View”
- “Supply Chain”
- “Personalize Customer Experiences”
- “Inventory Management”
- “Accelerating Advertising Revenue”
- “Attribution Analysis”
- “Contact Data Enrichment”
- “Foot Traffic Analytics”
- “Audience Segmentation”
- “Sentiment Analysis”
- “ESG Investment Analysis”
- “Fundamental Analysis”
- “Quantitative Analysis”
- “Risk Analysis”
- “Fraud Remediation”
- “Customer Onboarding”
- “Identity Resolution”
- “Asset Valuation”
- “Economic Impact Analysis”
- “Demand Forecasting”
- “Population Health Management”
- “Real World Data (RWD)”
- “Location Planning”
- “Regulatory Reporting”
- “Subscriber Acquisition and Retention”
- “Life Sciences Commercialization”
- “Patient 360”
- “Blockchain Analysis”
- “Customer Acquisition”
- “Data Quality and Cleansing”
- “Location Data Enrichment”
- “Location Geocoding”
- “Machine Learning”
- “Market Analysis”
- “Pricing Analysis”
- “Audience Activation”

business_needs[].description (required when using business_needs): Description of associated business_needs.name, maximum length 1000.

business_needs[].type: STANDARD (optional).

CUSTOM business needs¶

Custom business needs include a user defined name, description, and required type field with value CUSTOM.

business_needs.name (required when using business_needs): User defined name.

business_needs[].description (required when using business_needs): Description of associated business_needs.name, maximum length 1000.

business_needs[].type: CUSTOM (required when defining custom business needs).

`business_needs` examples¶

Standard without optional type

. . .
business_needs:
 - name: "Real World Data (RWD)"
   description: "Global weather data"
. . .

Copy

Standard with optional type

. . .
business_needs:
 - name: "Real World Data (RWD)"
   description: "Global weather data"
   type: STANDARD
. . .

Copy

Custom with required type

. . .
business_needs:
 - name: "Machinery Maintenance"
   description: "Repair and maintenance data for machinery"
   type: CUSTOM
. . .

Copy

`categories`¶

The categories field specifies the category or area the listing belongs to. Categories are optional for private listings but required for marketplace listings.

Categories are used in Snowflake Marketplace to browse listings by area and help consumers find your data.

The categories field is a list, but can only contain a single entry, from the set below:

BUSINESS
CONNECTORS
DEMOGRAPHICS
ECONOMY
ENERGY
ENVIRONMENT
FINANCIAL
GOVERNMENT
HEALTH
IDENTITY
LEGAL
LOCAL
LOOKUP_TABLES
MARKETING
MEDIA
SECURITY
SPORTS
TRANSPORTATION
TRAVEL
WEATHER

`categories` example¶

. . .
categories:
 - ECONOMY
. . .

Copy

`compliance_badges`¶

The compliances_badges field is used to indicate that a listing was reviewed by a third-party auditor and was certified as compliant with a specific standard or regulation.

When you configure a compliance badge, you can specify up to three types. Include the expiration date for each badge and the accompanying third-party certification documentation.

The following fields are used to configure a compliance badge:

compliance_badges: Used to declare and configure a compliance badge for a listing. Providers can declare multiple compliance certifications within the compliance_badges property.
- type: The compliance certification being requested. The following list shows the possible values:
  - SOC2
  - HIPAA
  - ISO27001
- expiry: The date when the compliance certification expires.
- files: The list of files that are used to verify the compliance certification.

For more information, see Listing compliance badges.

`compliance_badges` example¶

. . .
compliance_badges:
  - type: SOC2
    expiry: 12-25-2026
    files:
      - soc2_compliance_verification.pdf
  - type: HIPAA
    expiry: 06-07-2026
    files:
      - hipaa_compliance_verification.pdf
. . .

Copy

`data_attributes`¶

Data attributes provide consumers insight into information about the listing such as refresh rate and other characteristics.

The data_attributes field is optional for private listings but required for marketplace listings.

For additional information on data product attributes, see Data product - attributes.

Contains the following name value pairs:

data_attributes.refresh_rate (required for data listings; optional for app listings)

Specifies how often your data product is updated in Snowflake.

One of:
- CONTINUOUSLY
- HOURLY
- DAILY
- WEEKLY
- MONTHLY
- QUARTERLY
- ANNUALLY
- STATIC
data_attributes.geography (required), containing:

Specifies the geographic regions for which your data product has coverage.
- granularity (string, required)
  
  Geographic coverage of your dataset.
  
  One of:
  - LATITUDE_LONGITUDE
  - ADDRESS
  - POSTAL_CODE
  - CITY
  - COUNTY
  - STATE
  - COUNTRY
  - REGION_CONTINENT
- geo_option (string, required)
  
  One of:
  - NOT_APPLICABLE
  - GLOBAL
  - COUNTRIES
- coverage (required based on selection of geo_option), containing either :
  - states (list of states) containing any list of valid U.S. state names.
  Or
  - continents (list of continents):
    
    Any of:
    
    ASIA
    
    EUROPE
    
    AFRICA
    
    NORTH AMERICA
    
    SOUTH AMERICA
    
    OCEANIA
    
    ANTARCTICA
- time (required) containing:
  
  Specifies the time period that your data product covers.
  - granularity (required)
  One of:
  - EVENT_BASED
  - HOURLY
  - DAILY
  - WEEKLY
  - MONTHLY
  - YEARLY
  - time_range (required) containing the following name/value pairs:
    
    time_frame (required)
    
    One of:
    
    NEXT
    
    LAST
    
    BETWEEN
    
    unit (required)
    
    One of:
    
    DAYS
    
    WEEKS
    
    MONTHS
    
    YEARS
    
    value (required when time_frame is NEXT/LAST, integer), range 1-100.
    
    start_time (required when time_frame is BETWEEN, String date), format MM-DD-YYYY.
    
    end_time (required when time_frame is BETWEEN, String date), format MM-DD-YYYY.

`data_attributes` example¶

. . .
data_attributes:
  refresh_rate: DAILY
  geography:
    granularity:
      - REGION_CONTINENT
    geo_option: COUNTRIES
    coverage:
      continents:
        ASIA:
          - INDIA
          - CHINA
        NORTH AMERICA:
          - UNITED STATES
          - CANADA
        EUROPE:
          - UNITED KINGDOM
    time:
      granularity: MONTHLY
      time_range:
        time_frame: LAST
        unit: MONTHS
        value: 6

Copy

`data_dictionary`¶

The data_dictionary field provides consumers insight into the contents and structure of a listing before they install it into their account. Required for public listings, optional for all other listing types.

The data_dictionary field contains a list of up to five data dictionary entries:

data_dictionary.featured (required when using data_dictionary): must be ‘featured’.
data_dictionary.featured.database (required when using data_dictionary): database name.
data_dictionary.featured.objects (required when using data_dictionary): list of name value pairs -
- name (string, required): object name
- schema (string, required): schema
- domain (required):
  
  One of:
  - DATABASE
  - SCHEMA
  - TABLE
  - VIEW
  - EXTERNAL_TABLE
  - MATERIALIZED_VIEW
  - DIRECTORY_TABLE
  - FUNCTION
  - COLUMN

`data_dictionary` example¶

. . .
data_dictionary:
 featured:
    database: "WEATHERDATA"
    objects:
       - name: "GLOBAL_WEATHER"
         schema: "PUBLIC"
         domain: "TABLE"
       - name: "GLOBAL_WEATHER_REPORT"
         schema: "PUBLIC"
         domain: "TABLE"
. . .

Copy

`data_preview`¶

The data_preview field allows providers to identify and hide Personally identifiable information (PII) in the data preview samples generated from listing data. PII data is data that could directly or indirectly reveal an individual’s identity. Required for public listings, and optional for all other listing types.

The data_preview field includes the following entries:

data_preview.has_pii (required when using data_preview): indicates whether PII is included in the listing data.
- TRUE - PII is included in the listing data.
- FALSE - PII is not included in the listing data.
data_preview.metadata_overrides (recommended when data_preview.has_pii is TRUE ): identifies the location of the PII listing data and the objects within that dataset containing PII to hide or expose.
- database (string, required): Database name.
- objects (list, required): The objects to hide or expose columns from in the data preview samples:
  - schema (string, required): Schema name.
  - domain (string, required): Domain name.
  - name (string, required): Object name
  - pii_columns (list, optional): The columns containing PII.
  - overridden_pii_columns (list, optional): The columns Snowflake classification identified as containing PII, but should be available in the data preview samples shared with consumers.
    
    Periodically, Snowflake runs classifications on generated data previews. Any columns containing PII are defined in classified_pii_columns when SHOW commands are run.
    
    Columns identified by Snowflake as containing PII are hidden from consumers of the listing only in the data preview samples. If a provider of a listing determines the columns are erroneously identified as containing PII, they can specify the specific columns they want included in the data preview samples using overridden_pii_columns.

`data_preview` example¶

. . .
data_preview:
 has_pii: TRUE
 metadata_overrides:
    database: WEATHERDATA
    objects:
       - schema: PUBLIC
         domain: TABLE
         name: GLOBAL_WEATHER
         pii_columns: [ADDRESS, PHONE]
         overridden_pii_columns: [FIRST_NAME, LAST_NAME]
. . .

Copy

`draft_access_type`¶

Specifies how access to a draft listing is controlled.

Note

For “by request” listings, you must set draft_access_type: "BY_REQUEST" in the manifest.

This field determines the access model for the listing while it’s in draft status. This is especially relevant for compliance badging, as providers await approval of a listing’s badge or badges by the Snowflake compliance team.

The allowed values for draft_access_type are:

UNKNOWN
FREE
PAID
LIMITED_TRIAL
BY_REQUEST

`draft_access_type` examples¶

. . .
draft_access_type: "BY_REQUEST"
. . .

Copy

`external_targets`¶

The external_targets field is used to share public or private V2 listings.

Note

This field can only be used with V2 listings.

The access field is required when external_targets is specified, and it must include one of the following sub-fields:

organization: When creating a private listing, specify the organization name and accounts that can access the listing.
account: When creating a private listing, optionally specify the roles within an account that can access the listing.
all_organizations: When creating a public listing, set this to true.

`external_targets` examples¶

The follow example shows how to use external_targets to share private listings.

. . .
external_targets:
  access:
    - organization: OrgName2
      accounts: [acc1, acc2]
    - account: acc2
      roles: [role1, role2]
. . .

Copy

The follow example shows how to use external_targets to share public listings.

. . .
external_targets:
  access:
    - all_organizations: true
. . .

Copy

`locations`¶

Specifies the optional locations that can discover or access the listing.

Note

This field can only be used with V2 listings.

The access_regions field is required when locations is specified, and it must include one of the following sub-fields:

ALL: All regions can discover or access the listing.
name: An array of regions of the form “region_groups_type.snowflake_region” that can discover or access the listing; for example, access_regions: - name: PUBLIC.AWS_US_WEST_2.

Available region groupings for VPS deployments include the following:

AWS_US_EAST_1 (“US East (N. Virginia)”)
AWS_US_EAST_2 (“US East (Ohio)”)
AWS_US_WEST_2 (“US West (Oregon)”)
AWS_EU_WEST_1 (“EU (Ireland)”)
AWS_EU_WEST_2 (“EU (London)”)
AZURE_EASTUS2 (“East US 2 (Virginia)”)
AZURE_CENTRALUS (“Central US (Iowa)”)

`locations` example¶

. . .
locations:
  access_regions:
    - name: "PUBLIC.AWS_US_WEST_2"
. . .

Copy

For a complete list of regions, see SHOW REGIONS.

`monetization_display_order`¶

The optional monetization_display_order field specifies the order in which pricing plans are displayed to consumers in Snowflake Marketplace.

Note

This field can only be used with V2 listings.

`monetization_display_order` example¶

. . .
monetization_display_order:
  - offer_id_1
  - offer_id_2
  - offer_id_3
. . .

Copy

`offers`¶

Note

This field can only be used with V2 listings.

The optional offers field includes a list of up to eight offers that are associated with the listing. The offers field includes the following name value pairs:

name (String, required ): The user-defined name of the offer. The name must be formatted as all uppercase.
type (String, required): Must be one of the following types:
- FILE: Indicates that the offer is defined in a local YAML file.
- URL: Indicates that the offer is defined in a remote URL.
path (String, required): The path to the local or remote offers YAML.

`offers` example¶

. . .
offers:
  - name: PRICING_PLAN_1_DEFAULT_OFFER
    type: FILE
    path: offers/PRICING_PLAN_1_DEFAULT_OFFER.yaml
. . .

Copy

`pricing_plans`¶

Note

This field can only be used with V2 listings.

The optional pricing_plans field includes a list of pricing plans that are associated with the listing. The pricing_plans field includes the following name value pairs:

name (String, required): The user-defined name of the pricing plan. The name must be formatted as all uppercase.
type (String, required): Must be one of the following types:
- FILE: Indicates that the offer is defined in a local YAML file.
- URL: Indicates that the offer is defined in a remote URL.
path (String, required): The path to the local or remote pricing plan YAML.

`pricing_plans` example¶

. . .
pricing_plans:
  - name: PRICING_PLAN_1
    type: FILE
    path: pricingPlans/PRICING_PLAN_1.yaml
. . .

Copy

`resources`¶

Resources contain information about the listing, including links to documentation and a video.

The resources field is optional for private listing but required for marketplace listings.

Contains the following name value pairs:

resources.documentation (String, required ): A fully qualified link to a page on your website with more detailed documentation for the listing. Must start with http or https.
resources.media (String, optional): A fully qualified link to an unlisted or public YouTube video for the listing.

For more information see Details.

`resources` example¶

. . .
resources:
  documentation: https://www.example.com/documentation/
  media: https://www.youtube.com/watch?v=MEFlT3dc3uc
. . .

Copy

`trial_details`¶

The optional trial_details field captures trial details associated with the listing and includes the following name value pairs:

trial_type (String, required ): Specifies the type of the trial. Must be one of the following types:
- TIME
- USAGE
- LIMITED
- LIMITED_TIME
trial_time_limit (Integer, optional): Specifies the number of days that the listing will be allowed as a trial, after which the consumer would need to request the full product. A null value indicates that the listing is an unlimited time trial. Either trial_time_limit or trial_usage_limit must be specified.
trial_usage_limit (Integer, optional): Specifies the number of allowed free uses with this listing, after which the consumer would need to upgrade. Either trial_time_limit or trial_usage_limit must be specified.
trial_usage_unit (Long, optional): Specifies the unit (such as queries or rows) for the trial usage. Depending on this usage unit, the usage count is incremented accordingly. This field can only be used with trial-usage_limit.
description (String, optional): A string describing the trial details. The maximum length is 4,096 characters.

`trial_details` example¶

. . .
trial_details:
  trial_type: TIME
  trial_time_limit: 30
  description: "This is a 30-day free trial"
. . .

Copy

`usage_examples`¶

The usage_examples field is optional for private listings but required for marketplace listings.

Contains a list of the following name value pairs:

usage.title (String, required): Usage example title; maximum length 110 characters.
usage.description (String, optional): Associated description; maximum length 300 characters.
usage.query (String, required): Query associated with the usage example; maximum length 30,000 characters.

For more information, see Sample SQL queries.

`usage_examples` example¶

. . .
usage_examples:
  - title: "Return all weather for the US"
    description: "Example of how to select weather information for the United States"
    query: "select * from weather where country_code='USA'";
. . .

Copy

Listing manifest reference¶

Listing prefix¶

Listing prefix example¶

listing_terms¶

listing_terms example¶

targets¶

targets examples¶

auto_fulfillment¶

auto_fulfillment.refresh_schedule examples¶

Snowflake Native App auto_fulfillment example¶

Object level auto_fulfillment example¶

business_needs¶

STANDARD business needs¶

CUSTOM business needs¶

business_needs examples¶

categories¶

categories example¶

compliance_badges¶

compliance_badges example¶

data_attributes¶

data_attributes example¶

data_dictionary¶

data_dictionary example¶

data_preview¶

data_preview example¶

draft_access_type¶

draft_access_type examples¶

external_targets¶

external_targets examples¶

locations¶

locations example¶

monetization_display_order¶

monetization_display_order example¶

offers¶

offers example¶

pricing_plans¶

pricing_plans example¶

resources¶

resources example¶

trial_details¶

trial_details example¶

usage_examples¶

usage_examples example¶

Complete YAML example for a V1 data share listing¶

Complete YAML example for a V2 data share listing¶

`listing_terms`¶

`listing_terms` example¶

`targets`¶

`targets` examples¶

`auto_fulfillment`¶

`auto_fulfillment.refresh_schedule` examples¶

Snowflake Native App `auto_fulfillment` example¶

Object level `auto_fulfillment` example¶

`business_needs`¶

`business_needs` examples¶

`categories`¶

`categories` example¶

`compliance_badges`¶

`compliance_badges` example¶

`data_attributes`¶

`data_attributes` example¶

`data_dictionary`¶

`data_dictionary` example¶

`data_preview`¶

`data_preview` example¶

`draft_access_type`¶

`draft_access_type` examples¶

`external_targets`¶

`external_targets` examples¶

`locations`¶

`locations` example¶

`monetization_display_order`¶

`monetization_display_order` example¶

`offers`¶

`offers` example¶

`pricing_plans`¶

`pricing_plans` example¶

`resources`¶

`resources` example¶

`trial_details`¶

`trial_details` example¶

`usage_examples`¶

`usage_examples` example¶