- Go into the Markdown Source Code to get the actual formatting
- Only contribute if you actually know what you are doing and talking about on the API / Operation
- If you modify multiple files dont make a commit for each file, rather for each service
- Good Naming for PRs, Issues, Commits... (NOT modified file.md, say what you want / changed)
- Markdown formatting (Visual Studio Code)
- Include an example response (shortened)
{optional_description}
URL: {URL}
Method: {Method}
Auth Required: {Yes/No} ({Permission})
<key>
: <description>
[JSON Code Block] [if required]
<Body>
<key>
: <description>
<key>
: <description>
<key>
: <description>
---
Horizontal Line
*Example Response*
[JSON] Codeblock / Note which Status to expect if no content is returned
{
"hello": "world"
}
Description: {description}
Profiles: {profile_id_1}
, {profile_id_2}
[JS Code Block]
{
"{property_name}": "{example_value}" // {property_description}
}
[Property Description]:
- 1 Space after the Comment Start
- Dont use all LowerCase e.g. "item guid" -> "Item GUID"
- If its an enum, then include all possible values