> ## Documentation Index > Fetch the complete documentation index at: https://docs.particle.pro/llms.txt > Use this file to discover all available pages before exploring further. # List fields of research > Lists one level of the ANZSRC 2020 Fields of Research: the divisions, the groups of a division, or the fields of a group. Every code, slug, and title listed here is accepted wherever speaker expertise is filtered by field. ## OpenAPI ````yaml /openapi.json get /v1/people/fields openapi: 3.1.0 info: contact: email: api@particle.pro name: Particle url: https://particle.pro description: >- Podcast API for transcripts, mentions and sponsorship data. 140,000+ podcasts transcribed, diarized and speaker-identified within minutes of airing, about 28,000 episodes a day. Search transcripts by keyword or meaning, track brand and company mentions with alerts, pull sponsor and ad-read data and rankings. REST API plus an MCP server for AI agents. Also company, people and topic intelligence. summary: >- Podcast API: transcripts, mentions, sponsors and rankings for 140,000+ podcasts. termsOfService: https://particle.pro/legal/tos-api title: Particle API version: 0.1.0 x-guidance: >- Podcast, people, company and topic intelligence. Authenticate with a pp_ API key (X-API-Key header) or pay per request with x402: a keyless call to a billable endpoint returns 402 with the payment requirements in the PAYMENT-REQUIRED header; sign the USDC transfer and repeat the request with PAYMENT-SIGNATURE. Start with GET /v1/podcasts/search?q=; the slugs in responses are the inputs to the other endpoints. Docs: https://docs.particle.pro; setup playbook: https://api.particle.pro/agents.md; endpoint and tool map with prices: https://api.particle.pro/llms.txt; credential recipe: https://api.particle.pro/auth.md. x-logo: url: https://particle.pro/favicon.svg servers: - url: https://api.particle.pro security: - ApiKeyHeader: [] - BearerAuth: [] externalDocs: url: https://docs.particle.pro paths: /v1/people/fields: get: tags: - People - tier:standard summary: List fields of research description: >- Lists one level of the ANZSRC 2020 Fields of Research: the divisions, the groups of a division, or the fields of a group. Every code, slug, and title listed here is accepted wherever speaker expertise is filtered by field. operationId: list-fields-of-research parameters: - description: 'Results per page (default: all)' explode: false in: query name: limit schema: description: 'Results per page (default: all)' format: int64 maximum: 100 minimum: 1 type: integer - description: Opaque pagination cursor from previous response explode: false in: query name: cursor schema: description: Opaque pagination cursor from previous response type: string - description: >- List the fields one level below this one: the groups of a division, or the fields of a group. Accepts its code (32), slug (biomedical-and-clinical-sciences), or title (Biomedical and Clinical Sciences). Omit to list the divisions. explode: false in: query name: parent schema: description: >- List the fields one level below this one: the groups of a division, or the fields of a group. Accepts its code (32), slug (biomedical-and-clinical-sciences), or title (Biomedical and Clinical Sciences). Omit to list the divisions. maxLength: 200 type: string - description: >- Search the fields by title instead of listing a level: words match in either number and by prefix, so cardiology finds Cardiology (incl. cardiovascular diseases). With parent, only fields below that one are searched. Best matches first. explode: false in: query name: q schema: description: >- Search the fields by title instead of listing a level: words match in either number and by prefix, so cardiology finds Cardiology (incl. cardiovascular diseases). With parent, only fields below that one are searched. Best matches first. maxLength: 200 type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/PageExpertiseCode' description: OK '402': content: application/problem+json: schema: $ref: '#/components/schemas/PlatformError' description: >- Payment Required. Read error_code. payment_required is the x402 path: either a keyless request being challenged — pay $0.01 in USDC per request (requirements in the PAYMENT-REQUIRED header) or send a pp_ API key — or a supplied payment that failed settlement (details in the PAYMENT-RESPONSE header; retry the same signature before signing a new one). See https://docs.particle.pro/x402. Any other code means the credential was accepted but does not cover this request (a plan or session gate such as premium_required or paid_plan_confirmation_required); its resolve says how to obtain access, and no payment header is sent. default: content: application/problem+json: schema: $ref: '#/components/schemas/PlatformError' description: Error x-codeSamples: - label: cURL lang: curl source: |- curl -H "X-API-Key: $PARTICLE_API_KEY" \ "https://api.particle.pro/v1/people/fields" components: schemas: PageExpertiseCode: additionalProperties: false properties: cursor: description: Pass to next request for more results type: string data: description: List of results items: $ref: '#/components/schemas/ExpertiseCode' type: - array - 'null' has_more: description: Whether more results exist type: boolean required: - data - has_more type: object PlatformError: additionalProperties: false properties: detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string error_code: type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string resolve: $ref: '#/components/schemas/ErrorResolve' status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object ExpertiseCode: additionalProperties: false properties: code: description: >- The standard's own notation, such as 29-1212 (SOC), 2212 (ISCO), or 320101 (FoR). type: string level: description: >- Depth in the standard's official hierarchy: SOC major group 1 and detailed occupation 2; FoR division 1, group 2, field 3; ISCO-08 unit group 4 and minor group 3. ISCO-08 codes are the groups SOC maps to, listed flat without the standard's upper levels. format: int64 type: integer parent_code: description: >- Code one level up; omitted at the top level and for every ISCO-08 code, since ISCO-08 is listed without its upper levels. type: string slug: description: The title as a URL segment, such as cardiologists. type: string standard: description: >- The standard the code belongs to: soc_2018 (US Standard Occupational Classification), isco_08 (the ILO's International Standard Classification of Occupations), or anzsrc_for_2020 (ANZSRC Fields of Research). enum: - soc_2018 - isco_08 - anzsrc_for_2020 type: string title: description: The standard's official title, such as Cardiologists. type: string required: - standard - code - title - slug - level type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object ErrorResolve: additionalProperties: false properties: action: type: string endpoint: type: string message: type: string method: type: string url: type: string required: - message type: object securitySchemes: ApiKeyHeader: description: Pass your API key in the X-API-Key header (recommended). in: header name: X-API-Key type: apiKey BearerAuth: description: Pass your API key as a Bearer token in the Authorization header. scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.