Dime.Scheduler API

Name: Dime.Scheduler API
Brand: Dime.Scheduler API
Availability: InStock

✓ Official Vendor SpecProductivityCalendar SchedulingapiKey, bearer1 EndpointsREST

For Agents

Authenticate against Dime.Scheduler by exchanging an API key for a short-lived bearer token. Required as the first call before any downstream scheduling integration with Dime.Scheduler.

Install Jentic One Beta

Connect the Dime.Scheduler API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dime.Scheduler API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Dime.Scheduler API.

Exchange a Dime.Scheduler API key for a short-lived bearer token via POST /token

Bootstrap automated integrations with Dime.Scheduler that require bearer authentication on subsequent calls

Refresh authentication credentials in scheduled CI or middleware jobs without manual user login

GET STARTED

Start building with Dime.Scheduler API

Explore with Jentic

View OpenAPI Document

★ Bootstrapping a Dime.Scheduler Integration

Integration developers building connectors between Dime.Scheduler and Business Central, NAV, or custom field-service apps need to obtain a bearer token before calling any of the platform's scheduling operations. POST /token exchanges a long-lived API key for a short-lived bearer that the rest of the integration uses. Centralising this exchange in one helper avoids leaking the API key into downstream services.

POST /token with the Dime.Scheduler API key and store the returned bearer token in memory for use by the downstream scheduler client.

Scheduled CI Token Refresh for Middleware

Middleware that synchronises jobs and resources between an ERP and Dime.Scheduler typically runs on a schedule and needs valid bearer tokens for each run. A scheduled CI step calls POST /token to fetch a fresh token, writes it into the integration's secret store, and the synchronisation job consumes it. This pattern keeps the API key in a CI vault and limits bearer token exposure.

Call POST /token in a nightly CI job, store the returned bearer in the secret manager, and trigger the downstream Business Central sync.

Validating Dime.Scheduler Credentials

Operations teams can use the /token endpoint as a lightweight health check that an issued API key is still valid and the Dime.Scheduler tenant is reachable. A non-200 response signals either an expired key or an environment outage, allowing alerting before users notice scheduling failures.

Call POST /token with the production API key and alert if the response status is not 200.

AI Agent Token Bootstrap for Scheduling Workflows

AI agents orchestrating downstream Dime.Scheduler scheduling operations need a fresh bearer token to make authenticated calls. Through Jentic, the agent calls the /token operation as the first step of a workflow; the API key is held in MAXsystem and never enters the agent's context. Subsequent scheduling calls reuse the bearer until it expires.

Search Jentic for 'authenticate Dime.Scheduler', load the /token operation schema, and execute it to obtain a bearer token for downstream scheduling calls.

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Dime.Scheduler API key is stored encrypted in Jentic's MAXsystem vault. Agents call POST /token through Jentic, which returns the bearer token in the response without the raw key ever being exposed to the agent.

Intent-based discovery

Agents search by intent (e.g., 'authenticate Dime.Scheduler') and Jentic returns the /token operation with its input schema, so the agent runs the auth bootstrap without browsing the partner documentation.

Time to first call

Direct Dime.Scheduler auth setup: a few hours including key handling and bearer caching. Through Jentic: under 15 minutes — search, load, execute the /token operation.

FAQs

Specific to using Dime.Scheduler API through Jentic.

What authentication does the Dime.Scheduler API use?

The published surface uses an API key sent to POST /token, which returns a bearer token used to authorise subsequent calls. Through Jentic, the API key is held in the MAXsystem vault and the bearer token is fetched at execution time, so neither secret enters the agent's context.

Can I exchange my API key for a bearer token with the Dime.Scheduler API?

Yes, this is the only operation in this version of the spec. POST /token with your API key and Dime.Scheduler returns a short-lived bearer token. Use that token on subsequent calls into the wider Dime.Scheduler integration.

What are the rate limits for the Dime.Scheduler API?

Rate limits for the token endpoint are not published in the OpenAPI spec. In practice, /token is called infrequently (once per session or scheduled job), so it is rare to hit limits. Confirm with the Dime.Scheduler operations team if you plan high-volume token issuance.

How do I bootstrap a Dime.Scheduler integration through Jentic?

Search Jentic for 'authenticate Dime.Scheduler', load the schema for POST /token, and execute it with your stored API key. Jentic returns the bearer token from the response body, which downstream scheduling calls can then use.

Does this spec cover Dime.Scheduler's scheduling endpoints?

The published spec in this version exposes only the /token authentication operation. Scheduling, resource, and job operations are documented by Dime.Scheduler separately and are not part of this OpenAPI surface. Use /token to obtain a bearer, then call those operations using the broader Dime.Scheduler documentation.

Dime.Scheduler API

Connect the Dime.Scheduler API to your agent

Capabilities

Start building with Dime.Scheduler API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs