sz-sdk-json-type-definition
If you are beginning your journey with Senzing, please start with Senzing Quick Start guides.
You are in the Senzing Garage where projects are "tinkered" on. Although this GitHub repository may help you understand an approach to using Senzing, it's not considered to be "production ready" and is not considered to be part of the Senzing product. Heck, it may not even be appropriate for your application of Senzing!
⚠️ WARNING: sz-sdk-json-type-definition is still in development ⚠️ _
At the moment, this is "work-in-progress" with Semantic Versions of 0.n.x.
Although it can be reviewed and commented on,
the recommendation is not to use it yet.
Synopsis
The Senzing sz-sdk-json-type-definition uses JSON Type Definition
to model the JSON that is returned from Senzing SDK calls.
Code generated from this model improves compile-time type checking and code-completion in Integrated Development Environments (IDE) (e.g. "VSCode's IntelliSense").
Overview
By using the code generated by JSON Type Definition, JSON returned by the Senzing SDK calls are easier to parse. Examples:
- Python - main.py
- Go - main.go
- Java - Main.java
- Typescript - main.ts
- C-sharp Program.cs
The actual specification is senzingsdk-RFC8927.json.
From this specification, code is generated for the following languages:
Use
- Python comparison:
-
Here's how to parse a Senzing JSON response without
senzing-json:result = sz_engine.get_virtual_entity_by_record_id(record_keys, flags) feature_list = result.get("RESOLVED_ENTITY", {}).get("FEATURES", {}).get("NAME", [])
- Note that the JSON keys and datatypes of the values must be known ahead of time. Also, this method is subject to typographical errors.
-
Here's how to parse a Senzing JSON response with
senzing-json:result = sz_engine.get_virtual_entity_by_record_id(record_keys, flags) virtual_entity = SzEngineGetVirtualEntityByRecordIDResponse.from_json_data(result) feature_list = virtual_entity.resolved_entity.features["NAME"]
- When using an IDE, the fields and datatypes are supplied by the IDE's code-completion. Typos will be flagged by the IDE.
-
References
- Development
- Errors
- Examples
- Packages
Metadata
Release files for senzing-typedef 0.2.18
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| senzing_typedef-0.2.18.tar.gz | 7.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| senzing_typedef-0.2.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 MB
Release files / senzing_typedef-0.2.18.tar.gz
| Download URL | senzing_typedef-0.2.18.tar.gz |
|---|---|
| Size | 7.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
566527947ef3a9e83f3d99edb15bcad6405896d485dc67f9a99fb44c246dd756
|
|
BLAKE2b-256 checksum How to use checksums |
498b2ac9b98ab1cce7971facfc96f4c22b9f1f61b8012a20bc6297eae47f3ae4
|
| 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 Oct 20, 2025.
Transparency logRelease files / senzing_typedef-0.2.18-py3-none-any.whl
| Download URL | senzing_typedef-0.2.18-py3-none-any.whl |
|---|---|
| Size | 152.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d6e27071b4c93b74ff17c01e618b8525703713b15875420f5f07a07f6e650a5
|
|
BLAKE2b-256 checksum How to use checksums |
f2ed82f102d0d0328a33081987f021e2dd6a59d69ddd13c266ddfef023dc2a3f
|
| 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 Oct 20, 2025.
Transparency log