It looks like you are coming from United States, but the current site you have selected to visit is Indonesia. Do you want to change sites?

Yes, please. No. Keep me on the current site.

Integrate with HYPACK

HYPACK's SDK enables approved integrations between external systems, sensors, workflows, and partner solutions and supported HYPACK products. It's built to support productive integration work while keeping product security, quality, and support expectations clear on both sides. The SDK package is not available for public download. Access is granted on request.

Shutterstock 2321529777 | Web

Who should use our SDK?

  • Customers building an integration for their own use
  • Hardware or software partners integrating with HYPACK workflows
  • Developers working on behalf of a customer or partner

What the SDK includes

  • Documentation
  • Interface definitions and APIs
  • Sample projects and reference code
  • Driver development guidance, where applicable
  • Version and compatibility notes

Requesting access

Submit a request using the form linked below, including:

  • Your name and company or organization
  • The sensor, device, or integration you're developing
  • Intended use (internal use, commercial distribution, etc.)

 Request SDK Access

What you should know

Use of the SDK, and of anything you build with it, is governed by the HYPACK SDK License Agreement. By downloading or using the SDK, you agree to its terms. Key points:

  • You own what you build with the SDK. HYPACK retains ownership of the SDK itself and of any HYPACK code embedded in your driver or integration.
  • Distributing what you build to other HYPACK customers is permitted only if you disclose that it's third-party software, not developed or supported by HYPACK.
  • Selling or commercially bundling what you build — for example, with hardware — requires a separate written agreement with HYPACK.
  • SDK materials may not be used to train or fine-tune AI or machine learning systems.

*Requests are reviewed for legitimacy, fit, and support implications. Access may be denied or deferred if the request lacks a clear use case, seeks unrestricted redistribution of protected materials, or would create unreasonable support, legal, or security risk. Having a HYPACK license or maintenance plan does not by itself entitle a party to SDK access.