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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Nedap

Nedap Dossier.Care Plan Entry API

The dossier.CarePlanEntry API from Nedap — 8 operation(s) for dossier.careplanentry.

Documentation Provider Profile APIs.io OpenAPI GitHub

Nedap Dossier.Care Plan Entry 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 12 operations across 8 paths, and defines 17 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.

12 operations 8 paths 17 schemas 2 DELETE4 GET4 POST2 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 12

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

dossier.CarePlanEntry 12
POST
/t/dossier/care_plan_entriesdeprecated
Create CarePlanEntry
dossier.CarePlanEntryAPI.create body → 200
GET
/t/dossier/care_plan_entries/{id}deprecated
Get a resource by its ID
dossier.CarePlanEntryAPI.byId 3 params → 200404
PUT
/t/dossier/care_plan_entries/{id}deprecated
Updates the given CarePlanEntry
dossier.CarePlanEntryAPI.update 3 params body → 200400
DELETE
/t/dossier/care_plan_entries/{id}deprecated
Deletes the CarePlanEntry with given id
dossier.CarePlanEntryAPI.delete 3 params → 204400
POST
/t/dossier/care_plan_entries/createdeprecated
Create a Care Plan Entry
dossier.CarePlanEntryAPI.createEntry 2 params body → 200400
GET
/t/dossier/care_plans/{care_plan_id}/care_plan_entriesdeprecated
Return the CarePlanEntries of a CarePlan corresponding to the given id
dossier.CarePlanEntryAPI.byCarePlanId 1 param → 200
POST
/v0/administration/dossier/care_plan_entries
Create CarePlanEntry
postV0AdministrationDossierCarePlanEntries body → 200
GET
/v0/administration/dossier/care_plan_entries/{id}
Get a resource by its ID
getV0AdministrationDossierCarePlanEntriesById 3 params → 200404
PUT
/v0/administration/dossier/care_plan_entries/{id}
Updates the given CarePlanEntry
putV0AdministrationDossierCarePlanEntriesById 3 params body → 200400
DELETE
/v0/administration/dossier/care_plan_entries/{id}
Deletes the CarePlanEntry with given id
deleteV0AdministrationDossierCarePlanEntriesById 3 params → 204400
POST
/v0/administration/dossier/care_plan_entries/createdeprecated
Create a Care Plan Entry
postV0AdministrationDossierCarePlanEntriesCreate 2 params body → 200400
GET
/v0/administration/dossier/care_plans/{care_plan_id}/entries
Return the CarePlanEntries of a CarePlan corresponding to the given id
getV0AdministrationDossierCarePlansByCarePlanIdEntries 1 param → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are survey.Question (13 properties), dossier.CarePlanEntry (11 properties), dossier.Action (11 properties), dossier.Goal (10 properties). Each schema is shown below with its type and property counts.

survey.AnswerDefinition
object
AnswerDefinition model (no description)
9 properties
survey.AnsweredQuestion
object
AnsweredQuestion model (no description)
1 property
survey.Question
object
Question model (no description)
13 properties
dossier.Goal
object
Zorgplan "doel"
10 properties
AuditedBase
object
AuditedBase model (no description)
3 properties
dossier.Action
object
Zorgplan "actie"
11 properties
dossier.CreateCarePlanEntry
object
@deprecated This class is deprecated, at the moment of writing this class there is no way in Cupido to create a model that depends on creations of other models.
4 properties
dossier.list.CarePlanEntryList
object
CarePlanEntryList model (no description)
1 property
survey.Answer
object
Answer model (no description)
7 properties
dossier.GoalEntry
object
Zorgplan "doel" entry.
7 properties
dossier.CarePlanEntry
object
"Zorgplan" entry.
11 properties
dossier.ActionEntry
object
Zorgplan "actie" entry
7 properties
survey.ImportantForCarePlanGroup
object
ImportantForCarePlanGroup model (no description)
5 properties
dossier.Domain
object
Zorgplan "domein"
4 properties
survey.AnswerDefinitionGroup
object
AnswerDefinitionGroup model (no description)
6 properties
dossier.Demand
object
Zorgplan "aandachtspunt"
7 properties
dossier.DemandEntry
object
Zorgplan "aandachtspunt" entry
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nedap-dossier-careplanentry-api-openapi.yml Raw ↑

Other APIs Nedap publishes across the network.

Nedap Retail iD Cloud API
AE Profile APIs.io
Nedap Address API
AE Profile APIs.io
Nedap Admin.Background Image API
AE Profile APIs.io
Nedap Admin.License API
AE Profile APIs.io
Nedap Admin.Logo Image API
AE Profile APIs.io
Nedap Admin.Timesheet Config API
AE Profile APIs.io
Nedap Admin.Version API
AE Profile APIs.io
Nedap Agbcode API
AE Profile APIs.io
Nedap Agenda.Agenda Occurrence API
AE Profile APIs.io
Nedap Agenda.Agenda Series API
AE Profile APIs.io
Nedap Agenda.Client Absence Occurrence API
AE Profile APIs.io
Nedap Agenda.Label API
AE Profile APIs.io
← Back to N APIs
API Details
ID
nedap:nedap-dossier-careplanentry-api
Base URL
https://api.ons.io
Docs
https://ons-api.nl/english/english.html
Provider
Nedap
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=nedap-dossier-careplanentry-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/nedap-dossier-careplanentry-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Nedap Dossier.Care Plan Entry 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.