Anyone can use MAST interfaces to search for hosted data; anonymous users may preview and retrieve any publicly-available data. You do not need a user account to access most data, documentation, or the Archive Help Knowledge Base. If you have a MyST account, using the Login feature in MAST web tools is optional for public data.
Be aware that recent data from active missions can be protected during an Exclusive Access Period (EAP). During the EAP the Principal Investigator and their team have the opportunity to analyze and prepare their data for publication, and only authorized and authenticated users may retrieve the data. After the expiration of the EAP (denoted by the Release Date in MAST interfaces), the data become accessible to everyone without restriction. Metadata about observations that are under an EAP, such as coordinates, filters, exposure times, or footprints of the observations are available for anyone to see, including anonymous users.
EAP data can be queried from the MAST Portal, from the Hubble search interface, or from a MAST Application Programming Interface (API). EAP data are indicated in MAST interfaces in different ways, including the use of icons ( ).
User accounts enable MAST applications and services to authenticate individual users to the system. This is necessary only for some circumstances. Certain services also require prior authorization to use them, and authenticating via log-in is an essential step in that process.
User accounts for MAST are managed by STScI's Single Sign-On (SSO) system. SSO allows you to use your MyST credentials to log on to certain web-based services at the Institute, including the MAST Portal, the HST search interface, the STScI Grant Management System (STGMS), and the Astronomer's Proposal Tool. Rather than have each service maintain separate user accounts, logging in through the SSO Portal means remembering only one username and password.
If you have ever been a named Principal Investigator (PI) or Co-Investigator (Co-I) on an HST or JWST proposal, or have ever received a research grant managed by STScI, you probably already have a MyST account. You can verify whether you already have a MyST account with the MyST lookup tool by entering your email address. You may create a new account from the MyST home page.
Who Needs a MAST User Account?
User accounts are only needed for certain purposes, as described in the sub-sections below. Logging in to one of the MAST applications will authenticate your identity during the lifetime of your MAST session.
Subscriptions to Data
Subscribing to data notifications for active missions requires a log-in. You may subscribe to be informed when data are first received in the Archive, are reprocessed for some reason, or have become public.
Currently, subscriptions for data notifications are only available through the MAST Portal.
Accessing EAP Data
Previewing and retrieving EAP protected data requires both authentication and authorization. EAP data can be accessed from the MAST Portal, from the Hubble search interface, from the ftp server staging disk at archive.stsci.edu, or from a MAST Application Programming Interface (API).
Principal Investigators (PIs) for approved observing programs with HST or JWST are automatically authorized to access data from their program(s).
Accessing JWST Engineering Data
Using the MAST HelpDesk Portal
The MAST HelpDesk Portal provides links to certain MAST resources, and after logging in you can submit requests for assistance and track the responses to your questions.
Using the HelpDesk Portal is optional. You may instead simply send e-mail to email@example.com.
MAST also offers API token authorization for programmatic access to EAP data. Users with a MyST Account can find instructions on creating and using these tokens on the auth.MAST documentation page. With a valid token in place, authorized users will then be able to retrieve MAST EAP data through Astroquery or cURL scripts. See the video on Using Auth.MAST Tokens in the Demos and Tutorials chapter of the Portal Guide. The steps are simply:
- Navigate to the Tokens page and click the Create Token button.
- Record the long, alpha-numeric string in the environment variable
$MAST_API_TOKEN, preferably in your
.bashrcor equivalent shell file.
Be aware that API tokens expire after 10 days of inactivity or 60 days after creation, whichever comes first. Users experiencing difficulty with existing tokens should try generating a new one.