Platform

Run Grasshopper definitions from your own code

Everything ShapeDiver does is available to your own code. Three APIs cover computing a model, managing your models and users, and rendering in the browser; SDKs wrap them in the language you work in; and a set of ready-made integrations connects ShapeDiver to platforms such as Shopify and Speckle. This page is the map - the docs have the detail.

SDKs for TypeScript, .NET, Python, and PHP.

Diagram: your Grasshopper definition runs on the ShapeDiver platform (Geometry Backend and Platform Backend); your app connects through the Viewer API, the SDKs, and the integrations

Three APIs

One for computing, one for managing, one for rendering

API reference

ShapeDiver exposes three APIs, each for a different job:

Compute

Geometry Backend API

The compute engine. Send parameters, run the model, and get back geometry, data, and file exports - the raw computation, without a UI.

Geometry Backend

Manage

Platform Backend API

Where your models and users are managed: upload and organize models, and handle accounts and access. It’s the account side of the platform, in code.

Platform Backend

Render

Viewer API

Drives the ShapeDiver Viewer in the browser - load a model, set parameters, read outputs, and control the scene and camera. Covered in full on the 3D Viewer page.

3D Viewer

SDKs in your language

Work in the language you already use

You don’t have to call the APIs by hand. ShapeDiver publishes SDKs for TypeScript, .NET, Python, and PHP, so you can drive a model, manage your workspace, or wire ShapeDiver into a backend service, with the request-shaping and authentication handled for you.

SDK

TypeScript

SDK

.NET

SDK

Python

SDK

PHP

Integrations

Connect the tools you already run

Integrations in the docs

Alongside the APIs, ShapeDiver has ready-made integrations for common platforms, so a lot of the connecting is already done:

E-commerce

Put a configurator on your storefront and carry the configuration and production files into the order.

Industry

  • iJewel3D

iJewel3D for jewelry workflows.

Desktop connectors

Connectors for Rhino and Grasshopper link those desktop tools to ShapeDiver, and blueprints show how to build one for your own desktop application.

Where these fit

How the pieces line up

The three APIs map onto how an app comes together: the Geometry Backend computes the model the platform hosts; the Platform Backend manages the models and workspaces you keep there; and the Viewer API renders and drives the result in the browser. App Builder and a custom front end both sit on top of these - one no-code, one in code. And if you’d rather your AI coding agent did the wiring, the Agent Skills already know these APIs.

Diagram: the stack from the Grasshopper plug-in to your users, with the Geometry Backend API on the platform layer, the Platform Backend API on the workspace layer and the Viewer API on the 3D viewer layer

From the blog

Integrations and APIs, shown in webinars

All product updates

APIs, SDKs & Integrations

Build ShapeDiver into your stack

Start a free trial and connect a model to your own code - or talk to us if you’d like help scoping an integration. The API reference, SDKs, and integration guides are all in the docs.

Talk to our team

Your Business

How can we help?