What you are testing
You will create a fictional customer and read the same customer back. This API really stores customer records. A creation response alone is not proof that the record was saved.
1. Set up your practice data
Click Create workspace. A workspace is your own set of practice records, separate from other learners. When it says Workspace ready, move to the request guide. You do not need to install a database. Keep this workspace until you finish checking.
2. Follow the three request steps
- Log in as A: the prepared POST sends
{"username":"a","password":"practice-a"}tohttps://testkru.com/api/manual/v1/auth/login. Click Send request. Expect 200. Copy thetokenvalue from the body, without quotation marks. - Create a customer: click Next request step and paste that value into A's login token. Click Prepare this request. It fills the POST URL and Authorization header, and leaves the body empty. Add
"Content-Type":"application/json"to Headers and type a body with your own fictional name and new email, for example{"name":"Learner One","email":"learner.one@example.test"}. Inspect the fields, then send. Expect 201. Click Use this response to select the create evidence. Copy the returnedid. - Read the customer: go to the next request step and paste that exact ID. Prepare and send the GET. Expect 200. Compare its id, name and email with the POST response. Click Use this response to select the read-back evidence.
What the request fields mean
POST sends data, such as a login or a new customer. GET reads data. Request body is the JSON you send; response body is what the API replies with. JSON uses quoted field names and values, for example {"name":"Learner One","email":"learner.one@example.test"}.
Content-Type: application/json tells the API your request body is JSON. Authorization: Bearer TOKEN tells it you are acting as A. For creation, Prepare adds Authorization using your token. You add Content-Type and type the customer JSON yourself; inspect both headers before sending. This practice login is separate from your CodeKru account. Do not paste your CodeKru sign-in token.
3. Review evidence and submit
You need two selected requests: the customer POST with 201, and the later GET of that same customer with 200. The login is preparation and is not one of these two. Inspect both selected responses in step 3, enter the created customer ID again as your observed answer, and choose what the read-back established. Click Submit Answers.
When all checks pass, the score is 100/100 and your result is saved. Click Continue to the next lesson. If a check needs attention, correct or replace the selected evidence and check again. Do not reset or delete the customer before checking: its stored state is also verified.
If something goes wrong
401: log in again and paste the fresh token. Tokens last 15 minutes and reset invalidates them. 409 on POST: that email already exists; edit the body to use a new fictional email and retry. Select the new successful POST and read its new ID. 404 on GET: check the ID and that you are using A's token. Reloading clears the guide's working tokens and IDs; your saved evidence and answers remain available.
API rules
Name is trimmed and must contain 1–80 Unicode code points. Email is trimmed, lowercased and unique in your workspace. Optional age is an integer from 18 through 120. Unknown fields are rejected. A duplicate email returns 409 without creating another customer.
Optional self-review
Why is a GET after POST useful? What would 201 followed by 404 mean for an API that promises to save records? No written self-review is required to continue.