Postman Setup Docs

[emilkovacev]

Proposed changes

---

Postman is an invaluable resource for new developers on this api. Having a pre-configured json file for postman will allow developers to understand exactly what a request looks like, and how they can make that request. Another option would be to host that json config file somewhere in this repo, so that we can make updates as we develop new endpoints.

Types of changes

---

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

---

• My changeset covers only what is described above (no extraneous changes)
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged downstream

Further comments

---

N/A

[jessehartloff]

Looks good. More documentation is always a good thing