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 Care Provider API

The CareProvider API from Nedap — 16 operation(s) for careprovider.

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

Tagged areas include CareProvider. 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 16 operations across 16 paths, and defines 2 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.

16 operations 16 paths 2 schemas 2 DELETE10 GET4 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 16

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

CareProvider 16
POST
/t/external_care_providersdeprecated
Create CareProvider
CareProviderAPI.create body → 200400
POST
/t/external_care_providers/{care_provider_id}/assign_to_client/{client_id}deprecated
Assigns an external care provider to a client
CareProviderAPI.assignCareProviderToClient 2 params → 204
DELETE
/t/external_care_providers/{care_provider_id}/unassign_from_client/{client_id}deprecated
Unassigns an external care provider from a client
CareProviderAPI.unassignCareProviderFromClient 2 params → 204
GET
/t/external_care_providers/{id}deprecated
Return the Care Provider corresponding to the given id
CareProviderAPI.byId 1 param → 200404
GET
/t/external_care_providers/category/{category_id}/{identification}deprecated
Care provider API by category and identification
CareProviderAPI.byCategoryAndIdentification 2 params → 200
GET
/t/external_care_providers/identification/{identification}deprecated
Return the Care Provider corresponding to the given identification
CareProviderAPI.byIdentification 1 param → 200404
GET
/t/external_care_providers/ura/{ura_number}deprecated
Return the Care Providers corresponding to the given URA number
CareProviderAPI.byUraNumber 1 param → 200400
GET
/t/clients/{client_id}/care_providersdeprecated
Return the care providers of a Client corresponding to the given id
CareProviderAPI.byClientId 1 param → 200
POST
/v0/administration/careproviders
Create CareProvider
postV0AdministrationCareproviders body → 200400
POST
/v0/administration/careproviders/{care_provider_id}/assign_to_client/{client_id}
Assigns an external care provider to a client
postV0AdministrationCareprovidersByCareProviderIdAssignToClientByClientId 2 params → 204
DELETE
/v0/administration/careproviders/{care_provider_id}/unassign_from_client/{client_id}
Unassigns an external care provider from a client
deleteV0AdministrationCareprovidersByCareProviderIdUnassignFromClientByClientId 2 params → 204
GET
/v0/administration/careproviders/{id}
Return the Care Provider corresponding to the given id
getV0AdministrationCareprovidersById 1 param → 200404
GET
/v0/administration/careproviders/category/{category_id}/{identification}
Care provider API by category and identification
getV0AdministrationCareprovidersCategoryByCategoryIdByIdentification 2 params → 200
GET
/v0/administration/careproviders/identification/{identification}
Return the Care Provider corresponding to the given identification
getV0AdministrationCareprovidersIdentificationByIdentification 1 param → 200404
GET
/v0/administration/careproviders/ura/{ura_number}
Return the Care Providers corresponding to the given URA number
getV0AdministrationCareprovidersUraByUraNumber 1 param → 200400
GET
/v0/administration/clients/{client_id}/careproviders
Return the care providers of a Client corresponding to the given id
getV0AdministrationClientsByClientIdCareproviders 1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are CareProvider (15 properties), list.CareProviderList (1 property). Each schema is shown below with its type and property counts.

CareProvider
object
The source of this MedicationChart. A pharmacy. identificationNumber and companyName should be filled. The identificationNumber should be the AGB-code of the p…
15 properties
list.CareProviderList
object
CareProviderList model (no description)
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nedap-careprovider-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 Care Provider 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.