Seequent Developer Portal • Seequent Community • Seequent website
Evo Block Model API Client
The Block Model API provides the ability to manage and report on block models in your Evo workspaces. Enable your product with Evo connected workflows by integrating with the Seequent Block Model API.
The Block Model API supports a range of sub-blocking options, and both full and partial updates to block models, including updates of specified columns and/or sub-volumes. Block models are versioned, and the service supports reporting on the material content of current or previous versions, and comparing the content between versions of a block model.
Pre-requisites
- Python ^3.10
- An application registered in Bentley
Installation
pip install evo-blockmodels
Usage
See the evo-sdk-common documentation for information on how to authenticate, then select the organisation, hub and workspace that you would like to use.
Interacting with the Evo Block Model API
To get up and running quickly with the Evo Block Models SDK, start by configuring your environment and API connector.
from evo.blockmodels import BlockModelAPIClient
service_client = BlockModelAPIClient(environment, connector)
service_health = await service_client.get_service_health()
service_health.raise_for_status()
For some interactive Jupyter notebook examples, see the examples folder.
To run the notebooks in your browser:
uv run --all-groups jupyter notebook
Contributing
For instructions on contributing to the development of this library, please refer to the evo-python-sdk documentation.
License
The Python SDK for Evo is open source and licensed under the Apache 2.0 license..
Copyright © 2025 Bentley Systems, Incorporated.
Licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Metadata
Release files for evo-blockmodels 0.6.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 | |
|---|---|---|---|
| evo_blockmodels-0.6.0.tar.gz | 61.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| evo_blockmodels-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 150.4 kB
Release files / evo_blockmodels-0.6.0.tar.gz
| Download URL | evo_blockmodels-0.6.0.tar.gz |
|---|---|
| Size | 61.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb7ea4f8158f41e8571700403a96e129b9cede5c355873d5947e5d37c8c93162
|
|
BLAKE2b-256 checksum How to use checksums |
d2d765590f270b370287a5e528cf809a0972acb2f2b1cd77e957f2f8719c205d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 27, 2026.
Transparency logRelease files / evo_blockmodels-0.6.0-py3-none-any.whl
| Download URL | evo_blockmodels-0.6.0-py3-none-any.whl |
|---|---|
| Size | 88.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4add69a7d6e81d345f84e737bc2e728560401c862582ff3c5d7f764e6897d0a9
|
|
BLAKE2b-256 checksum How to use checksums |
8e8ee9eeb909a7d1dd933744daf148d1668d3b0530e27dc980d293cd61feedb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 27, 2026.
Transparency log