Skip to content
CodeKruPro

Export a reusable collection without secrets

Automation taskMediumAsked in: Capgemini, Infosys

"How do you share collections safely and run them in CI?" You finish this lesson with an exported collection that holds no passwords or tokens, and you check the file yourself.

Export a reusable collection without secrets

05 · Check permissions and share the collection

Recommended first: Check effective headers and inherited authentication

Your goal: Export a reusable collection without secrets

Follow one request at a time. Send it yourself, then select that response before you answer.

  1. 1Send requests
  2. 2Submit answers

Start here: sign in to practise.

Jump to practice

What you will learn

Finish the same Postman collection you started earlier. A useful handoff lets another person configure the base URL and their own credentials. A fresh import tests whether the saved artifact is reusable.

Your goals

  • Rebuild a known request without relying on a saved secret.
  • Choose what is safe to share.

Before you start

Read the previous lesson first if you have not already. This course does not require programming.

Practice setup

These requests use the public TestKru teaching API. No workspace is needed unless a step says so. Leave the body empty for GET, HEAD and OPTIONS. Example people and emails are fictional. Changes to /api/users are simulated and are not saved.

Follow these steps

  1. Make a sharing copy of Beginner API Lab in Postman. Keep baseUrl, userId and the {{practiceToken}} auth placeholder; clear practiceToken and any password/key values. Delete saved login response examples that contain tokens.
  2. Export the sharing copy as Collection v2.1 JSON. Open it as text and inspect variable values, headers, auth fields, request bodies and saved response examples. Remove secrets before pasting it here.
  3. Import the exported file as a new collection. Without changing its saved public requests, send known user 1 and missing user 99. Confirm the resolved addresses; if a variable is missing, repair the sharing copy and export again.
  4. Repeat those two public requests in this console and select both responses. The import exercise is self-reviewed; the export structure and console results are automatically checked.
  5. Paste the sharing export, answer what belongs in a handoff, and submit. Keep the clean file for your portfolio.

Investigate before concluding

First record the actual result for each case. Compare the body, headers and later state with the stated contract. Keep an observation separate from a prediction; use the model answer only after making your own attempt.

What to keep as evidence

  • The known user and the missing user both work.
  • Shared material has no real secret.
  • Another person could tell what to fill in.
References for this lesson

Finish this assignment

Select each named response with Use this response. Answer from those responses or the transcript on this page. Click Submit Answers. Your score is the percentage of checks that passed. Core checks are required to finish. Extra evidence checks are labelled. A saved 100/100 means every check passed. Continue opens the next lesson you can submit.

If something goes wrong
  • Change one part of the request at a time. If a check needs attention, read the note under it and compare it with the response you selected.
Self-review and independent variation
  • The known user and the missing user both work.
  • Shared material has no real secret.
  • Another person could tell what to fill in.

Run the missing-user request after a fresh import and confirm the address is still configurable.

Automatic checks verify the requests and answers configured for this lesson. The self-review is for your own reasoning. A score is not a certificate.

Open API reference

Practise and save your evidence

The lesson is public. Sign in to send requests and save progress. You will return to this lesson.

Sign in to practiseCreate an account