# Turn the Clearinghouse secure site into an API > Read your pending verification requests, Error Resolution Report errors and Reject Detail records from the Clearinghouse secure site with one API call each. Or have a workflow check the Research Needed queue each morning and email you the new requests. Page: https://fous.com/automate/national-student-clearinghouse-secure-site Updated: 2026-11-12 Works with your own National Student Clearinghouse secure site account. Fous is an independent product. ## What you can build on the School Secure Site ### List pending verification requests Reads the Action Required section of the Verification Services Dashboard: every request in Research Needed status, oldest first. - Takes: Nothing - Returns: Transaction ID, status, status date, degree levels requested, potential match, student details ### Check the Error Resolution Report Opens the Enrollment Reporting (Error Resolution Report) tile on the Data Reporting Dashboard and reads the error list, with the errors that must be corrected. - Takes: Nothing - Returns: Error code, description, record count, must be corrected, affected students ### Get Reject Detail records Reads the Reject Detail (School Review) and Reject Detail (All Records) tabs of the Enrollment Reporting (Reject Detail) tile after a file is processed. - Takes: Tab (School Review or All Records) - Returns: Student name, error information, tab ### Close a verification with dates of attendance Opens one pending request by transaction ID, selects Manage Request and closes it with Close with Dates of Attendance. - Takes: Transaction ID, attendance start date, attendance end date - Returns: Transaction ID, new status ## Automate the School Secure Site with a workflow A [workflow](/product/workflows) runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use. ### New Research Needed verification requests, every morning Starts: Every weekday at 7:30 1. List the pending verification requests in the Action Required section. 2. Keep the requests that were not there on the last run. 3. Email you the list, oldest first, with transaction ID, status date and degree levels requested. ### Open errors on the Error Resolution Report Starts: Every weekday at 8:00 1. Check the Error Resolution Report on the Data Reporting Dashboard. 2. Stop when it lists no errors. 3. Email you each error code, description and record count, with the errors that must be corrected first. ### New Reject Detail records, posted to your student system Starts: Every Monday at 9:00 1. Get the Reject Detail records from the All Records tab. 2. Keep the records that were not there on the last run. 3. Post each one, with the student's name and error information, to your webhook. You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month. ## Once built, one call from your code Once you have built a [method](/product/methods), it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “List pending verification requests” would look like. Example request: ``` curl https://api.fous.com/v1/runs \ -H "Authorization: Bearer $FOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "method": "secure.studentclearinghouse.org/list_pending_verifications", "input": {} }' ``` Example response: ``` { "status": "completed", "data": { "requests": [ { "transaction_id": "48213907", "status": "Research Needed", "status_date": "2026-11-04", "degree_levels_requested": [ "Bachelor's" ], "potential_match": false, "student": { "date_of_birth": "1998-03-14" } } ], "count": 1 } } ``` An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request. ## The School Secure Site’s own options The Clearinghouse takes enrollment reporting files through its Secure FTP site, which has a web interface and supports automated scripts, in an Excel/text or EDI format. Errors, rejects and verification requests are then worked by hand on the School Secure Site. Its MFA help page says APIs do not require MFA, but no API is documented for these screens. | Option | What it covers | What it takes | | --- | --- | --- | | Secure FTP | Sends enrollment reporting files to the Clearinghouse and retrieves files from it, by web browser or by automated script. | A Secure FTP account for your institution. | | Enrollment file formats | Excel/text and EDI layouts with header, detail and trailer records, sent on a transmission schedule of about 12 files a year. | An extract from your student information system in one of these formats. | | The School Secure Site by hand | Error Resolution on the Web, Reject Detail, the Verification Services Dashboard and Student Look-Up, one screen at a time. | A user name and password for your institution's account, with MFA. | Read on November 12, 2026: [Secure FTP knowledge base](https://help.studentclearinghouse.org/dataexchange/article-categories/secure-ftp/), [About Enrollment Reporting](https://help.studentclearinghouse.org/compliancecentral/knowledge-base/about-enrollment-reporting/), [Multi-Factor Authentication (MFA) Support](https://help.studentclearinghouse.org/schoolsecuresite/knowledge-base/mfa-support/). ## Signing in to the School Secure Site The School Secure Site asks for your user name and password under User Login, then an MFA code once MFA is enabled: Google Authenticator, SMS or, as a last resort, email. A trusted device skips the code for 30 days. With Fous you sign in once through the site's own sign-in with your own account: the login is sealed with AES-256, an emailed code is handled, and an expired session is signed back in. ## Worth knowing - **Errors in red hold the whole file**: Errors shown in red must be corrected before the Clearinghouse loads your enrollment file. Warnings are passable. The Clearinghouse suggests finishing corrections within 1 to 3 days, then clicking I Am Done. - **Rejects appear only after processing**: Check the Future Transmission tab of the Submission Schedule tile for Edits Completed or Processed Transmission first. Rejected records are fixed in your own system and on the Student Look-Up tab. - **Error reports go to two roles**: The error resolution report is emailed to the users with the Submission Data and Submission Data Alternate roles. Other users find it on the Data Reporting Dashboard. - **Files go in date order, about monthly**: A transmission schedule has about 12 transmissions per academic year, and files must be sent in chronological order. The Clearinghouse generates the yearly schedule by July 31. ## More in Education, research and nonprofit - [Slate](https://fous.com/automate/slate.md) - [Naviance](https://fous.com/automate/naviance.md) - [Common App for Recommenders](https://fous.com/automate/common-app-for-recommenders.md) - [AQA Centre Services](https://fous.com/automate/aqa-centre-services.md) - [Edexcel Online](https://fous.com/automate/edexcel-online.md) - [FSA Partner Connect](https://fous.com/automate/fsa-partner-connect.md) - [Submit learner data](https://fous.com/automate/submit-learner-data.md) - [VA Enrollment Manager](https://fous.com/automate/va-enrollment-manager.md) - [Sponsorship Management System](https://fous.com/automate/sponsorship-management-system.md) - [Infinite Campus](https://fous.com/automate/infinite-campus.md) - [PowerSchool SIS](https://fous.com/automate/powerschool-sis.md) - [EDOF](https://fous.com/automate/edof.md) - [Arbor MIS](https://fous.com/automate/arbor-mis.md) - [SLC HEP Services](https://fous.com/automate/slc-hep-services.md) - [Parchment](https://fous.com/automate/parchment.md) - [UCAS adviser portal](https://fous.com/automate/ucas-adviser-portal.md) - [Benevity Causes Portal](https://fous.com/automate/benevity-causes-portal.md) Other industries: [Con Edison My Account](/automate/con-edison-my-account), [BEES](/automate/bees), [ANZ Transactive - Global](/automate/anz-transactive), [e-OSCAR](/automate/e-oscar), [Edabu](/automate/edabu), [EPFO Unified Portal (Employer)](/automate/epfo-unified-portal-employer). ## Frequently asked questions ### Does the National Student Clearinghouse secure site have an API? Not one documented for schools' error, reject or verification screens. Enrollment files go in through Secure FTP, by browser or automated script, in Excel/text or EDI format. The MFA help page says APIs do not require MFA, but the corrections and the verification queue are worked on the School Secure Site by hand. ### Where do I find rejected enrollment records? On the Data Reporting Dashboard, in the Enrollment Reporting (Reject Detail) tile, under the Reject Detail (School Review) and Reject Detail (All Records) tabs. They appear once your file shows Edits Completed or Processed Transmission. Rejects are usually caused by an SSN inaccuracy. ### How often do we have to send enrollment files? About 12 times per academic year, one every 30 to 45 days. Semester schools send at least one First-of-Term, two Subsequent-of-Terms and one End-of-Term transmission per term, and files must go in chronological order. ### Does every sign-in ask for an MFA code? No. When you register a trusted device, the School Secure Site skips the code for 30 days on the same device and browser. A different browser, another device or a private window always asks for it. ### Is Fous affiliated with the National Student Clearinghouse? No. Fous is an independent product. You use it with your own School Secure Site account, and a method reads and does only what that account can. Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of National Student Clearinghouse secure site (National Student Clearinghouse). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.