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 Expense.Expense API

The expense.Expense API from Nedap — 10 operation(s) for expense.expense.

Nedap Expense.Expense 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 14 operations across 10 paths, and defines 5 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 10 paths 5 schemas 2 DELETE4 GET4 POST4 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 10 paths, the API surfaces 14 operations — 2 DELETE, 4 GET, 4 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

expense.Expense 14
POST
/t/expense/expensesdeprecated
Create Expense
expense.ExpenseAPI.create 2 params body → 200400
GET
/t/expense/expenses/{id}deprecated
Return the Expense corresponding to the given id
expense.ExpenseAPI.byId 3 params → 200400404
PUT
/t/expense/expenses/{id}deprecated
Updates the given Expense
expense.ExpenseAPI.update 3 params body → 200400404
DELETE
/t/expense/expenses/{id}deprecated
Deletes the Expense with given id
expense.ExpenseAPI.delete 3 params → 200400404
GET
/t/expense/expenses/search_by/employees/{employee_id}deprecated
Retrieve all expenses for the employee corresponding to the given employee id
expense.ExpenseAPI.searchByEmployeeId 3 params → 200
PUT
/t/expense/expenses/expensedistance/{expense_distance_id}deprecated
Updates an expense distance position with a new position value
expense.ExpenseAPI.updatePositionForExpenseDistance 1 param body → 200
POST
/t/expense/expenses/previewdeprecated
Used to get created Expense Route Without saving the expense
expense.ExpenseAPI.previewExpense 2 params body → 200400
POST
/v0/administration/expenses
Create Expense
postV0AdministrationExpenses 2 params body → 200400
GET
/v0/administration/expenses/{id}
Return the Expense corresponding to the given id
getV0AdministrationExpensesById 3 params → 200400404
PUT
/v0/administration/expenses/{id}
Updates the given Expense
putV0AdministrationExpensesById 3 params body → 200400404
DELETE
/v0/administration/expenses/{id}
Deletes the Expense with given id
deleteV0AdministrationExpensesById 3 params → 200400404
GET
/v0/administration/expenses/employees/{employee_id}
Retrieve all expenses for the employee corresponding to the given employee id
getV0AdministrationExpensesEmployeesByEmployeeId 3 params → 200
PUT
/v0/administration/expenses/expensedistance/{expense_distance_id}
Updates an expense distance position with a new position value
putV0AdministrationExpensesExpensedistanceByExpenseDistanceId 1 param body → 200
POST
/v0/administration/expenses/preview
Used to get created Expense Route Without saving the expense
postV0AdministrationExpensesPreview 2 params body → 200400

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are expense.Expense (13 properties), registration.Position (9 properties), expense.ExpenseDistance (6 properties), expense.list.ExpenseList (1 property). Each schema is shown below with its type and property counts.

expense.list.ExpenseList
object
ExpenseList model (no description)
1 property
registration.Position
object
A Position denotes a physical location on a map. This position can either consist of address information, a longitude/latitude pair or both. Not all fields are…
9 properties
expense.ExpenseDistance
object
An expense distance is the distance traveled to a location (position).
6 properties
DepartureLocation
string
DepartureLocation which is used to determine which address should be used for the automated travel calculations
expense.Expense
object
An expense is a value of some kind (determined) by its type, that an employee will be compensated for (usually via her payroll). Expenses can either be manual…
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nedap-expense-expense-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 Expense.Expense 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.