### Installing Node.js Dependencies for TradeStation API Docs - Shell

Source: https://github.com/tradestation/api-docs/blob/master/README.md

This command installs all necessary Node.js dependencies for the TradeStation API documentation project. It should be run after cloning the repository to set up the development environment, ensuring all required packages are available.

```Shell
npm install
```

--------------------------------

### Starting Local Development Server for TradeStation API Docs - Shell

Source: https://github.com/tradestation/api-docs/blob/master/README.md

This command initiates a local development server, allowing real-time preview of documentation changes. It automatically refreshes the browser upon modifications to the OpenAPI specification, facilitating an efficient development workflow.

```Shell
npm start
```

--------------------------------

### Basic Body Styling in CSS

Source: https://github.com/tradestation/api-docs/blob/master/web/index.html

This CSS snippet applies basic styling to the HTML body element, setting both the margin and padding to zero. This is commonly used to remove default browser spacing around the page content, ensuring the content starts at the very edge of the viewport.

```CSS
body { margin: 0; padding: 0; }
```

--------------------------------

### Running Tests for TradeStation API Docs - Shell

Source: https://github.com/tradestation/api-docs/blob/master/README.md

This command executes the test suite for the TradeStation API documentation project. It should be run after making changes to ensure the documentation is valid, consistent, and adheres to the specified guidelines before pushing to GitHub.

```Shell
npm test
```

--------------------------------

### Dumping API Payloads with Shell Scripts

Source: https://github.com/tradestation/api-docs/blob/master/CONTRIBUTING.md

This snippet demonstrates how to use the `api.sh` and `dump.sh` shell scripts to generate YAML schemas for API payloads. It pipes the output of `api.sh` (which presumably fetches data from a specified API endpoint) into `dump.sh` (which then processes it into a YAML format suitable for Swagger definitions).

```shell
cd scripts
./api.sh /data/quote/amzn | ./dump.sh
```

--------------------------------

### Defining and Referencing Global Headers in OpenAPI/Swagger (YAML)

Source: https://github.com/tradestation/api-docs/blob/master/spec/README.md

This snippet demonstrates how to define a reusable header, 'Rate-Limit-Limit', in a global 'headers' section and then reference it within a specific path's response. This approach minimizes duplication and ensures consistency across the API specification, with the global reference being inlined during the build process.

```YAML
...
headers:
  Rate-Limit-Limit:
    description: The number of allowed requests in the current period
    type: integer
...
paths:
  /api-keys:
    get:
      summary: Retrieve a list of api keys
      responses:
        200:
          description: A list of api keys was retrieved successfully
          headers:
            Rate-Limit-Limit:
              $ref: "#/headers/Rate-Limit-Limit"
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.