Skip to main content
Speckle provides SDKs — libraries that let you authenticate with Speckle Server, load and publish AEC data, and build integrations in the language that fits your project. Each SDK implements the same platform: projects, models, versions, objects and their relations, and the GraphQL API. The APIs differ; the concepts transfer.
How a version’s data is shaped is documented in Object model; language-specific setup lives under Python and .NET.
Updating a script written before 2026.9? See Migrate a .NET script or Migrate a Python script.

What are the Speckle SDKs?

The SDKs are how developers talk to Speckle outside the web app and desktop connectors. They let you:
  • Authenticate with Speckle Server
  • Create and query projects, models, and versions
  • Load and publish model data: objects, their properties, geometry, and relations
  • Filter, query, and process data in code
specklepy (Python) and Speckle.Sdk (.NET) are the production SDKs documented today. speckle.js (TypeScript) is in development — see speckle.js. Each SDK follows its language ecosystem (packaging, patterns, tooling). Platform behaviour is shared; examples and onboarding are language-specific.

Choosing an SDK

Pick the SDK that matches where your code runs, not a feature checklist.
Both SDKs can call the same server, read the same projects, and work with the same object model. If your team already uses Python or C#, start there.

Common platform concepts

These ideas are the same in every SDK. Learn the platform once; apply it in whichever language you use.

Learning paths

Python (specklepy)

Introduction

specklepy overview and repository

Installation

Install with pip

Quickstart

Publish and load your first model

Migrate to 2026.9

Move an operations.receive script to receive3

Guides

Task-oriented recipes

API Reference

Client, operations, resources

.NET (Speckle.Sdk)

Build your first model analysis tool

Load, traverse, export CSV — recommended start

Installation

Install with NuGet

Automate with scripts

Shortest path for scripts and Grasshopper C#

Publish and load a model

Optional deep dive — Send3, Receive3, and BundleBuilder

Migrate to 2026.9

Move a Receive2 script to Receive3

Guides

Task-oriented recipes

API reference

Method lookup after you have a working script

One platform, multiple SDKs

Speckle is one platform. Each SDK embraces the conventions of its language — import-and-go in Python, a one-time bootstrap in .NET for scripts — while exposing the same server resources and object model. Platform concepts (projects, models, versions, objects, properties, relations) transfer between SDKs. Code samples, bootstrap patterns, and API shapes stay language-specific. When a new SDK ships, it extends this shared model; you do not relearn what Speckle is.

FAQ

No. Read this page for orientation, then follow one learning path — Python or .NET — for installation, authentication, and examples.
Object model is language-agnostic. Data Schema covers versions published before 2026.9.
Yes. Both can target the same Speckle Server and projects. Choose the SDK per component (for example Python for analytics, .NET for a Revit connector).
Last modified on October 19, 2026