How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Nedap Arrangement.Intent API

The arrangement.Intent API from Nedap — 10 operation(s) for arrangement.intent.

Nedap Arrangement.Intent API is one of 269 APIs that Nedap publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 14 operations across 10 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 0.0.0.

Requests are made against a single base URL, https://api-development.ons.io.

14 operations 10 paths 4 schemas 4 DELETE4 GET2 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.0
Base URL
https://api.ons.io
Resource Areas
1

Paths & Operations 14

Across 10 paths, the API surfaces 14 operations — 4 DELETE, 4 GET, 2 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

arrangement.Intent 14
POST
/t/arrangement/intentsdeprecated
Create Intent
arrangement.IntentAPI.create body → 200
PUT
/t/arrangement/intents/{uuid}deprecated
Updates the given Intent
arrangement.IntentAPI.update 1 param body → 200400403404
DELETE
/t/arrangement/intents/{uuid}deprecated
Deletes the Intent with given uuid
arrangement.IntentAPI.delete 1 param → 200403404
GET
/t/arrangement/intents/by_client_period_plannable/{client_id}deprecated
Gets all intents for a Client in a given period and whether they are plannable
arrangement.IntentAPI.byClientInPeriodPlannable 4 params → 200
GET
/t/arrangement/intents/by_employee/{employee_id}deprecated
Gets all intents for an Employee
arrangement.IntentAPI.byEmployeeId 5 params → 200
PUT
/t/arrangement/intents/by_timeline/{timeline_uuid}deprecated
Updates all intents for a timeline identified by a UUID
arrangement.IntentAPI.createOrUpdateTimeline 1 param body → 200400403404
DELETE
/t/arrangement/intents/by_timeline/{timeline_uuid}deprecated
Deletes all intents for a timeline identified by a UUID
arrangement.IntentAPI.deleteTimeline 1 param → 204400403404
POST
/v0/administration/arrangement/intentsdeprecated
Create Intent
postV0AdministrationArrangementIntents body → 200
PUT
/v0/administration/arrangement/intents/{uuid}deprecated
Updates the given Intent
putV0AdministrationArrangementIntentsByUuid 1 param body → 200400403404
DELETE
/v0/administration/arrangement/intents/{uuid}deprecated
Deletes the Intent with given uuid
deleteV0AdministrationArrangementIntentsByUuid 1 param → 200403404
GET
/v0/administration/arrangement/intents/by_client_period_plannable/{client_id}
Gets all intents for a Client in a given period and whether they are plannable
getV0AdministrationArrangementIntentsByClientPeriodPlannableByClientId 4 params → 200
GET
/v0/administration/arrangement/intents/by_employee/{employee_id}
Gets all intents for an Employee
getV0AdministrationArrangementIntentsByEmployeeByEmployeeId 5 params → 200
PUT
/v0/administration/arrangement/intents/by_timeline/{timeline_uuid}
Updates all intents for a timeline identified by a UUID
putV0AdministrationArrangementIntentsByTimelineByTimelineUuid 1 param body → 200400403404
DELETE
/v0/administration/arrangement/intents/by_timeline/{timeline_uuid}
Deletes all intents for a timeline identified by a UUID
deleteV0AdministrationArrangementIntentsByTimelineByTimelineUuid 1 param → 204400403404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are arrangement.Intent (19 properties), arrangement.list.IntentList (1 property). Each schema is shown below with its type and property counts.

arrangement.QuantityUnit
string
The Intent's quantity unit, for example MINUTE or HOUR. In combination with the quantity amount, it determines the quantity of th the care that is intended. Fo…
arrangement.RecurrenceType
string
Together with the recurrence interval, the recurrence type determines how the intent is repeated over time. Examples: - 1, WEEK corresponds to 'every week' - 2…
arrangement.list.IntentList
object
IntentList model (no description)
1 property
arrangement.Intent
object
Intent of the preference
19 properties 12 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nedap-arrangement-intent-api-openapi.yml Raw ↑

Other APIs Nedap publishes across the network.

Nedap Retail iD Cloud API
Nedap Address API
Nedap Admin.Background Image API
Nedap Admin.License API
Nedap Admin.Logo Image API
Nedap Admin.Timesheet Config API
Nedap Admin.Version API
Nedap Agbcode API
Nedap Agenda.Agenda Occurrence API
Nedap Agenda.Agenda Series API
Nedap Agenda.Client Absence Occurrence API
Nedap Agenda.Label API
Where this information came from

This is an independent, third-party profile of Nedap Arrangement.Intent API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.