curl -H "X-API-Key: $PARTICLE_API_KEY" \
"https://api.particle.pro/v1/people/{id}/expertise"{
"standing": "established",
"capacity": "<string>",
"career_start_year": 123,
"credential": "<string>",
"experience": "at_least_10_years",
"fields": [
{
"code": "<string>",
"level": 123,
"slug": "<string>",
"standard": "soc_2018",
"title": "<string>",
"parent_code": "<string>"
}
],
"occupations": [
{
"code": "<string>",
"level": 123,
"slug": "<string>",
"standard": "soc_2018",
"title": "<string>",
"established": true,
"parent_code": "<string>",
"practicing": true
}
],
"organization": {
"name": "<string>",
"company": {
"id": "<string>",
"name": "<string>",
"description": "<string>",
"domain": "<string>",
"image_url": "<string>",
"slug": "<string>",
"ticker": "<string>"
},
"kind": "<string>"
},
"seniority": "professional"
}{
"detail": "Property foo is required but is missing.",
"error_code": "<string>",
"errors": [
{
"location": "<string>",
"message": "<string>",
"value": "<unknown>"
}
],
"instance": "https://example.com/error-log/abc123",
"resolve": {
"message": "<string>",
"action": "<string>",
"endpoint": "<string>",
"method": "<string>",
"url": "<string>"
},
"status": 400,
"title": "Bad Request",
"type": "https://example.com/errors/example"
}{
"detail": "Property foo is required but is missing.",
"error_code": "<string>",
"errors": [
{
"location": "<string>",
"message": "<string>",
"value": "<unknown>"
}
],
"instance": "https://example.com/error-log/abc123",
"resolve": {
"message": "<string>",
"action": "<string>",
"endpoint": "<string>",
"method": "<string>",
"url": "<string>"
},
"status": 400,
"title": "Bad Request",
"type": "https://example.com/errors/example"
}Get a Person's expertise
Returns what the Person’s records say about their expertise, in words: the SOC 2018 and ISCO-08 occupations and ANZSRC 2020 fields of research they are listed under (each usable as a filter by code, slug, or title), how their standing is recognized, their seniority and experience, how they know their field, where they work, and a sentence stating their credentials. Hosts, guests, panelists, and correspondents are read once linked to a podcast appearance; anyone else returns 404. The parameter accepts the Person slug (recommended) or the encoded Person UUID.
curl -H "X-API-Key: $PARTICLE_API_KEY" \
"https://api.particle.pro/v1/people/{id}/expertise"{
"standing": "established",
"capacity": "<string>",
"career_start_year": 123,
"credential": "<string>",
"experience": "at_least_10_years",
"fields": [
{
"code": "<string>",
"level": 123,
"slug": "<string>",
"standard": "soc_2018",
"title": "<string>",
"parent_code": "<string>"
}
],
"occupations": [
{
"code": "<string>",
"level": 123,
"slug": "<string>",
"standard": "soc_2018",
"title": "<string>",
"established": true,
"parent_code": "<string>",
"practicing": true
}
],
"organization": {
"name": "<string>",
"company": {
"id": "<string>",
"name": "<string>",
"description": "<string>",
"domain": "<string>",
"image_url": "<string>",
"slug": "<string>",
"ticker": "<string>"
},
"kind": "<string>"
},
"seniority": "professional"
}{
"detail": "Property foo is required but is missing.",
"error_code": "<string>",
"errors": [
{
"location": "<string>",
"message": "<string>",
"value": "<unknown>"
}
],
"instance": "https://example.com/error-log/abc123",
"resolve": {
"message": "<string>",
"action": "<string>",
"endpoint": "<string>",
"method": "<string>",
"url": "<string>"
},
"status": 400,
"title": "Bad Request",
"type": "https://example.com/errors/example"
}{
"detail": "Property foo is required but is missing.",
"error_code": "<string>",
"errors": [
{
"location": "<string>",
"message": "<string>",
"value": "<unknown>"
}
],
"instance": "https://example.com/error-log/abc123",
"resolve": {
"message": "<string>",
"action": "<string>",
"endpoint": "<string>",
"method": "<string>",
"url": "<string>"
},
"status": 400,
"title": "Bad Request",
"type": "https://example.com/errors/example"
}Authorizations
Pass your API key in the X-API-Key header (recommended).
Path Parameters
Person identifier. Accepts the Person slug (recommended) or the encoded Person UUID.
Response
OK
How the speaker's standing is recognized: established (conferred by others: a credential, a position, recognition in the field), self_described (claimed by the speaker), or unverified (the records do not say, which never means the speaker is not an expert).
established, self_described, unverified How the speaker knows their field: researcher, licensed_professional, practitioner, executive_founder, public_official, journalist_analyst, creator_entertainer, athlete_coach, clergy, firsthand, or layperson. Omitted when no single capacity is likely.
The year of the earliest dated role or degree in the speaker's records.
A sentence from the speaker's records, verbatim, that states their credentials.
How long the speaker's career spans, from the earliest dated role or degree in their records or as the records state it; omitted under ten years or when the records do not say.
at_least_10_years, at_least_25_years The ANZSRC 2020 fields of research the speaker is listed under, most specific first (see GET /v1/people/fields).
Show child attributes
Show child attributes
The SOC 2018 occupations, then the ISCO-08 groups, the speaker is listed under, most specific first. Filter by any of them with its code, slug, or title (see GET /v1/people/occupations).
Show child attributes
Show child attributes
Where the speaker works, when their records name an organization.
Show child attributes
Show child attributes
The highest level the speaker has reached in their field; omitted below professional.
professional, senior, distinguished Was this page helpful?