Get a follow-up
One follow-up: its status, and once it ended, its outcome and what was found.
status is waiting, next_check_at is when the place is looked in next and checks how many times it has been. Once status is done, outcome is found, time_up, or expired, and found holds only the thing that arrived: its kind, a one-line summary, and the code, link, file_url and file_name, or a short text, with sender, subject, and received_at. note is one plain line on how it ended.
cancelled and failed follow-ups stay readable; failed means the place could not be checked (note says why, for example the app was disconnected).
Only your own; anyone else gets 404. Needs followups:read. MCP tool: get_followup.Authorizations
API key with the vd_sk_ prefix, as Authorization: Bearer vd_sk_.... Create keys in Settings → API Keys.
Path Parameters
Response
The follow-up: once it ended, its outcome and what was found.
Who is waiting: api for one made here; igris, session or brain for one an in-app agent made.
igris, session, brain, api waiting: timed and checked. done: ended (outcome says how). cancelled. failed: could not be checked (note says why).
waiting, done, cancelled, failed The session or workflow of an in-app agent; empty here.
found: it arrived (found holds it). time_up: a check-back's time came. expired: nothing came in time.
found, time_up, expired The thing that arrived — only it, never the rest of the mailbox.
One plain line on how it ended.
Only things that arrived after this count.
How many times the place was looked in.

