@adcp/sdk API Reference - v14.0.0-beta.6
    Preparing search index...

    Function legacyPerformanceFeedbackResponse

    • Parameters

      • data: {
            success: true;
            feedback_id?: string;
            application_status?: "accepted" | "applied" | "not_applied";
            status_reason?: string;
            received_at?: string;
            applied_at?: string;
            sandbox?: boolean;
            context?: Omit<Omit<{}, "bank">, "authentication"> & {
                authentication?: unknown;
            };
            ext?: Omit<Omit<{ [key: string]: unknown }, "bank">, "authentication"> & {
                authentication?: unknown;
            };
        }
        • success: true

          Whether the performance feedback was successfully received

        • Optionalfeedback_id?: string

          Receiver-issued identifier for this immutable assertion. Orchestrator gateways and sellers declaring media_buy.performance_feedback MUST return it; legacy sellers may omit it. The identifier is local to the receiving hop. Use it in supersedes_feedback_id when revising that hop's assertion.

          1

        • Optionalapplication_status?: "accepted" | "applied" | "not_applied"

          Optimizer disposition at response time, distinct from the protocol envelope's task status. accepted means stored and eligible for evaluation, not that optimizer use is guaranteed. applied means incorporated into the seller's optimization inputs. not_applied means evaluated but not incorporated. Sellers declaring reports_application_status MUST return this field.

        • Optionalstatus_reason?: string

          Human-readable explanation when application_status is not_applied. May also explain material qualifications on accepted feedback.

          500

        • Optionalreceived_at?: string

          When the receiving orchestrator gateway or seller stored the assertion.

          date-time

        • Optionalapplied_at?: string

          When the seller incorporated the assertion into its optimization inputs. Present only when application_status is applied.

          date-time

        • Optionalsandbox?: boolean

          When true, this response contains simulated data from sandbox mode.

        • Optionalcontext?: Omit<Omit<{}, "bank">, "authentication"> & { authentication?: unknown }
        • Optionalext?: Omit<Omit<{ [key: string]: unknown }, "bank">, "authentication"> & {
              authentication?: unknown;
          }
      • Optionalsummary: string

      Returns McpToolResponse

      v6: createAdcpServerFromPlatform constructs wire responses from typed platform returns. Direct use is for v5 raw-handler adopters mid-migration only.