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 Location API

The Location API from Nedap — 14 operation(s) for location.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Location. 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 18 operations across 14 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.

18 operations 14 paths 2 schemas 14 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 18

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

Location 18
GET
/t/clients/{client_id}/locationsdeprecated
Return the locations of a Client corresponding to the given id
LocationAPI.byClientId 3 params → 200
GET
/t/clients/{client_id}/main_locationdeprecated
Location API main location by client id
LocationAPI.mainLocationByClientId 2 params → 200
GET
/t/locationsdeprecated
Returns every Location available from the LocationAPI
LocationAPI.all → 200
POST
/t/locationsdeprecated
Create Location
LocationAPI.create body → 200400404
GET
/t/locations/{id}deprecated
Return the Location corresponding to the given id
LocationAPI.byId 1 param → 200404
PUT
/t/locations/{id}deprecated
Update Location
LocationAPI.update 1 param body → 200400404
GET
/t/locations/multipledeprecated
Method used for requesting multiple Location objects using their ids
LocationAPI.multiple 1 param → 200
GET
/t/locations/x-stream-connect/datadeprecated
Return all Location models in a streaming manner
LocationAPI.streamAll → 200400404500
GET
/t/locations/x-stream-connect/updatesdeprecated
Return all Location models which where updated since the date given in the…
LocationAPI.streamUpdates 1 param → 200400404500
GET
/v0/administration/clients/{client_id}/clipped_locations
Return the locations of a Client corresponding to the given id
getV0AdministrationClientsByClientIdClippedLocations 3 params → 200
GET
/v0/administration/clients/{client_id}/main_location
Location API main location by client id
getV0AdministrationClientsByClientIdMainLocation 2 params → 200
GET
/v0/administration/locations
Returns every Location available from the LocationAPI
getV0AdministrationLocations → 200
POST
/v0/administration/locations
Create Location
postV0AdministrationLocations body → 200400404
GET
/v0/administration/locations/{id}
Return the Location corresponding to the given id
getV0AdministrationLocationsById 1 param → 200404
PUT
/v0/administration/locations/{id}
Update Location
putV0AdministrationLocationsById 1 param body → 200400404
GET
/v0/administration/locations/multiple
Method used for requesting multiple Location objects using their ids
getV0AdministrationLocationsMultiple 1 param → 200
GET
/v0/xstream/locations/data
Return all Location models in a streaming manner
getV0XstreamLocationsData → 200400404500
GET
/v0/xstream/locations/updates
Return all Location models which where updated since the date given in the…
getV0XstreamLocationsUpdates 1 param → 200400404500

Schemas 2

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

list.LocationList
object
LocationList model (no description)
1 property
Location
object
Location model (no description)
25 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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