/govdeals/events

POST /api/govdeals/events

Price: 1 credit

Get one GovDeals sale event by id or URL: title, description, open and close time, next and last lot close time, open lot count, banner, and its featured lots with current bid, photo and end time.

How to use it

Read one GovDeals sale event and its featured lots. For every lot of the event pass its id as event_id to govdeals/lots/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• event string required — GovDeals event id or event URL (examples: "31038", "https://www.govdeals.com/en/events/31038"; minLength: 1)

Response

• @type string (default: "GovdealsEventDetail")
• id string required
• display_id string nullable
• url string required
• description string nullable
• start_at integer nullable
• end_at integer nullable
• next_lot_end_at integer nullable
• open_lot_count integer nullable
• is_closed boolean nullable
• is_partner_event boolean nullable
• partner_event_url string nullable
• banner string nullable
• last_lot_end_at integer nullable
• has_lots boolean nullable
• region_id string nullable
• category_tier_id string nullable
• auction_type_id string nullable
• featured_lots array (default: [])
  • @type string (default: "GovdealsLotCard")
  • id string required
  • asset_id string required
  • seller_id string required
  • url string required
  • make string nullable
  • model string nullable
  • model_year integer nullable
  • category_code string nullable
  • category_name string nullable
  • seller_name string nullable
  • city string nullable
  • state string nullable
  • state_name string nullable
  • zip_code string nullable
  • country string nullable
  • current_bid number nullable
  • buy_now_price number nullable
  • bid_count integer nullable
  • bid_increment number nullable
  • currency string nullable
  • has_reserve boolean nullable
  • is_reserve_met boolean nullable
  • is_reserve_reduced boolean nullable
  • is_sold boolean nullable
  • start_at integer nullable
  • end_at integer nullable
  • event_id string nullable
  • lot_number integer nullable
  • auction_type_id string nullable
  • image string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No GovDeals event with this id Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.