---
title: "Direct Screen To Pipeline"
method: POST
path: "/v2/pipeline/direct"
tags: ["discovery-v2"]
---

# Direct Screen To Pipeline

`POST /v2/pipeline/direct`

Screen one prepared parcel against a saved buy box, whether or not it is eligible.

``POST /v2/pipeline`` answers "add this ranked lead" and correctly refuses a parcel that
fails a must-have. This route answers the other half of the product requirement — "screen
this specific site" — and refuses nothing that exists in the market: a failing parcel is
saved with verdict HOLD and its real failed evidence, so the customer gets an answer
instead of a dead end.

Everything else is identical to a discovery promotion, deliberately: same entitlement and
vintage checks, same canonical spec identity, same single transaction, same idempotency,
and the same hard boundary — no provider call, no contact, no cost-ledger row. The saved
row never enters discovery results; discovery reads parcel facts, not promoted matches.

## Headers

- `authorization` string, nullable
- `X-Tenant` string, nullable

## Request body

- DirectPromoteRequest — Screen one specific prepared parcel against a SAVED buy box. No draft and no query hash: this is not "add row N of a result set", it is "screen this site", so the saved spec is the only sensible yardstick and the server derives the query identity itself. ``vintage_id`` is the vintage the caller resolved the parcel against. It is optional for older clients but strongly recommended: without it, an operator promoting a new vintage between resolve and screen would silently screen different facts than the user saw.
  - `parcel_key` string, required
  - `buy_box` string, required
  - `vintage_id` string, uuid, nullable

## Response `202`

Successful Response

- PromoteResponse
  - `property_id` string, uuid, required
  - `pipeline_item_id` string, uuid, required
  - `buy_box_match_id` string, uuid, required
  - `diligence_job_id` string, uuid, required
  - `status` string, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/mireye/apis/mireye-scout-api.md) · [All operations](https://skmtc.net/mireye/apis/mireye-scout-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mireye/mireye-scout-api/revisions/c80d2b343f16/schema)
