








































































































.webp)





















Facilities Link is a CAFM solution helping facility managers track work orders, preventive maintenance, assets, and tenant services across commercial portfolios.
Have any questions? We’re here to help You
Integration timelines vary by complexity. For standard implementations with no customizations, connections can be live within 1-2 weeks. This includes authentication setup and basic workflow configuration. For implementations requiring custom workflows or specific business logic, timelines typically range from 2-6 weeks depending on the scope. Complex enterprise deployments with multiple systems and custom requirements may take 6-10 weeks. These timelines are significantly shorter than traditional integration projects, which often take 2-24 months.
Makini's API supports date filtering on most endpoints using query parameters. You can filter by creation date, modification date, or entity-specific date fields like order date or delivery date. Common patterns include modified_after=2024-01-01 to retrieve records updated since a specific date, or relative timestamps like modified_after=2024-01-01T00:00:00Z. For optimal performance, use incremental data retrieval patterns rather than repeatedly fetching all records. The sync status endpoint provides the last sync timestamp, which you can use as the modified_after value for your next query. This approach minimizes data transfer and API load while ensuring you capture all changes.
Write operation limitations vary by system. Common limitations include: field-level restrictions (some fields may be read-only), business rule validation (orders may require certain fields or valid vendor codes), permission requirements (the connected account needs specific permissions), timing restrictions (some systems prevent modifications after certain workflow states), and rate limits on write operations. Custom fields in target systems may not be writable through standard APIs. Some systems have transactional requirements—for example, purchase order line items must be created in the same transaction as the order header. During implementation, we identify write operation limitations for your specific use cases and design workflows that work within those constraints.
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.
