> ## 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. # Get a field of research > Returns one ANZSRC 2020 field of research with its parent and children. The {code} parameter accepts the code, slug, or title. > [!TIP] > > Prefer the terminal? This endpoint is also a command in the Particle CLI: pick **Particle CLI** in the request example's language menu. [Install the Particle CLI](https://cli.particle.pro). ## OpenAPI ````yaml /openapi.json get /v1/people/fields/{code} 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/{code}: get: tags: - People - tier:standard summary: Get a field of research description: >- Returns one ANZSRC 2020 field of research with its parent and children. The {code} parameter accepts the code, slug, or title. operationId: get-field-of-research parameters: - description: >- The field of research's ANZSRC 2020 code (320101), slug (cardiology-incl-cardiovascular-diseases), or title. A title a group shares with one of its own fields resolves to the group. in: path name: code required: true schema: description: >- The field of research's ANZSRC 2020 code (320101), slug (cardiology-incl-cardiovascular-diseases), or title. A title a group shares with one of its own fields resolves to the group. maxLength: 200 type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/ExpertiseCodeDetail' 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/{code}" - label: Particle CLI lang: bash source: |- # Install: https://cli.particle.pro particle field components: schemas: ExpertiseCodeDetail: additionalProperties: false properties: children: description: >- Every code one level down; omitted for the most specific level. Below a SOC major group are its minor groups, below a minor group its broad groups, and below a broad group or an alias its detailed occupations. items: $ref: '#/components/schemas/ExpertiseCode' type: - array - 'null' code: description: >- The standard's own notation, such as 29-1212 (SOC), 2212 (ISCO), or 320101 (FoR). type: string equivalents: description: >- The same occupation in the other occupation standard, per the official BLS SOC 2018 to ISCO-08 crosswalk: the ISCO groups a SOC occupation maps to, or the SOC occupations that map to an ISCO group. Omitted for fields of research. items: $ref: '#/components/schemas/ExpertiseCode' type: - array - 'null' group: description: >- Set for a code that stands for several detailed SOC 2018 occupations: a SOC minor group (such as 29-1000 Healthcare Diagnosing or Treating Practitioners), a broad group (such as 29-1210 Physicians), or an alias, an everyday name such as doctors (physicians and surgeons). Every occupation filter accepts one and matches a speaker listed under any of its occupations. enum: - minor - broad - alias 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. Omitted for a SOC group or alias (see group). format: int64 type: integer parent: $ref: '#/components/schemas/ExpertiseCode' description: >- The code one level up as you browse, the reverse of children: a detailed SOC occupation's broad group, a broad group's minor group, a minor group's major group. Omitted at the top level and for ISCO-08 codes. parent_code keeps the standard's official parent, which for a detailed SOC occupation is its major group. parent_code: description: >- The standard's official parent code; omitted at the top level and for every ISCO-08 code, since ISCO-08 is listed without its upper levels. A SOC broad group's parent is its minor group and a minor group's its major group, but a detailed SOC occupation's official parent is its major group (29-1211 has parent_code 29-0000), so it can differ from parent, which is the browse parent one level up (29-1210). 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 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 group: description: >- Set for a code that stands for several detailed SOC 2018 occupations: a SOC minor group (such as 29-1000 Healthcare Diagnosing or Treating Practitioners), a broad group (such as 29-1210 Physicians), or an alias, an everyday name such as doctors (physicians and surgeons). Every occupation filter accepts one and matches a speaker listed under any of its occupations. enum: - minor - broad - alias 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. Omitted for a SOC group or alias (see group). format: int64 type: integer parent_code: description: >- The standard's official parent code; omitted at the top level and for every ISCO-08 code, since ISCO-08 is listed without its upper levels. A SOC broad group's parent is its minor group and a minor group's its major group, but a detailed SOC occupation's official parent is its major group (29-1211 has parent_code 29-0000), so it can differ from parent, which is the browse parent one level up (29-1210). 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 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.