What a completion record looks like

Every learner gets one when they finish. This is a sample.

Sample

Completion record

Name
Sample learner
Course
Bruno Foundations — test a shop's order API with Bruno, from your first request to a whole collection that passes
Completed
8 November 2026
Project
View the dashboard →
Skills demonstrated
Installing an API client and creating a collection saved as plain files · Sending GET and POST requests with query parameters, headers and a JSON body, and reading the response · Using environments and variables to send the same requests to different targets · Keeping a secret out of a collection's files · Sending a key as Bearer authorisation, and testing that a request with no key is refused · Writing assertions and JavaScript test scripts, and reading their results · Writing a check that fails for the right reason before it passes · Passing a value from one response into the next request · Running a whole collection in the Collection Runner · Reading a collection as its files on disk

What was built

A Bruno collection, Kestrel Shop API, for an invented bike-parts shop: five requests to a public echo service, two environments, a secret key, assertions and test scripts, an order number carried from one response to the next request, and a run of the whole collection with every request passing, saved as plain files on your own computer. Then a second collection for an invented tea shop, from briefs.

The 6 sessions, and when each was completed on their own

Session 1Install Bruno and send your first request4 October 2026
Session 2Send an order, and read what was sent11 October 2026
Session 3Two environments and a secret18 October 2026
Session 4A key, a refusal, and checks that can fail25 October 2026
Session 5Test scripts, and one answer feeding the next request1 November 2026
Session 6Run the whole collection, and see it as files8 November 2026

Each session was completed twice: once with step-by-step guidance on one company’s data, then on a second company’s data from a brief, with guidance only when asked. Every check passed on both. Alongrail records the sessions, the checks and the dates; the dashboard itself is the learner’s own, hosted where they chose.

The record is a description of work you did, not a claim about you. Anyone who opens it can see the work for themselves. It stays private until you publish it, and you can unpublish it at any time.

The name, the course, the date, the skills and the link to the dashboard: that is the whole of it. Nothing on it is about you that you didn’t do.