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 Moves.Plan Card Occurrence API

The moves.PlanCardOccurrence API from Nedap — 6 operation(s) for moves.plancardoccurrence.

Documentation Provider Profile APIs.io OpenAPI GitHub

Nedap Moves.Plan Card Occurrence 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 6 operations across 6 paths, and defines 15 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.

6 operations 6 paths 15 schemas 2 PATCH4 POST

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 6

Across 6 paths, the API surfaces 6 operations — 2 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

moves.PlanCardOccurrence 6
PATCH
/t/plan_cards/{checksum}deprecated
Update a plan card occurrence
moves.PlanCardOccurrenceAPI.incidentalChange 1 param body → 200400401403404429
POST
/t/plan_cards/{checksum}/plandeprecated
Plan a single plan card into a container
moves.PlanCardOccurrenceAPI.plan 1 param body → 200400401403404429
POST
/t/plan_cards/searchdeprecated
Return the active plan cards searched for within a specified period
moves.PlanCardOccurrenceAPI.search body → 200400401403429
PATCH
/v0/plannen_roosteren/plan_cards/{checksum}
Update a plan card occurrence
patchV0PlannenRoosterenPlanCardsByChecksum 1 param body → 200400401403404429
POST
/v0/plannen_roosteren/plan_cards/{checksum}/plan
Plan a single plan card into a container
postV0PlannenRoosterenPlanCardsByChecksumPlan 1 param body → 200400401403404429
POST
/v0/plannen_roosteren/plan_cards/search
Return the active plan cards searched for within a specified period
postV0PlannenRoosterenPlanCardsSearch body → 200400401403429

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are moves.PlanCardOccurrence (17 properties), moves.PlannedAddress (9 properties), moves.PlanCardOccurrencePlanRequest (9 properties), moves.ContainerSearchRequest (5 properties). Each schema is shown below with its type and property counts.

moves.PlanCardOccurrencePlanRequest
object
Moves a single plan card to another time and order in a container
9 properties 4 required
moves.PlannedAddress
objectnull
Address where {@link PlannedVisit}s are planned. Moves has it's own Address model, and plancards can be planned tp addresses not known in other systems.
9 properties
moves.PlanCardOccurrence
object
A single instance of a recurring plan card as retrieved from the new Plancore.
17 properties 17 required
moves.ContainerSearchRequest
object
The request body used to search for containers
5 properties 2 required
moves.Recurrence
object
This describes how often this plan card should occur.
3 properties 3 required
moves.PlanCardOccurrenceResponseMetadata
object
Metadata about the impact of the plan card occurrence planning
1 property
moves.PlanCardOccurrenceResponse
object
The response from a successful plan card planning mutation
2 properties
moves.PlanCardOccurrenceAttributesRequest
object
Incidentally update a plan card occurrence, for example by canceling a single care moment
5 properties 4 required
moves.PlanCardOccurrenceResponseMetadataImpact
object
Metadata about the impact of the plan card occurrence planning
1 property
moves.PlanCardOccurrenceList
object
A response body that contains a list of plan tasks found for this search
2 properties 2 required
moves.RecurrenceType
string
The type of repetition between occurrences. Weekly means once a week, Incidental means once for this validFrom until validTo period.
moves.ContainerAssignment
objectnull
An assignment of a plan card to a specific container ( shift or employee ) on a specific date. 'null' refers to being unplanned
2 properties 2 required
moves.PlanCardOccurrenceId
object
A set of identifiers linking to a single PlanCardOccurrence with additional checksums for mutation validations.
3 properties 3 required
moves.PlanCardRecurrenceInformation
object
This describes how often this plan card should occur.
moves.MovesRatelimitError
object
An error describing a specific rate limit has been reached and that the client should wait to retry the response
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nedap-moves-plancardoccurrence-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-moves-plancardoccurrence-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-moves-plancardoccurrence-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/nedap-moves-plancardoccurrence-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 Moves.Plan Card Occurrence 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.