@adcp/sdk API Reference - v10.0.1
    Preparing search index...

    Interface ValidateContentDeliveryRequest

    Request parameters for batch validating delivery records against content safety policies

    interface ValidateContentDeliveryRequest {
        adcp_version?: string;
        adcp_major_version?: number;
        standards_id: string;
        records: {
            record_id: string;
            media_buy_id?: string;
            timestamp?: string;
            artifact: Artifact;
            country?: string;
            channel?: string;
            brand_context?: { brand_id?: string; sku_id?: string };
        }[];
        feature_ids?: string[];
        include_passed?: boolean;
        context?: ContextObject;
        ext?: ExtensionObject;
    }
    Index

    Properties

    adcp_version? adcp_major_version? standards_id records feature_ids? include_passed? context? ext?

    Properties

    adcp_version?: string

    Release-precision AdCP version (VERSION.RELEASE, e.g. "3.0", "3.1", "3.1-beta"). On a request: the buyer's release pin — the seller validates against its supported_versions and returns VERSION_UNSUPPORTED on cross-major mismatch, or downshifts to the highest supported release within the same major. On a response: the release the seller actually served — clients SHOULD validate the response against that release's schema, not against their pin. Patches are not negotiated; surface them as build_version on capabilities for operational visibility. When omitted, falls back to adcp_major_version (deprecated) or server default. Buyers SHOULD emit both adcp_version and adcp_major_version through 3.x to remain compatible with sellers that only read the legacy field. NORMALIZATION: SDKs that read full-semver values from bundle metadata (e.g. ComplianceIndex.published_version = "3.1.0-beta.1") MUST normalize to release-precision ("3.1-beta.1") before emitting on the wire — meta-field values are NOT valid wire values.

    adcp_major_version?: number

    DEPRECATED in favor of adcp_version (release-precision string). Servers MUST continue to honor this field through 3.x. Removed in 4.0. Original semantics: the AdCP major version the buyer's payloads conform to. Sellers validate against their supported major_versions and return VERSION_UNSUPPORTED if unsupported. When omitted, the seller assumes its highest supported version.

    standards_id: string

    Standards configuration to validate against

    records: {
        record_id: string;
        media_buy_id?: string;
        timestamp?: string;
        artifact: Artifact;
        country?: string;
        channel?: string;
        brand_context?: { brand_id?: string; sku_id?: string };
    }[]

    Delivery records to validate (max 10,000)

    Type Declaration

    • record_id: string

      Unique identifier for this delivery record

    • Optionalmedia_buy_id?: string

      Media buy this record belongs to (when batching across multiple buys)

    • Optionaltimestamp?: string

      When the delivery occurred

      date-time

    • artifact: Artifact
    • Optionalcountry?: string

      ISO 3166-1 alpha-2 country code where delivery occurred

    • Optionalchannel?: string

      Channel type (e.g., display, video, audio, social)

    • Optionalbrand_context?: { brand_id?: string; sku_id?: string }

      Brand information for policy evaluation. Schema TBD - placeholder for brand identifiers.

      • Optionalbrand_id?: string

        Brand identifier

      • Optionalsku_id?: string

        Product/SKU identifier if applicable

    feature_ids?: string[]

    Specific features to evaluate (defaults to all)

    include_passed?: boolean

    Include passed records in results

    context?: ContextObject
    ext?: ExtensionObject

    Settings

    Member Visibility

    On This Page

    Properties