Authenticate to the iOffice (Eptura Workplace / Hummingbird) REST API with header-based credentials and manage user and space records.
domain: ioffice.github.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Send every request over HTTPS with x-auth-username and x-auth-password headers set to your integration's credentials
Call GET /external/api/rest/v2/users with a search parameter to look up an employee by ID
Call GET or PUT on the rooms (space) resource to read or update space inventory, noting the API still uses room terminology even though the product now refers to spaces
Call the buildings count endpoint with a locationSearch parameter to retrieve building or asset counts for a city or state
When updating a record with PUT, send only the id plus the changed fields rather than the full object
Known gotchas
Authentication is username/password sent in request headers rather than OAuth2 or an API key, so store and rotate these credentials carefully
Default page size is 50 and capped at 100, and issuing concurrent paginated requests can trigger 429 responses, so page sequentially
The public docs still live on the legacy iOffice GitHub Pages site rather than a rebranded Eptura portal, and may lag behind current Hummingbird app naming
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?