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.omaha.Omaha Classification API

The dossier.omaha.OmahaClassification API from Nedap — 6 operation(s) for dossier.omaha.omahaclassification.

Documentation Provider Profile APIs.io OpenAPI GitHub

Nedap Dossier.omaha.Omaha Classification 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 8 operations across 6 paths, and defines 18 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.

8 operations 6 paths 18 schemas 4 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 8

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

dossier.omaha.OmahaClassification 8
GET
/t/dossier/omaha/omaha_classifications/{id}deprecated
Get the OmahaClassification corresponding to the given id
dossier.omaha.OmahaClassificationAPI.byId 3 params → 200400404
PUT
/t/dossier/omaha/omaha_classifications/{id}deprecated
Updates the given OmahaClassification
dossier.omaha.OmahaClassificationAPI.update 3 params body → 200400
POST
/t/dossier/omaha/omaha_classifications/by_client/{client_id}/newdeprecated
Create an OmahaClassification for the Client corresponding to the given id
dossier.omaha.OmahaClassificationAPI.newDraft 3 params → 200400
GET
/t/dossier/omaha/omaha_classifications/by_survey_result/{survey_result_id}deprecated
Dossier omaha omaha classification API by survey result
dossier.omaha.OmahaClassificationAPI.bySurveyResult 1 param → 200
GET
/v0/administration/omaha/classifications/{id}
Get the OmahaClassification corresponding to the given id
getV0AdministrationOmahaClassificationsById 3 params → 200400404
PUT
/v0/administration/omaha/classifications/{id}
Updates the given OmahaClassification
putV0AdministrationOmahaClassificationsById 3 params body → 200400
POST
/v0/administration/omaha/classifications/by_client/{client_id}/new
Create an OmahaClassification for the Client corresponding to the given id
postV0AdministrationOmahaClassificationsByClientByClientIdNew 3 params → 200400
GET
/v0/administration/omaha/classifications/by_survey_result/{survey_result_id}
Dossier omaha omaha classification API by survey result
getV0AdministrationOmahaClassificationsBySurveyResultBySurveyResultId 1 param → 200

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are dossier.omaha.ClassifiedProblem (15 properties), dossier.omaha.OmahaClassification (15 properties), survey.Question (13 properties), survey.AnswerDefinition (9 properties). Each schema is shown below with its type and property counts.

dossier.omaha.ClassifiedProblem
object
(nl) Omaha Gebieden
15 properties
survey.AnswerDefinitionGroup
object
AnswerDefinitionGroup model (no description)
6 properties
survey.AnsweredQuestion
object
AnsweredQuestion model (no description)
1 property
dossier.omaha.ClassifiedIntervention
object
(nl) Omaha Acties
6 properties
survey.Question
object
Question model (no description)
13 properties
dossier.omaha.ClassificationStatus
string
Status of this omaha classification
AuditedBase
object
AuditedBase model (no description)
3 properties
dossier.omaha.Problem
object
Omaha definitie van 'gebied'
4 properties
dossier.omaha.Domain
object
Omaha Domein
2 properties
dossier.omaha.SignOrSymptom
object
Omaha definitie van 'signalen en symptomen'
4 properties
dossier.omaha.ClassifiedSignOrSymptom
object
(nl) Omaha 'Signalen en symptomen'
2 properties
dossier.omaha.InterventionTarget
object
Omaha Actievlak
2 properties
survey.Answer
object
Answer model (no description)
7 properties
dossier.omaha.ModifierReach
string
(nl) Omaha kenmerken (1/2)
dossier.omaha.InterventionCategory
object
Omaha soort actie
2 properties
survey.AnswerDefinition
object
AnswerDefinition model (no description)
9 properties
dossier.omaha.ModifierProblemLevel
string
(nl) Omaha kenmerken (2/2)
dossier.omaha.OmahaClassification
object
represents a full Omaha classification for one client, including both problem and intervention classification
15 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nedap-dossier-omaha-omahaclassification-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-omaha-omahaclassification-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-omaha-omahaclassification-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/nedap-dossier-omaha-omahaclassification-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.omaha.Omaha Classification 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.