Submit through the gateway
Send a signed-off packet through the right submission gateway.
By the end you’ll be able to
- Understand the gateway submission step and its preconditions.
- Submit a signed-off packet in the demo.
- Distinguish API gateways from portal-upload returns.
Once a return is signed off you submit it. For the HESA Data Futures streams that means the HESA Data Futures Gateway (`@databridge/hesa-gateway-client`); for TCSI it's the TCSI API via PRODA. For the UK portal returns (TEF, KEF, SLC SBR, UCAS HEI) submission is an operator upload: DataBridge produces a CSV + tamper-evident manifest and you upload it through the regulator's portal (`docs/RETURNS_COMPLETENESS.md`).
The submission step refuses to send a return that hasn't passed sign-off. The handshake records the submission id and the gateway's acknowledgement on the audit log so the round-trip is provable end-to-end.
In demo mode the gateway clients short-circuit to a simulated response — the audit-log entry is real, the network call is not. That's enough to learn the shape and the gate, without touching the regulator.
You'll open the Submissions screen for the demo institution and inspect a previous (simulated) submission, then look at the audit-log entries the round-trip created.
Walkthrough
- Open submissions
1.Open the HESA submissions screen
See the simulated submission history for the demo institution.
- View detail
2.Inspect a submission
Open a previous submission to see the packet, the gateway acknowledgement, and the linked audit-log entries.
- Open audit log
3.Cross-check the audit log
Open the audit log and look for the matching submission entries — that's the evidence trail.
Your turn
Open the HESA submissions screen and see the demo institution's submission history.
Hint: Use the 'Open submissions' step above.