The SEER API is a RESTful Web service that supports various SEER Program data sets and mapping. This service is available to developers who wish to incorporate SEER resources into their own systems. These resources include databases and tools developed to enhance registry operations and quality improvement. The SEER API is designed for integration into registry computer systems and is not designed to be accessed by end-users.

The goal of SEER API is to provide a centralized repository of SEER Program tools that is available to all programming environments and operating systems. The API is based on REST principles, therefore, it is very easy to write and test applications. You can use your browser to access URLs and to test APIs. Any programming language that can read HTTP data from a URL can use web services. Results are returned in JSON format which can be easily parsed and interpreted. See the Usage page for language-specific examples.

The SEER API powers a variety of SEER tools, including:

The Surveillance, Epidemiology and End Results (SEER) Program is a premier source for cancer statistics in the United States. The SEER Program collects information on incidence, prevalence and survival from specific geographic areas representing 28 percent of the US population and reports on all these data plus cancer mortality data for the entire country.

Recent Changes

October 11, 2018

  • The required query parameters for the /rest/disease/{version}/same_primary endpoint were modified. Instead of using a single year parameter it now requires two years to be supplied. One year for the first disease and one year for the second disease. The old year parameter was called "year" and the new parameters are called "year1" and "year2".

April 19, 2018

  • The NDC entities were modified to add SEER-maintained categorization information.

March 20, 2018

  • NAACCR 18 definitions were added to the NAACCR API (/rest/naaccr).
  • A new algorithm, "eod_public", was added to the staging API (/rest/staging). For more information on EOD and how the staging API works in general, see staging-client-java for details.