September 2026 Summaries

Unified’s MCP server integrates with LangChain and LangGraph through the official MCP adapter, exposing more than 67,000 Unified tools as native LangChain tools for AI agents that interact with connected CRM, ATS, HRIS, accounting, ticketing, storage, messaging, and commerce systems. The guide provides Python and TypeScript quickstarts showing how to authenticate with a workspace API key, scope access to an end-customer connection, retrieve available tools, and use them with LangChain agents or LangGraph ToolNodes for multi-step workflows. Available tools vary according to the customer’s connected integration and authorized permissions, while URL parameters can restrict tool access, enforce read-only permissions, and hide sensitive personal data. It recommends retaining workspace API keys on the backend, using per-customer MCP clients in multi-tenant applications to isolate data access, and directly invoking tools for deterministic workflows. The document also identifies separate US and EU endpoints and offers troubleshooting guidance for authentication failures, missing tools, incorrect tool selection, and improperly supplied server options.

Regulated SaaS integrations can expand compliance risk when they persist webhook payloads, polling snapshots, logs, or third-party records, turning an integration layer into an unplanned data store subject to audit, retention, security, and residency requirements. A zero-storage architecture minimizes this footprint by processing authorized data in transit, routing requests directly to source APIs, returning real-time results, and discarding data after delivery rather than retaining external records or cached payloads. Because native webhooks vary widely across platforms, the approach recommends a consistent webhook interface that uses native events where available and centrally managed, stateless change detection where they are not, avoiding stored snapshots while handling rate limits and retries. Effective residency controls also require regional traffic routing, customer-controlled credentials and observability systems, network restrictions, and clear visibility into where data flows and what logs contain. The article argues that these architectural choices can simplify security reviews, improve real-time product and AI capabilities, reduce maintenance, and provide clearer answers to enterprise audit questions.

Unified.to received the 2026 API Award for Best Business Software API at API World 2026 in Santa Clara, California, after selection by the API World Advisory Board from public nominations. The award, one of 26 presented by DevNetwork, recognizes technical innovation, industry impact, API-community adoption, and contributions to API practices. Unified.to’s Real-Time Unified API enables B2B SaaS applications to read and write directly to customers’ source systems across categories including CRM, accounting, and applicant tracking, without retaining a full copy of customer data. Its architecture transforms requests, pagination, payloads, and webhook events in real time, while retaining only encrypted connection identifiers and limited operational metadata. The company argues that direct source access reduces inconsistencies caused by delayed synchronization, particularly for write operations and AI agents that require current information; its MCP server provides similar scoped access and can remove personally identifiable information before data reaches models. Unified.to CEO Roy Pereira credited the company’s customers and product teams for the recognition.

Virtual webhooks create a consistent event stream by separating integration reads from endpoint dispatches, allowing each stage to recover independently when failures occur. If a receiving endpoint times out or returns an error, Unified makes several immediate retry attempts before applying progressively longer delays over a recovery period of up to roughly two weeks, while a successful delivery resets the schedule. Integration read failures such as transient API errors or rate limits use similar backoff behavior and respect provider retry guidance, whereas terminal connection problems like broken authorization can immediately mark a webhook unhealthy. This separation prevents endpoint outages from consuming integration retry capacity and vice versa, although once a subscription reaches `is_healthy: false`, both reading and dispatch stop until intervention. Users should return a 2xx response after safely accepting payloads, design handlers to tolerate possible duplicate deliveries, keep endpoints reachable, and monitor health status for persistent failures.

Workable treats talent-pool candidates and job-specific candidates as separate records, so creating a person with the candidate endpoint produces a talent-pool ID, while attaching that person to a job through the application endpoint creates a distinct job-scoped candidate ID and application ID. Integrations should store both identifiers, using the new job-scoped candidate ID for later job-related retrievals or updates and avoiding repeated application creation with the original talent-pool ID, which would create duplicate copies. Candidate creation is safe to retry by email because Unified returns an existing talent-pool candidate when Workable rejects a duplicate, while searches by email may return both talent-pool and job-scoped records after an attachment. Changes to either record do not synchronize to the other, making native IDs necessary despite matching email addresses. Application creation also requires a Workable member ID, preferably supplied as a user ID, and email searches can help recover valid current IDs if an older ID returns a 404 error.

Unified.to’s Social Media API enables products to publish content to customers’ connected social accounts through a single SDK method and standardized Post object, covering platforms such as LinkedIn, Instagram, Bluesky, Google Business Profile, Mastodon, and Pinterest while executing writes directly on the originating platforms. Customers authorize accounts to generate connection IDs, applications list available profiles for account selection, and composers can support text, media, accessibility alt text, titles, calls to action, post types, replies, quotes, language, and scheduling where individual platforms allow them. Because platform capabilities and requirements differ, developers are advised to consult the integration capability matrix, adapt interfaces to supported fields, enforce mandatory media rules for platforms such as Instagram and Pinterest, and interpret 501 responses as unsupported functionality rather than retryable failures. After creating a post, applications should store its returned ID and retrieve its status and public URL to distinguish published, processing, rejected, draft, scheduled, or deleted states. The API also supports listing existing posts and metrics, updating or removing posts where available, replying through parent post IDs, and publishing the same content to multiple profiles through separate calls, while applications may need their own scheduling system when a platform does not support native scheduled publishing.

Unified has introduced a Social Media API that provides a standardized interface for reading and writing posts, profiles, reviews, and engagement insights across platforms including Instagram, Facebook, LinkedIn, Google Business Profile, Trustpilot, Threads, Pinterest, Bluesky, Mastodon, and Twitter. The API uses four normalized objects—Post, Profile, Review, and Insight—while executing requests directly against each customer’s source platform in real time without caching or storing end-customer data. It supports products such as cross-platform publishing tools, review-response inboxes, local listing management, reporting dashboards, threaded conversations, and AI agents that need current social data. Coverage, writable fields, scheduling, query options, and webhook availability vary by platform because they remain subject to each provider’s API, developer-program approvals, account restrictions, and content rules. Posts can generally be created, updated, or removed, reviews can be read and replied to where supported, and profiles and insights are read-only, with webhooks currently available for post creation and updates on supported integrations.

Unified.to’s August 2026 update reported 829 integrations and 2,805 enhancements, with expansion focused on regional accounting, e-commerce marketplaces, point-of-sale systems, applicant tracking, and assessments. The company launched Unified Social Media and Performance Management APIs, enabling standardized access to social profiles, posts, reviews, engagement data, performance cycles, reviews, goals, and feedback across supported platforms. Major platform-wide additions included bank feed accounts and transactions on 45 accounting, banking, and payment integrations, a Paymentterm object across major accounting systems, Shipment and Tracking objects for commerce and ERP platforms, and employee_roles fields across 242 integrations. Other improvements added attendance, time, HR taxonomy, commerce order, payment, item-pricing, messaging, call-recording, reporting, webhook, pagination, and search capabilities. The update emphasizes a direct-to-source API model without cached records and a strategy of making common objects and fields available in consistent formats across many vendors to reduce per-integration development work.

Floats, a platform that converts ATS candidate records into branded, evidence-based profiles for staffing agencies, selected Unified.to to avoid dedicating most of an engineering year to building and maintaining individual ATS integrations. The company determined that direct or in-house integrations would limit prospective customers, require handling varied authentication, data models, rate limits, and partner approvals, and divert resources from its AI-driven profile-generation capabilities. Unified.to’s pass-through architecture, which reads data from source ATS platforms without retaining mirrored candidate databases, helped reduce security-review concerns involving third-party personal data. Its documented read and write capabilities also enabled Floats to ensure profiles and candidate statuses could be returned to each ATS. Floats expanded from support for one ATS to more than 140 platforms, allowing it to pursue more deals while focusing development on SOLA, its beta AI recruiting assistant for ATS search, candidate matching, and candidate research.