Account

Sign-in by email — step C: resume the paired executor

Called from the device logged in BY EMAIL, once per email sign-in. Verifies the Dynamic session JWT, finds this Dynamic user's pairing, requires the SAME email (by sha256) and the same executor wallet that consented, then binds this Supabase session to that executor.

The first time, the pairing is PENDING and nothing binds: 409 login_link_pending names the wallet (and executor) that consented. Show the FULL wallet_address and ask whether it is the person's own wallet — it is the one that gets paid for work done from this email. Yes: call again with accept_wallet = that address. No: unpair with DELETE /login-email.

The session is REDUCED: it may apply, submit and rate, but changing the wallet or the Solana payout address, deleting the account, pairing or unpairing by wallet, and approving or cancelling an H2A task answer 403.

post/api/v1/account/login-email/resume

Request

Base URL: https://api.execution.market
URL: https://api.execution.market/api/v1/account/login-email/resume
Auth: API key in header Signature-Input

Headers

authorizationstring nullable

Bearer <supabase_jwt>

Request body

dynamic_jwtstring required

The Dynamic session JWT of the EMAIL login. Its verified_credentials[] must hold exactly one credential with format == 'email'.

accept_walletstring nullable

Only while the pairing is PENDING (409 login_link_pending): the wallet_address that 409 showed, after the person confirmed it is THEIR wallet — the one that will be paid for work done from this email. Ignored once the pairing was accepted.

Response

Successful Response

executor_idstring required

wallet_addressstring required

The executor's payout wallet (lowercase)

reduced_sessionboolean

Always true: this session may work but may not change the wallet, the Solana payout address, delete the account, pair or unpair emails, or approve an H2A payment.

Changes

No recorded changes to this operation across all 1 revision of this API.