Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock (
) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
About
Available APIs
Guidance
Latest Releases
Post-Secondary Employment Outcomes (PSEO) Time Series (2001-2022)
The experimental Post-Secondary Employment Outcomes (PSEO) dataset is available as a Census Bureau API.
PSEO are experimental tabulations developed by the Center for Economic Studies' Longitudinal Employer-Household Dynamics (LEHD) Research program at the U.S. Census Bureau. PSEO data provide earnings and employment outcomes for college and university graduates by degree level, degree major, and post-secondary institution. These statistics are generated by matching university transcript data with a national database of jobs, using state-of-the-art confidentiality protection mechanisms to protect the underlying data.
The PSEO are made possible through data sharing partnerships between universities, university systems, State Departments of Education, State Labor Market Information offices, and the U.S. Census Bureau. PSEO data are available for post-secondary institutions whose transcript data has been made available to the Census Bureau through a data-sharing agreement.
For more information on the PSEO, see the PSEO data page. For information on other LEHD data products, check out the LEHD website.
-
Experimental Data ProductPost-Secondary Employment Outcomes (PSEO)PSEO data provide earnings and employment outcomes for college and university graduates by degree level, degree major, and post-secondary institution
-
Data ToolLocal Employment DynamicsThe LED Partnership leverages existing data in the development of new sources of economic and demographic information for policy makers and data users.
Earnings
- API Call: api.census.gov/data/timeseries/pseo/earnings
- Earnings Endpoint Detailed Variables: api.census.gov/data/timeseries/pseo/earnings/variables.html
- Examples and Supported Geographies
Flows
- API Call: api.census.gov/data/timeseries/pseo/flows
- Flows Endpoint Detailed Variables: api.census.gov/data/timeseries/pseo/flows/variables.html
- Examples and Supported Geographies
Basic Settings - Endpoint, Get Statement, Geography, Key
- Required: One endpoint – listed above.
- “earnings?” - Earnings
- “flows?” – Flows
- Required: A “get” statement – this is typically used to display indicators, but categorical variables, label fields, or status flags can also be added here. Categorical variables, label fields, and status flags in the “get” statement will display all available values.
- “get=Y1_P25_EARNINGS”
- Required: At least one geography in the “for” statement.
- “&for=us:1” requests national data
- "&for=division:1” requests Census Division data by FIPS code for the New England Division (Flows Endpoint only)
- All selections in the “get” statement must be separated by commas, all selections in the “for” statement must be separated by the ampersand (“&”) character.
- DEGREE_LEVEL is set to '05' (baccalaureate) if not included in the "get" or "for" statements. Default values for other categorical variables are assumed if not specified. Note that tabulations for all institutions will appear if an INSTITUTION is not specified in the "for" statement. We recommend adding LABEL_INSTITUTION to the "get" statement to differentiate the resulting tabulations. Examples showing the minimum requirements for a fully-formed basic query for the Earnings Endpoint and the Flows Endpoint:
The following two PSEO API queries demonstrate the key components available for each endpoint. The first query will return median earnings one year after graduation from the University of Texas – Austin with a baccalaureate degree in Computer and Information Sciences during the three-year 2001 cohort. The second query will return the count of those same graduates that are employed in the Professional, Scientific, and Technical Services industry in the Pacific Census Division one year after graduating. These two examples are repeated in each of the sections below, with the relevant statement bolded in the query.
Earnings:
Flows:
Select desired Indicators using the “get” statement.
- View available Earnings Indicators [TXT <1.0 MB]
- View available Flows Indicators [TXT <1.0 MB]
Earnings:
Flows:
- Select the desired Geography codes as a “predicate” using “&for” statement.
- Geographies represent the geography of the employer. Geography must be “national” for the Earnings endpoint and can be "national" or "division" for the Flows endpoint.
- View available division codes [TXT <1.0 MB]
Earnings:
Flows:
- Select desired Institution (OPEID) codes as a “predicate”.
- Institution codes are required to be eight characters long, with the last two digits representing sub-institution codes. As you can see in the above example, the University of Texas –Austin code is six digits with no sub-institution codes, so is represented as “00365800”.
- View all INSTITUTION codes [TXT <1.0 MB]
- View INSTITUTION codes [TXT <1.0 MB] for which PSEO has published data.
Earnings:
Flows:
- Select the State of the Institution as a “predicate”.
- View available INST_STATE (two-digit State FIPS) codes [TXT <1.0 MB]
- State of the Institution can be set to "00" to view online-only institutions.
Earnings:
Flows:
- Select desired Institution Level characteristic as a “predicate”.
- Institution Level can be set to “S” to view state-level aggregates.
- View available INST_LEVEL characteristics [TXT <1.0 MB]. Note only "I" and "S" currently have tabulations.
Earnings:
Flows:
- Select desired Degree Level characteristic as a “predicate”.
- View available DEGREE_LEVEL characteristics [TXT <1.0 MB]
Earnings:
Flows:
- Select desired CIP (Classification of Instruction Programs) Level characteristic as a “predicate”.
- CIP Level can be “2” or “4” for the Earnings Endpoint but only “2” for the Flows Endpoint.
- View available CIP_LEVEL characteristics [TXT <1.0 MB]
Earnings:
Flows:
- Select desired CIPCODE (Classification of Instruction Programs) characteristic as a “predicate”.
- CIP Codes can be two or four digits for the Earnings Endpoint. Four digit CIP Codes are formatted with a decimal after the first two digits – i.e. “11.01”. CIP Codes are only two digits for the Flows Endpoint.
- View available CIPCODE characteristics [TXT <1.0 MB]
- Select desired Industry/NAICS Sector characteristics as a “predicate”.
- View available NAICS characteristics [TXT <1.0 MB]
Earnings:
Flows:
- Select desired Graduation Cohort year as a “predicate”.
- Graduation Cohort year is a four digit number representing the first year of the graduation cohort. The number of years in the cohort is reported in the separate GRAD_COHORT_YEARS variable. When tabulating across all cohorts, the value “0000" will be used for GRAD_COHORT.
- Rules for determining valid values for GRAD_COHORT: if DEGREE_LEVEL=05 (i.e. Baccalaureate), valid values are 2001, 2004, 2007, 2010, 2013, 2016, 2019. For any other DEGREE_LEVEL, valid values are 2001, 2006, 2011, 2016.
Earnings:
Flows:
- Select the number of Graduation Cohort years as a “predicate”.
- The number of Graduation Cohort years is the number of year cohorts in the graduation cohort of reference. It varies by degree_level. Since tabulations are not done across degree levels, GRAD_COHORT_YEARS will be reported when GRAD_COHORT=0000.
- Rules for determining valid values for GRAD_COHORT_YEARS: if DEGREE_LEVEL=05 (i.e. Baccalaureate), GRAD_COHORT_YEARS=3 (3 year cohorts). For any other DEGREE_LEVEL, GRAD_COHORT_YEARS=5 (5 year cohorts).
- Get data for all characteristics in a Category Variable:
api.census.gov/data/timeseries/pseo/earnings?get=Y1_P50_EARNINGS,INSTITUTION,INST_STATE,DEGREE_LEVEL,CIP_LEVEL,CIPCODE,GRAD_COHORT&for=us:1&key=YOUR_KEY_GOES_HERE - Get data for multiple indicators and multiple Divisions:
api.census.gov/data/timeseries/pseo/flows?get=Y1_GRADS_EMP,Y5_GRADS_EMP,Y10_GRADS_EMP,INSTITUTION&for=division:2,4,5,9&key=YOUR_KEY_GOES_HERE
- Wildcards (“*”) can currently only be used to select Census Divisions – i.e. “&for=division:*”.
- The “get” statement can hold categorical variable names, labels, and status flags in addition to indicator names. Adding a categorical variable name to the “get” statement will include that column in the query results and returns all of its characteristics.
- Labels exist for all categorical variables – simply add “LABEL_” to the beginning of a categorical variable (i.e. LABEL_CIPCODE).
- Status flags [TXT <1.0 MB] exist for all indicators – simply add “STATUS_” to the beginning of an indicator (i.e. STATUS_ Y1_GRADS_EMP). The exception to this rule is the 25th, 50th, and 75th percentile earnings indicators are represented by a single status flag. For example, the status flag for Y1_P25_EARNINGS, Y1_P50_EARNINGS, and Y1_P75_EARNINGS would be STATUS_Y1_EARNINGS.
- Commas can be used to select multiple indicators, multiple geographies, and multiple graduation cohorts. Multiples for other categories can be requested via the “get” statement or using the complete parameter string in the “for” statement (i.e. “&NAICS=11&NAICS=54&NAICS=22”).
- The AGG_LEVEL_PSEO [TXT <1.0 MB] (“&AGG_LEVEL_PSEO=38”) variable is also available to query via the API. This field functions similar to a summary level and can be used to return all tabulations for a particular categorical variable crossing.
- CIP_LEVEL is not required when using CIPCODE, respectively. If CIP_LEVEL is used, make sure the values queried match the CIPCODE codes. For example, use CIP_LEVEL=2 when CIPCODE is two digits.
Check out data.census.gov, the Census Bureau's main data dissemination tool. You can access tables with PSEO data. You can also view data.census.gov Resources for step-by-step guidance, video tutorials, FAQs, and more.
Below are the links to the PSEO data tables on data.census.gov:
Earnings:
data.census.gov/table/PSEOEARNINGS.PSEOEARNINGS
Flows:
Related Information
The data provided represent official statistics released by the U.S. Census Bureau. Do not alter the precision of data values when storing or formatting them for display, or the results may disagree with the official releases. All products developed using these data files must attribute the data source as the U.S. Census Bureau. Include the originating program name for the benefit of your users.
Page Last Revised - January 3, 2025
✕
Is this page helpful?
Yes
No
Yes
No✕
NO THANKS
255 characters maximum
255 characters maximum reached
255 characters maximum reached
✕
Thank you for your feedback.
Comments or suggestions?
Comments or suggestions?
