# Overview

The LaunchBrightly Product Screenshots API is uniquely focused on capturing screenshots from password-gated Web Applications for use in your knowledge-base articles. This includes features like:

- Set up a login profile for your Demo Account (username/password)
- Render the page in any mode such as Light/Dark, Mobile/Desktop, US/DE/FR etc.
- [Remove unwanted elements](https://docs.launchbrightly.com/product-screenshots-api/remove-elements) from the page before capturing a screenshot
- [Execute automated input actions](https://docs.launchbrightly.com/product-screenshots-api/execute-actions) before the screenshot is captured to set up a specific state
- [Capture a screenshot](https://docs.launchbrightly.com/product-screenshots-api/capture-screenshot) of a section of the page using Selectors (or custom `data-lb` attributes)
- [Style the output image](https://docs.launchbrightly.com/product-screenshots-api/style-image) according to your brand guidelines
- [Annotate images](https://docs.launchbrightly.com/product-screenshots-api/annotate-image) with text, shapes, arrows etc. so you can speak to specific parts
- Request screenshots in bulk and [save them directly to your cloud](https://docs.launchbrightly.com/product-screenshots-api/export-screenshots)

For every accepted field and default, see the full [Screenshot API reference](https://docs.launchbrightly.com/product-screenshots-api/options).

The API is designed and built in conjunction with the [Help Center Sync API](https://docs.launchbrightly.com/help-center-sync-api/overview) and we try by choice to make them complement each other. These two APIs are also the foundation for our [screenshot automation platform](/content/site-root.html) for customer support teams.

The API is organized around [REST](http://en.wikipedia.org/wiki/Representational_State_Transfer). Our API has predictable resource-oriented URLs, accepts [JSON-encoded](http://www.json.org/) request bodies, returns [JSON-encoded](http://www.json.org/) responses, and uses the well-recognized header convention `x-api-key` for passing your API key. All properties on our endpoints are case-insensitive. We try hard to use standard [HTTP response codes](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status) and verbs.

## Supported Application types

- Ungated Web Application
- Password-gated Web Applications
- Token-based authentication Web Applications (request access)
- Native Applications (on the roadmap)