include:
top_guestsranks the guests listed under the code by podcast appearances in a window, then by how many distinct shows booked them.top_podcastsranks the shows that booked the code’s guests most.
standing="established" ranks only credentialed or recognized experts, so “the shows that book established finance experts” is field plus top_podcasts plus standing. A broad code covers everything below it: a SOC major group or an ANZSRC division ranks every occupation or field inside it.
Take codes from particle_expertise_resolve. Guest slugs work with particle_person_get (include: ["expertise"]) and particle_podcast_get_guest; podcast slugs work with every podcast tool.
For a guest search with several criteria (practicing, seniority, capacity, employer, all-time appearances), use particle_podcast_list_guests. For one show’s guest mix, use particle_podcast_resolve with include: ["guest_expertise"].
Inputs
Passing neither
occupation nor field returns missing_parameter; passing both returns invalid_input. A window longer than 90 days, or one whose since falls after until, returns invalid_parameter. A code that names nothing returns not_found with the closest codes as did-you-mean suggestions, pointing at particle_expertise_resolve.
Output
A markdown document with the code’s title as an H2, then**Standard:**, **Code:**, **Slug:** and **Level:** rows, a **Parent:** row (Title (code, slug)) below the top level, and an **Equivalents:** row for an occupation with crosswalk counterparts. A ### Children (N) section lists every code one level down, each as Title (code, slug). The following H3 sections appear when requested:
### Top guests— an italic line naming the window (and<standing> guests onlywhenstandingis set), then numbered lines formattedN. Name (person-slug) — A appearances on P shows, last YYYY-MM-DD.### Top podcasts— the same window line, then numbered lines formattedN. Podcast title (podcast-slug) — A appearances by G guests, last YYYY-MM-DD.
field="banking-finance-and-investment", include=["top_guests","top_podcasts"], standing="established", limit=3, truncated):
Example
Related
- REST equivalents:
GET /v1/people/occupations/{code}andGET /v1/people/fields/{code}for the code;/guestsand/podcastsbelow them for the boards, with the samestandingparameter. - Find a code with
particle_expertise_resolve. - Filter guests on more criteria with
particle_podcast_list_guests; filter shows by their guest mix withparticle_podcast_resolve.