SDKs
SDKs for integrations against the legacy API (Java, C#/.NET, PHP, Python, C++)
The SDKs on this page target the legacy agrirouter API only (MQTT and REST with protobuf envelopes). They do not work against the current API.
The current API is a small REST+SSE surface, meant to be consumed directly or through a client generated from the OpenAPI specification with a code-generation tool from your language's ecosystem. Thin SDKs for the current API may show up later. None exist today.
The SDKs below are for partners maintaining integrations against the legacy API. For context on which API surface they cover, see the Legacy API reference and the migration guide.
Available SDKs
| Language | Status | Repository |
|---|---|---|
| Java | Official | agrirouter-sdk-java |
| C# / .NET | Official | agrirouter-sdk-dotnet-standard |
| PHP | Official | agrirouter-sdk-php |
| Python | Official | agrirouter-sdk-python |
| C++ | Community (3rd party) | agrirouter-sdk-cpp |
Feature coverage differs between SDKs. If something is missing, open a pull request or reach out to DKE Data.
Choosing an SDK
Pick the SDK that matches your stack. All official SDKs cover the core legacy-API workflows: onboarding, capability management, sending messages, and retrieving them. The C++ SDK is maintained by a third party and is not officially supported by DKE Data.
Using the Current API Without an SDK
For the current API, generate a client from the OpenAPI specification with a tool from your language's ecosystem (for example, openapi-generator or oapi-codegen). The current API is a small REST surface (four endpoints plus an SSE stream), so partners often skip the generator entirely and hit it directly with the standard HTTP client from their language.