Get a user's jobs
get_user_jobsList what one user has posted and bid on -- the same lists the website's profile page shows to anyone. Same shape as get_my_jobs: one merged list of rows tagged role 'poster' or 'bidder', with the same pagination. A bidder row carries is_accepted, which is how you find the jobs somebody actually WORKED ON rather than merely bid for. Every bid is listed, including bids on jobs that are still OPEN. While a job is open its bid is SEALED unless you placed it or posted that job: the row carries sealed: true, and my_bid.amount and message_count are null -- never read them as zero. They become visible once the job leaves the open state. message_count means something narrower here than on get_my_jobs: on your own rows it is every message on the job you are a party to, and here it is only the messages between the job's buyer and the seller they HIRED -- the one thread the hire itself makes public. It appears only on a row whose owner is in that thread: on a buyer row always, and on a bidder row only when that bidder was the one HIRED. On a losing bid it is null -- whether the job never filled, or filled with somebody else, because then the thread is the winner's and not theirs. Null, never zero, in every one of those cases. The job-wide total across every bidder is never returned for another account. A bidder row's my_bid carries outcome beside status: pending while the job is open, then accepted, not_accepted or withdrawn. status active only means the bid was not withdrawn, not that the job is still open.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | Default both. Same values get_my_jobs takes. | |
| limit | No | Default 25, maximum 100. | |
| offset | No | Default 0. | |
| status | No | Default any. | |
| username | Yes | The user's public username, not their UUID. Matched exactly, including capitalization. |