Each listing documents what a platform exposes through its official API today, where the gaps are, and which actions Integuru could generate for it.
npm install -g integuruBuildertrend's REST API requires partner approval, leaving most construction tech teams without a programmatic path to project, schedule, and financial data. Integuru can generate a production-ready HTTP API — chat with us to get started.
FieldEdge has no public API. The legacy HVAC, plumbing, and electrical dispatch platform exposes no developer access of any kind. Integuru can generate a production-ready HTTP API covering jobs, customers, and technician dispatch. Chat with us to get started.
Fieldwire's REST API covers basic tasks and plans but leaves RFI workflows, sheet markups, and advanced reporting inaccessible. Integuru can generate a complete production-ready HTTP API — chat with us to get started.
Housecall Pro's beta API covers basic job and customer reads but enforces rate limits and leaves scheduling, dispatch, and write operations inaccessible. Integuru generates a complete managed HTTP API. Chat with us to get started.
Jobber's public GraphQL API covers read-heavy workflows but gates write operations behind app review and enforces rate limits that break production pipelines. Integuru generates a complete managed HTTP API. Chat with us to get started.
Procore's App Marketplace review gates production API access, and web-app-only reports remain off-limits entirely. Integuru delivers a managed HTTP API with 24/7 maintenance — chat with us to get started.
Sage 300 Construction and Real Estate has no public REST API — only a legacy SOAP/COM layer for certified Sage partners. Integuru can generate a production-ready HTTP API — chat with us to get started.
ServiceTitan's partner API requires paid certification and minimum ARR commitments that block most teams. Integuru generates a production-ready HTTP API covering jobs, customers, invoices, and dispatch. Chat with us to get started.
Glofox limits API access to gym and studio partners and does not fully document what it exposes, blocking most teams from client, class, membership, and attendance data. Integuru can generate a production-ready HTTP API — chat with us to get started.
Mindbody's partner enrollment and rate limits block most teams from building on its API. Integuru generates a managed, production-ready HTTP API for client, appointment, and membership data — chat with us to get started.
AdvancedMD restricts REST API access to marketplace partners, leaving most healthtech teams without a self-serve path to patient, appointment, clinical note, and billing data. Integuru can generate a production-ready HTTP API — chat with us to get started.
athenahealth restricts REST API access to approved developer program partners, leaving most healthtech teams without a self-serve path to patient, appointment, clinical note, and billing data. Integuru can generate a production-ready HTTP API — chat with us to get started.
Jane App has no public developer API, leaving allied health practices and healthtech teams with no programmatic path to patient records, appointments, billing, or clinical documentation. Integuru can generate a production-ready HTTP API — chat with us to get started.
Tebra's appointment scheduling is live on Integuru today. This page covers the broader Kareo/Tebra clinical and billing workflows — patient records, clinical notes, claims, and insurance — that go beyond scheduling. Chat with us to get started.
Applied Epic restricts REST API access to select Applied Systems partners, leaving most insurtech teams without a programmatic path to policy, client, claims, and certificate data. Integuru can generate a production-ready HTTP API — chat with us to get started.
Duck Creek APIs for policy, billing, and claims are partner-gated, leaving most insurtech teams without a self-serve path to P&C carrier data. Integuru can generate a production-ready HTTP API — chat with us to get started.
Guidewire Cloud APIs for PolicyCenter, BillingCenter, and ClaimCenter require a Guidewire implementation partner agreement. Integuru can generate a production-ready HTTP API without the partnership dependency — chat with us to get started.
HawkSoft has no public API and no developer program, leaving independent agency management workflows completely inaccessible programmatically. Integuru can generate a production-ready HTTP API — chat with us to get started.
Clio has a documented REST API, but bulk document operations, administrative reporting views, and OAuth token management create production bottlenecks. Integuru provides a managed HTTP API that covers what the official API misses; chat with us to get started.
Filevine's REST API requires a formal partner program and dedicated account access, blocking most development teams from matter, contact, time, and document workflows. Integuru can generate a production-ready HTTP API: chat with us to get started.
MyCase controls its API access to select integration partners, leaving most development teams without a self-serve path to matter, contact, time, and billing data. Integuru can generate a production-ready HTTP API: chat with us to get started.
Neos (by Assembly Software) has no public developer API, leaving matter management, contact, time, document, and billing workflows completely inaccessible programmatically. Integuru can generate a production-ready HTTP API: chat with us to get started.
Clover has a public REST API but with coverage gaps in reporting views, batch exports, and web-app-only data surfaces. Integuru adds the managed-service layer for production reliability — chat with us to get started.
Lightspeed Restaurant has a public REST API but with coverage and throughput limitations that block reporting, batch exports, and high-frequency data access. Integuru can generate a production-ready HTTP API — chat with us to get started.
Square for Restaurants has a public API but omits restaurant-specific data like floor plans, course management, and certain reporting views. Integuru adds the managed-service layer for production reliability — chat with us to get started.
Toast restricts production API access to formal partner agreements, blocking most teams from POS, menu, and order data until approval clears. Integuru can generate a production-ready HTTP API — chat with us to get started.
Boulevard controls REST API access to select integration partners, leaving most teams without a self-serve path to client, appointment, transaction, and invoice data. Integuru can generate a production-ready HTTP API — chat with us to get started.
GlossGenius has no public developer API. Integuru is the only programmatic path to client, appointment, and transaction data for this salon scheduling and payments platform — chat with us to get started.
ADP restricts Marketplace API access to certified partners after a months-long review process, blocking most engineering teams from payroll, employee, and time data. Integuru can generate a production-ready HTTP API — chat with us to get started.
Gusto has a public REST API but with significant endpoint coverage gaps in payroll run details, contractor payments, and garnishments. Integuru fills those gaps with a production-ready HTTP API — chat with us to get started.
Paychex Flex API access requires a formal partner onboarding process with no self-serve path, leaving most engineering teams without access to payroll, employee, and time data. Integuru can generate a production-ready HTTP API — chat with us to get started.
Rippling has no public developer API. Engineering teams that need to sync employee, payroll, or benefits data out of Rippling have no official programmatic route. Integuru's direct HTTP approach is the only path — chat with us to get started.
Not seeing your platform?
If the platform you need isn't listed here, chat with us. Integuru analyzes any platform's network requests and generates a production-ready HTTP API; no official API required. Sandbox testing is always free before you go to production. See what's already live in the integrations catalogue.