canonical: https://jentic.com/apis/dimescheduler.com/dimescheduler # Dime.Scheduler API Dime.Scheduler is a resource-planning and scheduling platform commonly paired with Dynamics 365 Business Central and NAV. The published OpenAPI surface in this version exposes a single token-issuance endpoint that exchanges an API key for a short-lived bearer token used by the broader Dime.Scheduler integration. Customers automate the auth handshake from build pipelines, integration middleware, and AI agents that subsequently call Dime.Scheduler's wider scheduling functions. ## For AI 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. ## Scope Does not currently expose job, resource, appointment, or notification operations in this OpenAPI surface - use for exchanging an API key for a bearer token only. ## Capabilities - 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 ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance and never enters the agent's context. Subsequent scheduling calls reuse the bearer until it expires. Example prompt: Search Jentic for 'authenticate Dime.Scheduler', load the /token operation schema, and execute it to obtain a bearer token for downstream scheduling calls. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/token` | Exchange an API key for a short-lived bearer token | ## Key resources - **Authentication** — Exchange an API key for a bearer token used by the Dime.Scheduler API ## Why Jentic - **Setup:** Wiring Dime.Scheduler by hand means exchanging its API key for a bearer token and managing that token's lifetime yourself. Through Jentic you install once, import the Dime.Scheduler API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** This Dime.Scheduler surface exposes only the token-exchange operation, so scope your agent to that single operation. You choose the operations it may call, so nothing beyond minting a bearer token is included unless the directory exposes and you add more. - **Credential handling:** Your Dime.Scheduler API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'authenticate to Dime.Scheduler', and Jentic returns the token operation with its input schema so the agent runs the auth bootstrap without browsing the reference docs. ## Related APIs - **Calendly** — Self-service appointment scheduling for individuals and teams - **Nylas** — Calendar, email, and contacts API across providers - **ServiceNow** — ITSM and workflow platform with field-service modules ## FAQ ### 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 your Jentic One instance 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. ### Can I limit what my agent is allowed to do with the Dime.Scheduler API? Yes. Because you run your own self-hosted Jentic One instance, your rules decide which operations and credentials the agent may use. This Dime.Scheduler surface exposes only the token-exchange operation, so you can scope the agent to just POST /token and nothing else. The API key stays in your instance and is injected at execution time, so the agent can mint a bearer token without ever seeing the secret.