A name given to an individual at birth, baptism, or during another naming ceremony, or through legal change.
4.0
middleName
string
OPT
NOT REQ’D
A secondary name given to an individual at birth, baptism, or during another naming ceremony.
5.0
lastSurname
string
REQ’D
NOT REQ’D
The name borne in common by members of a family.
6.0
generationCodeSuffix
string
OPT
NOT REQ’D
An appendage, if any, used to denote an individual's generation in his family (e.g., Jr., Sr., III).
7.0
maidenName
string
OPT
NOT REQ’D
The individual's maiden name.
8.0
hispanicLatinoEthnicity
boolean
REQ’D
NOT REQ’D
An indication that the individual traces his or her origin or descent to Mexico, Puerto Rico, Cuba, Central, and South America, and other Spanish cultures, regardless of race. The term, "Spanish origin," can be used in addition to "Hispanic or Latino."
N/A
9.0
LocalPersonId
string
REQ’D
NOT REQ’D
A string uniquely identifying the person for the Vendor Software.
10.0
SexType
string
REQ’D
NOT REQ’D
Person’s gender. Valid options are: M = Male) , F = Female, or X = Non-Binary
Sending the name for staff who use an alternative name to identify themselves (e.g. Jimmy for James)
For staff, who use a nickname such as a shortened version of their legal name, their alternative name may be preferred over their legal name. However, this alternative name should NOT be reported to WISEdata.
While not required, LEAs may report the alternative names in WISEid Upload File manually or inside the WISEid App under Other Names.
Not submitted to WISEdata
2.0
Retrieving staff data from the WISEdata API
The the /staff endpoint is populated with person data submitted through the WISEid application. The staff Local Person ID will also be populated in this endpoint (only the staff persons who have a local Person ID will be populated).
SIS vendors are able to download the staff data from the /staffs endpoint. DPI strongly encourages SIS vendors to do a GET on /staffs to retrieve staff data that has been submitted to the WISEid application.
To be able to submit the /staffSectionAssociation endpoint, the /staff should be populated. For more information about the Local Person IDs and their relationship to Roster data, visit