CollegeScoreCard.ed.gov Getting Started: API Access (2026)

Getting started overview

The College Scorecard API offers direct access to data on college costs, graduation rates, earnings, and debt for institutions across the United States. This guide outlines the process for obtaining an API key and making your initial request, enabling access to the College Scorecard data documentation. The API is designed for researchers, developers, and data analysts who require programmatic access to higher education statistics. All data provided through the API is publicly available and free to use, making it a resource for various applications, including academic research on higher education, policy analysis, and student guidance on college selection.

The College Scorecard data is regularly updated and maintained by the U.S. Department of Education. It provides a standardized way to compare institutions based on key metrics. The API is RESTful, returning data in JSON format, which is a common data interchange format for web services, as described by JSON.org. Understanding the API's structure and available endpoints is crucial for effective data retrieval, and the official College Scorecard API reference provides detailed information on parameters and responses.

Quick Reference Steps

Create an account and get keys

To access the College Scorecard API, you must obtain an API key. This key authenticates your requests and helps the Department of Education manage usage. The process typically involves a simple registration on the official College Scorecard data portal. While the data itself is free and publicly available, the API key helps ensure fair use and provides a mechanism for contact regarding important updates or changes to the service.

1. Navigate to the API Documentation: Start by visiting the College Scorecard API documentation page. This page contains the most current information regarding API access and key acquisition.
2. Locate the API Key Request Section: Within the API documentation, there will be a specific section dedicated to obtaining an API key. This typically involves filling out a short form.
3. Provide Required Information: You will likely need to provide your name, email address, and a brief description of how you intend to use the API. This information helps the Department of Education understand the diverse applications of the data.
4. Submit the Request: After filling out the form, submit your request. The API key is usually sent to your provided email address within a short period. Check your spam or junk folder if you do not receive it promptly.
5. Store Your API Key Securely: Once you receive your API key, treat it like a password. Do not hardcode it directly into client-side code, and avoid sharing it publicly. For server-side applications, consider using environment variables or a secure configuration management system to store the key. The Google Cloud documentation on API keys provides general best practices for securing API keys.

It is important to note that there is no concept of a paid tier for the College Scorecard API; the entire dataset is publicly available for free. The API key is solely for identification and usage monitoring purposes.

Your first request

After acquiring your API key, you can make your first request to the College Scorecard API. This example demonstrates how to retrieve data for a specific college, illustrating the basic structure of an API call. The API base URL is https://api.data.gov/ed/collegescorecard/v1/schools.

Example: Fetching Data for a Specific School

Let's retrieve information for a school, for instance, by its ID. You would append your API key to the request URL using the api_key parameter.

Using cURL (Command Line)

Replace YOUR_API_KEY with the key you received.

curl "https://api.data.gov/ed/collegescorecard/v1/schools?api_key=YOUR_API_KEY&_fields=school.name,latest.admissions.admission_rate.overall&school.name=Harvard%20University"

This cURL command requests the school name and overall admission rate for 'Harvard University'. The _fields parameter is used to specify which fields to return, optimizing the response size. The API supports a wide range of query parameters for filtering, sorting, and selecting specific data fields, as detailed in the College Scorecard API documentation.

Using Python

For programmatic access, Python is a common choice due to its extensive libraries for HTTP requests and JSON parsing.

import requests
import json

api_key = "YOUR_API_KEY" # Replace with your actual API key
base_url = "https://api.data.gov/ed/collegescorecard/v1/schools"

params = {
    "api_key": api_key,
    "_fields": "school.name,latest.admissions.admission_rate.overall,latest.cost.attendance.academic_year",
    "school.name": "Massachusetts Institute of Technology"
}

response = requests.get(base_url, params=params)

if response.status_code == 200:
    data = response.json()
    print(json.dumps(data, indent=2))
else:
    print(f"Error: {response.status_code}")
    print(response.text)

This Python script fetches the school name, admission rate, and academic year attendance cost for 'Massachusetts Institute of Technology'. The requests library simplifies HTTP interactions, and json handles parsing the API's JSON response.

Using a Web Browser

You can also test simple API calls directly in your web browser. Paste the URL, including your API key and parameters, into the address bar. The browser will display the JSON response directly.

https://api.data.gov/ed/collegescorecard/v1/schools?api_key=YOUR_API_KEY&_fields=school.name,latest.admissions.admission_rate.overall&school.name=Stanford%20University

This method is useful for quickly verifying endpoint functionality and understanding the basic structure of the returned data.

Common next steps

Once you have successfully made your first request, several common next steps can enhance your use of the College Scorecard API:

1. Explore Additional Endpoints and Parameters: The API offers various endpoints for different types of data, and extensive parameters for filtering, sorting, and selecting specific fields. Review the detailed API documentation to discover the full range of available data and how to query it effectively. For example, you can query by location, size, or specific program offerings.
2. Implement Pagination and Rate Limiting: For large datasets, the API uses pagination to return results in manageable chunks. Learn how to use the _page and _per_page parameters to navigate through results. Additionally, be aware of the API's rate limits to avoid hitting request caps, which are typically outlined in the API usage policies.
3. Error Handling: Integrate robust error handling into your application. The API returns standard HTTP status codes (e.g., 400 for bad request, 403 for forbidden, 500 for server error) and often includes descriptive error messages in the JSON response. Properly handling these errors ensures your application remains stable.
4. Data Storage and Analysis: Depending on your project, you might need to store the retrieved data in a database for further analysis or to build a local cache. Tools like Python's Pandas library or R's data frames are excellent for manipulating and analyzing the structured data obtained from the API.
5. Build a User Interface: For student guidance or public-facing applications, consider building a user interface that consumes the API data to present it in an accessible and interactive way. Web frameworks like React, Angular, or Vue.js can be used to create dynamic data visualizations and search tools.
6. Stay Updated: The College Scorecard dataset and API may receive updates. Regularly check the official College Scorecard website and documentation for announcements regarding new data fields, API version changes, or deprecations.

Troubleshooting the first call

Encountering issues during your first API call is common. Here's a guide to diagnosing and resolving typical problems:

• Invalid API Key (HTTP 403 Forbidden):
  • Check for typos: Ensure your API key is copied exactly as provided.
  • Key not active: Confirm that your API key has been activated. Sometimes there's a short delay after registration.
  • Missing key: Verify that the api_key parameter is included in your request URL.
• Bad Request (HTTP 400):
  • Incorrect parameter names: Double-check the spelling and casing of all parameters (e.g., _fields, school.name) against the API documentation.
  • Invalid parameter values: Ensure that the values you're passing for parameters are in the correct format (e.g., numeric values for IDs, correctly encoded strings for names). URL encoding issues, as detailed by Mozilla Developer Network on URL encoding, can cause problems with special characters in parameter values.
  • Missing required parameters: Some endpoints may have mandatory parameters. Consult the documentation for specific requirements.
• Not Found (HTTP 404):
  • Incorrect base URL: Verify that the base URL for the API endpoint is correct (e.g., https://api.data.gov/ed/collegescorecard/v1/schools).
  • Endpoint does not exist: Ensure you are calling a valid endpoint.
• Server Error (HTTP 500 or 503):
  • These usually indicate an issue on the API provider's side.
  • Retry: Wait a few minutes and try the request again.
  • Check status page: Look for any service status announcements on the College Scorecard homepage or documentation.
• No Data Returned (Empty Array or Null):
  • Filtering too strictly: Your query parameters might be too restrictive, resulting in no matching data. Try broadening your search criteria.
  • Data field not present: The specific data field you are requesting might not exist for the entity you are querying.
• Rate Limit Exceeded (HTTP 429 Too Many Requests):
  • You've sent too many requests in a short period.
  • Back off: Implement a delay between your requests or use a rate limiting strategy to stay within the API's limits.

When troubleshooting, always refer to the specific error message provided in the API response, as it often contains direct clues about the problem. Logging your requests and responses can also be invaluable for debugging.