Read One Person's Full Detail by aVenture Profile URL, Slug, or URL
Start here for any aventure.vc person profile URL, slug, or personal profile URL. Exact read: returns the full PersonDetail (names, profile, company roles, and investments) of the one person a slug, URL, or candidate signals prove, so do not re-read it with getPerson or searchPeople; it answers 404 or 409 instead of guessing. For an existing-record name read, use POST /v1/people/search with personName (CLI people search —person-name) and verify the candidates against identity fields, roles, and evidenced URLs before reading an id. An empty search means no visible match for those filters, not permission to file. Choose universal lookup only when its possible filing effect is intended. Use the UUID item route for an id; any id query is rejected. Canonical redirects are preserved. A signed-in user’s read charges one view per distinct returned record against the monthly entity or person view allowance; a repeat read of the same record in the month is free, and an exhausted cap answers 429 with Retry-After.
Authentication
Your aVenture API key (https://aventure.vc/settings/api-keys) or OAuth access token
Query parameters
Group A — exact person slug (URL-friendly identifier). Mutually exclusive with id, url, and every candidate signal in group C.
Group B — aventure.vc person profile URL (such as https://aventure.vc/people/<slug>) or the person’s current profile URL, resolved via strict host+path or domain-only match. Mutually exclusive with id and slug; may be combined with group-C candidate signals for URL-first fallback.
Optional URL type qualifier for URL lookup (e.g., ‘linkedin’, ‘twitter’). Narrows Group B (url) and Group C (urlDomain) matching. Not an identifier on its own.
URL match mode qualifier: ‘hostPath’ (strict host + path match, default) or ‘domain’ (host-only match). Not an identifier on its own.
Group C — candidate lookup signal: person full name. A name alone never resolves (404): pair it with other group-C signals (location, urlDomain) or url. To find an existing person by name, use searchPeople with personName, compare candidate identity fields, roles, and evidenced URLs, then read the confirmed id. Search results are candidates, not identity verdicts. Choose universal lookup only when its possible filing effect is intended. For the people at a company, use listEntityPersonAssociations. Mutually exclusive with id and slug.
Group C — candidate lookup signal: loose name match (any of given/family/full). A name alone never resolves; combine it with other group-C signals or url. Mutually exclusive with id and slug.
Group C — candidate lookup signal: person location (city, state, country). Combine with other group-C signals for bounded search. Mutually exclusive with id and slug; may be combined with url for fallback.
Group C — candidate lookup signal: person URL domain (host only, no path). Combine with other group-C signals for disambiguation. Mutually exclusive with id and slug; may be combined with url for fallback.
Include URL link values in the response (default: true). Set false to omit urlLink array.
Include association values in the response (default: true). Set false to omit association array.
Include address values in the response (default: true). Set false to omit address array.
Maximum association values to return; the server caps it at its own association limit. Default: 40.
Permit generated monogram photo fallback (default: true). Set false to exclude monogram photos in response.
Profile panels to embed in this one read (repeat or comma-separate). Each named panel answers the same rows as its own endpoint’s first page; omitted panels stay absent.
Response headers
Requests allowed per client IP in the current rate-limit window.
Requests left before the tightest applicable rate-limit bucket rejects.
Seconds until the exhausted rate-limit bucket admits another request; 0 when none is exhausted.
Response
Supplemental person data — addresses and URL links
Investments associated with this person. When include names investment, these are newest first, the same rows as GET /v1/people/{personId}/investments?sort=date,desc&size=200 page 0: fewer than 200 rows is the whole list, otherwise continue at page=1 with the same sort and size.
Newest active blog posts first; present only when include names blogPost
The queued or running full-research run covering this record; null when none, and always null on people embedded in another record.
Precomputed person graph; present only when include names graph
Investor activity rollup; present only when include names investorActivity
Most similar people, highest score first; present only when include names similar