Sending

Get (or wait for) the reply to a sent email

Changed on

Returns the first threaded inbound reply to a send, keyed by the inbound email's reply_to_sent_email_id. This is the canonical "did a reply arrive for this send?" call: after /send-mail, poll (or long-poll) here instead of hand-rolling an /emails/search loop.

By default the call returns immediately with reply: null when nothing has arrived yet. Set wait=true to long-poll: the server holds the request up to wait_timeout_ms (default 10000, max 30000), returning as soon as the first reply lands. On a wait that elapses with no reply, the response has reply: null and timed_out: true.

The reply object is compact (headers plus bodies); fetch /emails/{id} with reply.id for the fully parsed record, or /threads/{thread_id} for the whole back-and-forth.

get/sent-emails/{id}/reply

Request

  • Base URL: https://api.primitive.dev/v1
  • URL: https://api.primitive.dev/v1/sent-emails/{id}/reply
  • Auth: HTTP bearer

Path parameters

idstring uuid required

Resource UUID

Query parameters

waitboolean

When true, long-poll up to wait_timeout_ms for the first reply to arrive instead of returning immediately. Mirrors send-mail's server-side wait semantics. The server accepts only the literal strings true / false (standard boolean query serialization); omitted means no wait.

wait_timeout_msinteger

Maximum time to hold the request when wait=true. Server default is 10000. NOT given an OpenAPI default on purpose, matching the /emails wait parameter: a default makes some generators send the value on every call.

Response

Reply status for the send (reply may be null)

successboolean required

Changes

    • info

      removed the invalid_signup_code enum value from the / response property for the response status

    • info

      removed the invalid_signup_code enum value from the / response property for the response status

    • info

      removed the invalid_signup_code enum value from the / response property for the response status

    • warning

      added the new not_a_repeating_send enum value to the / response property for the response status

    • warning

      added the new not_a_repeating_send enum value to the / response property for the response status

    • warning

      added the new not_a_repeating_send enum value to the / response property for the response status

    • warning

      added the new repeat_idle_requires_internal_recipient enum value to the / response property for the response status

    • warning

      added the new repeat_idle_requires_internal_recipient enum value to the / response property for the response status

    • warning

      added the new repeat_idle_requires_internal_recipient enum value to the / response property for the response status

    • warning

      added the new repeat_recipient_external enum value to the / response property for the response status

    • warning

      added the new repeat_recipient_external enum value to the / response property for the response status

    • warning

      added the new repeat_recipient_external enum value to the / response property for the response status

    • warning

      added the new repeat_stop_not_allowed enum value to the / response property for the response status

    • warning

      added the new repeat_stop_not_allowed enum value to the / response property for the response status

    • warning

      added the new repeat_stop_not_allowed enum value to the / response property for the response status

    • warning

      added the new repeat_unsupported enum value to the / response property for the response status

    • warning

      added the new repeat_unsupported enum value to the / response property for the response status

    • warning

      added the new repeat_unsupported enum value to the / response property for the response status