Skip to main content

Select matches and deduct credit

POST 

/search/:searchId/select

A guest has zero account credits: at paymentStage=selection, payment is required and selection is not persisted; at paymentStage=results, selection uses the existing unpaid masked-results path. Guest access requires current session ownership; no guest wallet or paid marker is created.

Selects matches. After selection, matches cannot be changed and only the results endpoint is available.

Whether this call spends a credit depends on the user's paymentStage (see User.paymentStage on GET /users/me):

  • selection (or absent): one credit is deducted here. With no credits available the call returns 402 and the selection is rolled back, so it can be retried after buying credits.
  • results: nothing is charged here; the credit is charged by GET /search/{searchId}/results.

Important: This operation can only be performed once per search. If matches are already selected, returns 400 error.

Request​

Responses​

Matches selected (and a credit deducted when paymentStage is selection)