Planning, time and vacation — your systems talk directly to infoBoard.
The infoBoard REST API gives your systems programmatic access to planning objects, time tracking, digital planning boards, clock-in times and vacation management. JSON over HTTPS, secured with a Bearer token.
- REST over HTTPS
- JSON
- Bearer token
- Documentation on request
In many companies, order, time and employee data sits in several systems — in the ERP, in the time tracking system, in your own tools. Every manual export costs time and creates the risk that two systems show different information.
The infoBoard REST API closes that gap programmatically. Your developers access planning objects, time tracking, planning boards, clock-in times and vacation management directly, over JSON and HTTPS.
One API for planning, time tracking and HR processes.
The REST API follows common conventions. Every response has the same structure: content, API code, HTTP code and message. If you have connected a REST API before, you will find your way around immediately.
Connect planning objects — read, create, edit, delete.
Read planning objects from your planning board, or create, change and delete them — straight from your own system.
Track time — start, stop, report complete, no re-typing.
Your systems start and stop time tracking, move or copy operations simultaneously and report orders complete — all through the API.
Read digital planning boards and clock-in times — for your own reports.
Pull planning board and clock-in data, then show it where your team already looks — in your own dashboard or report.
Manage vacation — request, approve, book.
The complete workflow runs through the API — from the vacation request, through approval or rejection, to booking the entitlement.
JSON over HTTPS, secured with a Bearer token.
Clear endpoints, one consistent response format and secure transmission. Your developers work with tools they already know.
Clearly documented — with examples for every endpoint.
The documentation describes endpoints, object properties and status codes — including sample requests you can try out right away.
How to get access
Access runs over HTTPS and is secured with a Bearer token. Read access works directly through the API. To create and edit planning objects, you also need the infoBoard Application Server. We work out with you which endpoints your use case needs — just request the documentation.
You get the full API documentation on request.
Just leave us your contact details — we will send you access to the documentation, with every endpoint, object property and example.
Planning a specific integration?
Describe your use case — we will tell you which endpoints you need, and whether the Application Server is required for write access. Directly with someone who knows the API.