API reference navigation
POST /v1/search/steering

Record a steering verdict

Access
Authenticated
search:read
Cost
Free
Rate limit
60 / minute per account
Quota
None

Leave a thumbs up/down on a developer within a saved search. Steering is per-search: a repeat verdict on the same developer replaces the prior one. Free to record; a re-execute that applies it is priced as the search it re-runs.

Request body SubmitSteeringRequest

  • savedSearchId string required

    The saved search this verdict belongs to.

    max 16 chars
  • developerId string required

    The developer being judged.

    max 64 chars
  • verdict string required

    Thumbs up or thumbs down. Submitting again for the same developer replaces the earlier verdict.

    updown
  • reason string | null

    Optional free-text reason. Stored with the note and shown back on the steering list.

    max 500 chars

Responses

  • 200 The recorded steering note
    • id string required

      Identifier of this steering note.

    • savedSearchId string required

      The saved search this verdict applies to. Steering is per saved search, never global.

    • developerId string required

      The developer the verdict is about.

    • verdict string required

      Thumbs up or thumbs down on this developer for this saved search.

      updown
    • reason string | null required

      The free-text reason given, when one was. Null otherwise.

    • createdAt string required

      When the verdict was recorded, as an ISO 8601 instant.

  • 401 No or invalid credential
    • code string required

      Stable machine-readable error code. Branch on this, never on the numeric status.

      bad_requestunauthorizedsignature_requiredpayment_requiredforbiddennot_foundconflictgonepayload_too_largeunprocessable_entitytoo_many_requestsinternal_errornot_implementedbilling_unavailablenot_contactablemailbox_link_unavailablemailbox_requiredmail_engine_unavailablewebhook_publisher_unavailabledatabase_unavailableclient_error
    • message string required

      Human-readable explanation of the refusal.

    • status integer required

      The HTTP status code, repeated in the body.

    • remedy object

      A self-serve path forward, when one exists (a 402 points at the credit top-up).

      • kind string required

        What kind of remedy this is, so a client can route it: whether the caller can clear the condition through the API, or a person must act in the web app.

        topupconnect_mailbox
      • url string required

        Where to go to clear the condition: an API path, or a web app page when only a person can.

  • 403 Missing search:read
    • code string required

      Stable machine-readable error code. Branch on this, never on the numeric status.

      bad_requestunauthorizedsignature_requiredpayment_requiredforbiddennot_foundconflictgonepayload_too_largeunprocessable_entitytoo_many_requestsinternal_errornot_implementedbilling_unavailablenot_contactablemailbox_link_unavailablemailbox_requiredmail_engine_unavailablewebhook_publisher_unavailabledatabase_unavailableclient_error
    • message string required

      Human-readable explanation of the refusal.

    • status integer required

      The HTTP status code, repeated in the body.

    • remedy object

      A self-serve path forward, when one exists (a 402 points at the credit top-up).

      • kind string required

        What kind of remedy this is, so a client can route it: whether the caller can clear the condition through the API, or a person must act in the web app.

        topupconnect_mailbox
      • url string required

        Where to go to clear the condition: an API path, or a web app page when only a person can.

  • 404 No such saved search in this account
    • code string required

      Stable machine-readable error code. Branch on this, never on the numeric status.

      bad_requestunauthorizedsignature_requiredpayment_requiredforbiddennot_foundconflictgonepayload_too_largeunprocessable_entitytoo_many_requestsinternal_errornot_implementedbilling_unavailablenot_contactablemailbox_link_unavailablemailbox_requiredmail_engine_unavailablewebhook_publisher_unavailabledatabase_unavailableclient_error
    • message string required

      Human-readable explanation of the refusal.

    • status integer required

      The HTTP status code, repeated in the body.

    • remedy object

      A self-serve path forward, when one exists (a 402 points at the credit top-up).

      • kind string required

        What kind of remedy this is, so a client can route it: whether the caller can clear the condition through the API, or a person must act in the web app.

        topupconnect_mailbox
      • url string required

        Where to go to clear the condition: an API path, or a web app page when only a person can.