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 Client Story.Story API

The client_story.Story API from Nedap — 14 operation(s) for client_story.story.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include client_story.Story. 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 14 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 14 paths 4 schemas 10 GET2 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 14

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

client_story.Story 14
GET
/t/client_story/authorized/images/by_client_id_and_referencedeprecated
Authorized api Return a base64 encoded string of the image that is identified…
client_story.StoryAPI.authorizedImageByClientIdAndReference 2 params → 200
GET
/t/client_story/authorized_stories/full_by_client/{client_id}deprecated
Return the full client story for the given client id
client_story.StoryAPI.authorizedFullByClient 1 param → 200
POST
/t/client_story/care_relations/request_for_client/{client_id}deprecated
Get permission for the current careprovider to view the client story
client_story.StoryAPI.createPermission 1 param → 200
GET
/t/client_story/images/by_client_id_and_referencedeprecated
Return a base64 encoded string of the image that is identified by the given…
client_story.StoryAPI.imageByClientIdAndReference 2 params → 200
PUT
/t/client_story/stories/by_client/{client_id}deprecated
Save updates to the story of the client incrementally
client_story.StoryAPI.saveAnswer 1 param body → 200
GET
/t/client_story/stories/full_by_client/{client_id}deprecated
Return the full client story for the given client id
client_story.StoryAPI.fullByClient 1 param → 200
GET
/t/client_story/stories/single_answer_full_by_client/{client_id}deprecated
Return the full client story for the given client id Collapses the full json…
client_story.StoryAPI.singleAnswerFullByClient 1 param → 200
GET
/v0/client_story/authorized/clients/{client_id}/client_story/images
Authorized api Return a base64 encoded string of the image that is identified…
getV0ClientStoryAuthorizedClientsByClientIdClientStoryImages 2 params → 200
GET
/v0/client_story/authorized/stories/full_by_client/{client_id}
Return the full client story for the given client id
getV0ClientStoryAuthorizedStoriesFullByClientByClientId 1 param → 200
POST
/v0/client_story/care_relations/request_for_client/{client_id}
Get permission for the current careprovider to view the client story
postV0ClientStoryCareRelationsRequestForClientByClientId 1 param → 200
GET
/v0/client_story/clients/{client_id}/client_story/images
Return a base64 encoded string of the image that is identified by the given…
getV0ClientStoryClientsByClientIdClientStoryImages 2 params → 200
PUT
/v0/client_story/stories/by_client/{client_id}
Save updates to the story of the client incrementally
putV0ClientStoryStoriesByClientByClientId 1 param body → 200
GET
/v0/client_story/stories/full_by_client/{client_id}
Return the full client story for the given client id
getV0ClientStoryStoriesFullByClientByClientId 1 param → 200
GET
/v0/client_story/stories/single_answer_full_by_client/{client_id}
Return the full client story for the given client id Collapses the full json…
getV0ClientStoryStoriesSingleAnswerFullByClientByClientId 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are client_story.Story (6 properties), client_story.Category (4 properties), client_story.Answer (3 properties). Each schema is shown below with its type and property counts.

client_story.Category
object
Category model (no description)
4 properties
client_story.AccessLevel
string
The access level of the story, can be NONE, READONLY, or READWRITE
client_story.Story
object
Story model (no description)
6 properties
client_story.Answer
object
Answer model (no description)
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nedap-client-story-story-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
#client_story.Story
← Back to N APIs
API Details
ID
nedap:nedap-client-story-story-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-client-story-story-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/nedap-client-story-story-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 Client Story.Story 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.