> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/enterprise/siemens-typer.md). # Siemens Typer Siemens Typer App for iOS and Android The Typer app provides the ability to transmit data to the the Siemens Typer USB device over Bluetooth Low Energy (BLE) protocol. Typer can be used as a standalone app, or it can be used with Keeper Password Manager to transmit information with one click. When the Typer device is plugged into the USB port of a computer, it behaves as a keyboard device. Pairing can be completed by performing a QR code scan via the camera of the device, or by manual entry of the device MAC address. When Typer is installed on the same device as Keeper Password Manager, a new menu item is displayed in the Keeper record called "Share to Typer". Tap on the "Share to Typer" menu item, then select which field to send. After the user selects the fields they want to send, Keeper will open the Typer app and transmit those fields via its "Text to Send" text editor. The Typer app will then pair to the Siemens BLE Typer peripheral and send the text to the peripheral. ### Installation #### Google Play * #### iOS * {% hint style="info" %} If you are interested in purchasing a Siemens Typer device, please contact **** {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.keeper.io/release-notes/enterprise/siemens-typer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.