canonical: https://jentic.com/apis/singaporechatbots.sg/singaporechatbots-sg # Singaporechatbots Sg Facility Chatbot API documentation. FacilityBot API for facility management, fault reporting, and building maintenance. The API exposes 1320 endpoints. ## For AI agents Programmatically getapiv1managerspersonalmapsetting, putapiv1managerspersonalmapsetting. Covers 1320 operations. ## Scope Does not handle payments, crm, or developer tools - use for communications only. ## Capabilities - getApiV1ManagersPersonalMapSetting - putApiV1ManagersPersonalMapSetting - putApiV1ManagersAvailabilityStatus - postApiV1ManagersDisableTwoFactorAuthentication - postApiV1ManagersVerifyTwoFactorAuthentication - postApiV1ManagersRegisterTwoFactorAuthentication - getApiV1ManagersId ## Use cases ### Communications Operations Use the Facility Chatbot API documentation. to perform communications operations programmatically. The API provides 1320 endpoints covering core functionality including getapiv1managerspersonalmapsetting, putapiv1managerspersonalmapsetting, putapiv1managersavailabilitystatus. Example prompt: Call GET `/api/v1/managers/personal_map_setting` to getapiv1managerspersonalmapsetting ### Automated Account_Tags Management Automate account_tags operations by combining multiple Facility Chatbot API documentation. endpoints. Agents can putapiv1managerspersonalmapsetting and then putapiv1managersavailabilitystatus in a single workflow. Example prompt: Call PUT `/api/v1/managers/personal_map_setting` to putapiv1managerspersonalmapsetting, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Facility Chatbot API documentation. endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually. Example prompt: Search Jentic for 'getapiv1managerspersonalmapsetting', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/managers/personal_map_setting` | getApiV1ManagersPersonalMapSetting | | PUT | `/api/v1/managers/personal_map_setting` | putApiV1ManagersPersonalMapSetting | | PUT | `/api/v1/managers/availability_status` | putApiV1ManagersAvailabilityStatus | | POST | `/api/v1/managers/disable_two_factor_authentication` | postApiV1ManagersDisableTwoFactorAuthentication | | POST | `/api/v1/managers/verify_two_factor_authentication` | postApiV1ManagersVerifyTwoFactorAuthentication | | POST | `/api/v1/managers/register_two_factor_authentication` | postApiV1ManagersRegisterTwoFactorAuthentication | | GET | `/api/v1/managers/{id}` | getApiV1ManagersId | | GET | `/api/v1/managers/manager_topics` | getApiV1ManagersManagerTopics | ## Key resources - **Account_Tags** — Operations for account_tags - **Accounts** — Operations for accounts - **Agent_Managements** — Operations for agent_managements - **Agents** — Operations for agents - **Announcements** — Operations for announcements ## Why Jentic - **Setup:** Wiring the Facility Chatbot API by hand means reading its spec to find the right manager and topic endpoints on the facility-chatbot host and threading each call through yourself. Through Jentic you install once, import the Facility Chatbot API from the API Directory, and your agent calls it. - **Permission scoping:** The Facility Chatbot API puts the manager id in the URL path (`/api/v1/managers/{id}`), so a rule can pin your agent to one manager record: it can read that manager and nothing else. You choose the operations it may call, so changes like updating a personal map setting or availability status are not included unless you add them. - **Credential handling:** This Facility Chatbot API endpoint set requires no credential, so there is no secret to store, and your own Jentic One instance still keeps request handling out of the agent's prompt, logs, and context. - **Discovery method:** Agents search Jentic by intent such as 'read a manager profile' or 'list manager topics', and Jentic returns the matching Facility Chatbot API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Twilio** — Alternative communications API - **Sendgrid** — Alternative communications API - **Pusher** — Complementary communications API ## FAQ ### What authentication does the Facility Chatbot API documentation. use? The Facility Chatbot API documentation. uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I getapiv1managerspersonalmapsetting with the Facility Chatbot API documentation.? Yes. Use the GET `/api/v1/managers/personal_map_setting` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Facility Chatbot API documentation.? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I getapiv1managerspersonalmapsetting through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getapiv1managerspersonalmapsetting'. Jentic returns the matching Facility Chatbot API documentation. operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Facility Chatbot API documentation. have? The Facility Chatbot API documentation. exposes 1320 endpoints covering account_tags, accounts, agent_managements operations. ### Can I limit what my agent is allowed to do with the Facility Chatbot API? Yes. Jentic One runs self-hosted, so your own rules decide which Facility Chatbot operations and credentials the agent may use. Because this API carries the manager id in the URL path (`/api/v1/managers/{id}`), a rule can pin the agent to a single manager record and grant read-only access to that manager. Write operations like updating a personal map setting or availability status stay off unless you explicitly add them to the agent's allowed operations.