onshnap
onshnap exports Onshape assemblies as static URDF or MJCF files with STL meshes. Takes a frozen snapshot of the assembly and exports it as a fixed robot description file.
Specifically, it exports assemblies as static robot descriptions (no kinematic chains) with star topology (all parts connected to a single base_link via fixed joints).
It also supports exporting to MJCF if you want to do that for some reason.
Usage
First install the package:
pip install onshnap
Then set your Onshape API keys in your environment and run the export:
export ONSHAPE_ACCESS_KEY="your-access-key"
export ONSHAPE_SECRET_KEY="your-secret-key"
onshnap /path/to/directory/with/config
To find where to get your Onshape API keys, see the Onshape Help Center.
Configuration
The config.json should contain:
{
"url": "https://cad.onshape.com/documents/...",
"filetype": "urdf", // optional, defaults to "urdf"
"output_name": "onshnap", // optional, defaults to "onshnap"
"mesh_dir": "meshes", // optional, defaults to "meshes"
"units": "meter", // optional, defaults to "meter"
"create_centroid_links": true // optional, defaults to false
}
Configuration Options:
url(required): Onshape document URLfiletype(optional): Output format -"urdf"(default) or"mjcf"output_name(optional): Base name for output files (default:"onshnap")mesh_dir(optional): Subdirectory name for mesh files (default:"meshes")units(optional): Units for mesh export -"meter"(default) or"inch"create_centroid_links(optional): If True, create virtual links at center of mass (default:false)
Metadata
Release files for onshnap 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| onshnap-0.2.0.tar.gz | 19.8 kB | With provenance | Details |
Release files / onshnap-0.2.0.tar.gz
| Download URL | onshnap-0.2.0.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20dd3e3a0e318c4ce688af72aa1eb04d76dbff0af45daf4ded7ee410c70d28da
|
|
BLAKE2b-256 checksum How to use checksums |
e07338ec0762abccc088c653f27a6805d4a3bcda65bb081bcdd7cb99241d2531
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 10, 2026.
Transparency logSecurity for onshnap 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for onshnap-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 10, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.