








































































































.webp)





















iOffice (now part of Eptura) provides workplace management software for space, asset, move, and visitor management in corporate facilities.
Have any questions? We’re here to help You
All API requests require authentication via bearer token. After successfully connecting a system through Makini's authentication module, you receive an API token. Include this token in the Authorization header of your requests: Authorization: Bearer YOUR_API_TOKEN. Each connection has a unique token, allowing you to manage multiple customer connections independently. Tokens remain valid as long as the underlying system credentials are valid and the connection is active. If a customer changes their system credentials, you'll need to reconnect to obtain a new token.
Makini uses standard HTTP status codes and structured error responses. Error responses include an error code (e.g., AUTHENTICATION_FAILED, RATE_LIMIT_EXCEEDED), error type for categorization, a human-readable error message, and a unique request ID for support inquiries. Common status codes include 400 for invalid requests, 401 for authentication failures, 403 for permission issues, 429 for rate limiting, 500 for server errors, and 503 for service unavailability. Use the error code for programmatic error handling rather than parsing error messages. The request ID helps our support team quickly identify and investigate specific issues.
Makini provides tiered support plans. Standard support includes email support with business hours response times, access to documentation and knowledge base, and webhook notifications for issues. Extended support adds direct access to our engineering team, faster response times including after-hours support for critical issues, proactive monitoring and recommendations, and assistance with custom development. Enterprise support includes dedicated support contacts, participation in architecture planning, quarterly business reviews, and priority feature requests. All plans include access to our API documentation, authentication guides, and community resources. Support hours can be added to any plan based on your anticipated needs.
No. For M2M setup, both "Authorization Flow" and "Authorization Code Grant" should be unchecked. Only "Client Credentials (Machine To Machine) Grant" should be checked, along with the required scopes (Restlets and REST Web Services).
