Development

Among the heaps of configurable settings, there is also an abundance of options to interact programmatically with Dime.Scheduler. Whether you prefer raw HTTP, an SDK, the command line or a low-code connector — pick the entry point that fits your stack.

Developer Areas

API

The single uniform REST API to push data into Dime.Scheduler from any technology stack.

REST • JSON • OpenAPI • Authentication

SDKs

First-class .NET and JavaScript SDKs that wrap the API for a smooth developer experience.

.NET • JavaScript • TypeScript types

CLI

Command-line tooling for scripting, automation and CI workflows against Dime.Scheduler.

Cross-platform • Scripts • CI/CD

Connectors

Pre-built connectors for Business Central, NAV, Power Platform and Zapier as low-code alternatives.

BC • NAV • Power Platform • Zapier

Why one API?

Most of the data that is used in Dime.Scheduler is accessible through RESTful web API services. However, most of them were designed for internal use, and we intend to keep it that way — there is an alternative approach that is a one-stop shop to feed data into the planning tool: the Dime.Scheduler API.

The API has been designed as one uniform interface that allows you to insert, update or remove any kind of data the application uses. It is also a web service, which makes it accessible to a wide array of technologies and programming languages.

In fact, the API service is so essential that the plugins and development tools were built on it. The connectors for BC, NAV, CRM, Power Platform — they all rely heavily on the API. Same goes for the SDKs and CLIs: they are wrappers around the API to improve the development experience.