Developer resources

Are you a developer and want to integrate xBand into your project? Or are you working on something innovative that could benefit from a vibration-based interface?
xBand offers several integration paths, from our CocoaPod and Swift package for iOS, to the HTTP API and Webhooks for platform-independent server communication. Whether you’re building custom workflows, experimenting with new types of haptic feedback, or exploring entirely new interaction models, xBand gives you the tools to extend and adapt the device to your own ideas.
If you’re interested in deeper collaboration, partnerships, or custom integrations, we’re always happy to talk. Let’s build something exciting together.
xBand Integration for iOS
We provide a lightweight iOS integration library for managing wireless communication between the xBand device and an iOS app.
It handles connection and sending vibration messages to an xBand. The framework supports sending Morse code messages and custom vibration patterns, as well as methods tailored for navigation and directional feedback.
Installation with CocoaPods
Add pod 'xBandConnectIOS' to your Podfile.
Installation with Package Manager
Add xBandConnectIOS as a Package Dependency by using the following URL in your package manager:
https://gitlab.com/xtactor/public/swift-packages/xBandConnectIOS
Example Project
A demo application is available to help you get started with xBand integration. It showcases key functions such as connection and vibration control. The demo app requires a physical iOS device (not supported in simulator).
The example project uses xBandConnectIOS as a CocoaPod. If you want to use the package instead, simply remove xBandConnectIOS from the podfile and add the package dependency instead.
GitLab – xBandConnectIOSExample
Key Features of the Library
- Connection management: Monitor connection and automatically connect to any nearby xBand.
- Vibration output: Send standard Morse code or create custom low-level motor patterns.
-
Navigation: Tells xBand to vibrate based on an angle and distance to a navigation target. The navigation vibration patterns are pre-configured on the xBand device. If you want to know more about the preconfigured navigation vibration patterns, contact us.
- Battery and firmware monitoring: Read device info like battery level or firmware version using built-in callbacks.
Licensing
This library is released under the MIT License. See the LICENSE file in the repository for details.
xBand HTTP API & Webhooks
The xBand HTTP API allows you to integrate xBand into your own systems using simple web requests. It provides a platform-independent way to send vibration messages to an xBand device and receive button commands or Morse messages from the device through Webhooks.
With the HTTP API you can trigger Morse messages or low-level motor signals. You can also capture incoming commands from the band and use them to drive actions in your own application or service.
Sending Messages to xBand
Send vibration messages by making a standard HTTP GET request to our endpoint:
https://xtactor.io/api/v1/text-to-xband?apiSecret={apiSecret}&message={message}
You can find your API-secret in the app.
Messages are converted to vibrations in Morse code on the xBand device. For custom vibration messages with low-level motor control, special characters (<, >, #, |) can be used in the message to activate specific vibration motors or pauses.
Receiving Messages from xBand (Webhooks)
To receive commands from xBand, configure a Webhook URL in the xBand app.
When triggered, the app will send a GET request to your server containing:
- apiSecret (for validation)
- message
- Text (interpreted from Morse code button presses), if the band is in Morse mode.
- The number of button presses that initiated the HTTP API button command, if the band is in Watch Mode.
You can trigger outbound messages using:
Morse Mode: write "w {message}" in Morse code
Watch Mode: assign HTTP API to a button command (the number of presses becomes the message)
Example Server
A simple Spring Boot project is available to help you get started with Webhook handling, response logic, and also shows some example integrations like sending messages between two xBand devices and external integrations.
GitLab – xBand HTTP Server Example
Key Features of the HTTP API
- Two-way communication: Send vibration messages and receive commands from xBand.
- Custom vibration patterns: Use text-based patterns (vibrated in Morse), or low-level motor signals.
-
Webhook support: Build event-driven integrations.
- Platform independence: Works with any language, framework, or environment that supports HTTPS.
- Secure communication: All traffic validated with your apiSecret and always sent over HTTPS.
When to Use the HTTP API
- You want to integrate xBand into a backend system.
- You want to build custom commands, alerts, automation, or cross-device messaging.
- You’re exploring advanced or experimental use cases such as IoT triggers, Discord bots, home automation, or cloud-based workflows.
Partnerships and custom integrations
We’re always open to new ideas and partnerships. Whether you're developing an app, creating an accessibility tool, building a navigation solution, or exploring entirely new use cases.
We can support:
- Custom integrations or prototyping
- Research collaborations
- Accessibility or navigation-focused solutions
- Developer guidance and technical support
- Early access to firmware or APIs
If you want to explore what’s possible together, please reach out to us at team@xtactor.com.