Participant

Data Dictionary for Participant Data

The following example shows how the Golf participant data is identified. The data tables below will identify the properties available within the metadata.

{
  "id": 203533,
  "name": "Jordan Spieth",
  "firstName": "Jordan",
  "lastName": "Spieth",
  "gender": "male",
  "type": "athlete",
  "country": {
    "id": 16,
    "name": "USA"
  },
  "sports": [
    {
      "id": 3,
      "name": "Golf"
    }
  ],
  "meta": {
    "date-of-birth": {
      "code": "participant:date-of-birth",
      "name": "Date Of Birth",
      "value": "1993-07-27"
    },
    "height": {
      "code": "participant:height",
      "name": "Height",
      "value": "186"
    },
    "place-of-birth": {
      "code": "participant:place-of-birth",
      "name": "Place Of Birth",
      "value": "Dallas, TX"
    },
    "professional-status": {
      "code": "participant:professional-status",
      "name": "Professional Status",
      "value": "yes"
    },
    "status": {
      "code": "participant:status",
      "name": "Status",
      "value": "active"
    },
    "weight": {
      "code": "participant:weight",
      "name": "Weight",
      "value": "83"
    }
  },
  "updated": "2015-10-28T15:11:26Z",
  "links": [
    {
      "rel": "self",
      "href": "http://sport.api.press.net/v1/participant/203533"
    }
  ]
}
<?xml version="1.0" encoding="utf-8" ?>
<pa:sports-content xmlns="http://iptc.org/std/nar/2006-10-01/" xmlns:pa="http://sport-api.pa.press.net/2016-09-30/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <pa:sports-metadata doc-id="http://sport.api.press.net/v1/participant/203533" document-class="pa:participant-detail">
        <sports-title>Jordan Spieth</sports-title>
    </pa:sports-metadata>
    <pa:player id="player.203533">
        <pa:player-metadata key="player:203533" gender="male" nationality="USA">
            <name>Jordan Spieth</name>
            <sports-property formal-name="common:updated" value="2015-10-28T15:11:26Z"/>
            <sports-property formal-name="participant:date-of-birth" value="1993-07-27"/>
            <sports-property formal-name="participant:height" value="186"/>
            <sports-property formal-name="participant:place-of-birth" value="Dallas, TX"/>
            <sports-property formal-name="participant:professional-status" value="yes"/>
            <sports-property formal-name="participant:status" value="active"/>
            <sports-property formal-name="participant:weight" value="83"/>
            <pa:sports-content-codes>
                <sports-content-code code-type="pa:sport" code-key="sport:3" code-name="Golf"/>
            </pa:sports-content-codes>
        </pa:player-metadata>
    </pa:player>
</pa:sports-content>

Property Location

Content TypePath
JSON$.meta
XML/:sports-content/:player/:player-metadata/:sports-property
PropertyCodeExampleUnit
date-of-birthparticipant:date-of-birth1942-09-16Date
heightparticipant:height150Number (cm)
place-of-birthparticipant:place-of-birthPortugalString
professional-statusparticipant:professional-statusno*Boolean
statusparticipant:statusactive*String
weightparticipant:weight100Number (kg)

*Enumeration values

Code: participant:professional-status
no
yes

📘

Professional status in the API denotes 'pro/am' status

Code: participant:status
active
retired
unattached
dead

What’s Next