August 2026 Summaries

Setting up Google Business Profile API access with OAuth 2.0 for a Unified integration requires a Google account with appropriate Business Profile permissions, an active and verified profile that generally meets Google’s age and website requirements, and a new Google Cloud project. Users must submit Google’s Application for Basic API Access early, since API quotas remain at zero and calls return 429 errors until approval, which may take days or weeks. After creating the project, users enable the required Business Profile APIs, configure an OAuth consent screen with the sensitive business.manage scope alongside standard identity scopes, and work with Unified Support to configure a CNAME for the redirect URL so the app can be verified under the desired branding. They then create web OAuth credentials using the redirect URI supplied by Unified, publish and verify the application, and enter the resulting client ID and secret into Unified. Approval can be confirmed through Cloud Console quotas, where 300 requests per minute indicates access is active; common issues include pending approval, incorrect OAuth credentials or redirect URI, missing profile permissions, disabled APIs, and unverified application branding.

The instructions describe how to register and configure a Facebook OAuth2 application for use with Unified.to. Users must create a Meta Developer account and app, provide its name and contact email, select the relevant use case, connect it to a business portfolio, and customize the Page management use case with permissions including page listing, engagement, content reading, insights, posting, email, and public profile access. Facebook Login for Business must then be configured with Unified.to OAuth2 redirect URLs, while the app’s basic settings should include Unified.to domains for standard, EU, and Australian services. Finally, the app’s ID and secret, found under App Settings > Basic, are entered into the Unified.to Facebook integration page to enable users to authorize Facebook connections.

Thrive Learning supports real-time Unified webhooks for objects including LMS content, courses, students, HRIS employees, and learning activity. Webhooks must be configured within the Thrive application, typically by asking the customer’s Thrive administrator or implementation team to create user subscriptions for students and employees, content subscriptions for content and courses, and completion subscriptions for activity events. Each subscription should use the relevant Unified workspace webhook URL with the appropriate workspace and connection IDs, and the Unified API endpoint should be adjusted when using a different regional API URL.

QuickBooks Online webhook registration must be configured manually in the Intuit Developer Portal because Intuit does not offer a programmatic registration API, while Unified receives Intuit notifications and distributes them to configured Unified webhook subscriptions. Setup requires an Intuit app with QuickBooks Online Accounting scopes, an OAuth-connected QuickBooks connection in a Unified workspace, and the workspace ID to construct a regional Unified callback URL. In the Intuit portal, users select the appropriate Production or Development environment, enter the endpoint, and enable supported entities such as Customer, Vendor, Invoice, and Class, which map to Unified accounting contact, invoice, and category objects. Native Unified webhooks must then be created for each required object and event combination, such as created, updated, or deleted. Testing involves sending a portal test notification or modifying an enabled entity in the matching QuickBooks company, then confirming Unified receives and forwards the event; common issues include an incorrect workspace ID, environment mismatch, disabled entities, missing Unified subscriptions, or a QuickBooks connection lacking a realm ID.

QuickBooks Online native webhooks with Unified require manual configuration in the Intuit Developer Portal because Intuit does not offer a programmatic webhook-registration API. Users need an Intuit Developer app with QuickBooks Accounting scopes, an OAuth-connected QuickBooks connection in a Unified workspace, and a workspace-specific Unified endpoint URL, with the appropriate regional API host where applicable. In the Intuit portal, they must select either the Production or Development environment, enter the Unified endpoint, and enable supported entities such as Customer, Vendor, Invoice, and Class, which map to Unified accounting contacts, invoices, and categories. Separate Unified native webhooks must then be created for each desired object and event, such as creation, updates, or deletions. Testing can involve Intuit’s test-notification feature and changes to enabled entities in a matching QuickBooks company, while troubleshooting focuses on the workspace ID, environment selection, entity settings, Unified event subscriptions, OAuth realm ID availability, and the fact that subscriptions are tracked separately for each QuickBooks company realm.

Facebook Messenger sends webhook events to a single callback URL configured once at the Meta App level, while individual connected Pages are subscribed through the integration. Setup requires adding the Messenger product in the Meta App Dashboard, configuring the Unified webhook URL with a workspace ID and any non-empty verification token, and subscribing the Page object to messages, messaging_postbacks, and message_reactions events. Required OAuth permissions include pages_messaging, pages_manage_metadata, and pages_read_engagement. Incoming non-echo messages are routed as messaging_message creation events and MESSAGE_RECEIVED events, while postbacks and quick replies become BUTTON_CLICK events and message reactions are classified as REACTION_ADDED or REACTION_REMOVED events.

Unified.to connects to JD Edwards EnterpriseOne 9.2 as an external, read-only REST client through the Application Interface Services (AIS) Server, requiring no software installation within the JD Edwards environment. Administrators must confirm that an AIS Server running on Tools Release 9.2.4 or later is associated with a Security Server, record its externally reachable HTTPS `/jderest` URL, configure trusted TLS certificates, enable standard EnterpriseOne username/password authentication, and create a dedicated least-privilege service account with inquiry-level access. The account must be authorized both to use AIS and to access the required EnterpriseOne applications, records, and fields, while firewall or proxy rules must permit inbound HTTPS from Unified.to’s designated regional egress IP addresses. Administrators should test authentication by requesting an AIS session token, investigate common issues involving connectivity, certificates, credentials, AIS permissions, EnterpriseOne security, or token expiration, and then securely provide Unified.to with the AIS URL, service-account credentials, and optional environment and role settings.

POS integration connects applications to retail and restaurant point-of-sale platforms such as Clover, Square, Toast, and Lightspeed, enabling access to sales, payments, inventory, locations, employee records, and time-clock data through a single authorized connection. Unified treats POS not as a standalone data category but as an integration spanning its Accounting, Payments, E-Commerce, and HR & Directory APIs, allowing each data type to use a specialized model rather than a simplified generic POS schema. The platform routes requests directly to source systems in real time without storing customer data, preserves provider-specific fields alongside normalized values, and offers raw data and passthrough access for unsupported unified fields. It can deliver native webhooks where available or virtual webhooks that detect changes at configurable intervals, supporting uses such as revenue reporting, payment reconciliation, workforce scheduling, staff synchronization, and multichannel inventory management. Support varies by provider and capability, with integration pages documenting available categories, fields, and event support across more than 142 POS integrations as of August 2026.

Unified.to describes how a product can use one authorized NetSuite ERP connection to retrieve and combine accounting, payment, shipping, and HR data for an up-to-date order-to-cash and fulfillment view. The approach scopes reads to customer subsidiaries, retrieves dedicated sales order and invoice records, reconciles payments through allocation data that includes applied amounts, currencies, and historical exchange rates, and follows item fulfillments to carrier tracking details. It can also associate expenses with employees through the HR & Directory API without requiring another authorization. The guidance emphasizes checking each ERP’s capability page because category and object support vary by platform, requesting source-intensive fields such as line items and allocations only when needed, and treating 501 Not Implemented responses as unsupported functionality rather than empty data. To keep views current, applications can subscribe to supported virtual webhook events or use incremental reads based on update timestamps, while accounting for NetSuite limitations such as unavailable delete and direct tracking events and the transition from a deprecated generic Order model to dedicated Salesorder and Purchaseorder objects.

A comparison of nine integration vendors argues that no provider offers a standalone ERP API category, instead combining accounting APIs, connector-specific actions, or custom integration infrastructure to access ERP data. Using vendor documentation reviewed in August 2026, it evaluates support for 11 major ERP platforms, connector maturity, public coverage visibility, multi-entity data modeling, and whether data is read live or from cached storage. The analysis claims Unified.to is the only vendor with live API integrations for all 11 benchmark platforms, although several newer enterprise connectors are read-focused or read-only, while competitors such as Apideck, Codat, Merge, Rutter, StackOne, Truto, Paragon, and Knit offer differing levels of accounting and ERP coverage. It emphasizes that advertised platform logos may not reflect writable endpoints, financial-ledger depth, named product editions, or support for subsidiaries and intercompany structures. The comparison identifies public field- and endpoint-level capability matrices as important for buyers, notes that some vendors cache customer data while others query source systems directly, and concludes that the appropriate choice depends on whether a product needs broad ERP coverage, deep support for a few accounting systems, connector-specific workflows, or fully custom models.

Unified.to’s Performance Management API enables products to read, create, update, and synchronize employee goals across platforms such as 15Five, BambooHR, HiBob, and Lattice through a standardized Goal object and a single connection ID per customer. The guide explains how normalized fields including progress, status, goal type, parent relationships, employee ownership, milestones, and weighting can support goal lists, OKR hierarchies, and quantified performance views while allowing interfaces to gracefully handle fields that vary by platform. It advises developers to verify per-integration coverage, distinguish unsupported functionality signaled by a 501 response from an empty result, and restrict editing features to supported write capabilities. Changes can be kept current through virtual webhook subscriptions where available or through scheduled incremental reads using update timestamps, while direct requests and writes operate against the customer’s source platform. It also recommends using real-time reads for specific known goals and maintaining a local synchronized database for broader searching, filtering, and cross-goal analysis.

Unified announced a Performance Management API that provides a normalized interface for reading employee goals, review cycles, performance reviews, and feedback, and for writing goals and feedback, across 15Five, BambooHR, Engagedly, HiBob, and Lattice. The API uses four shared objects—Goal, Cycle, Review, and Feedback—with platform-specific coverage documented through a capability matrix, while preserving access to platform-specific data through raw fields. Unified states that requests and writes are passed directly to each customer’s source platform without caching or storing end-customer data, supporting current data for sensitive performance records. The service also links performance objects to HRIS employee identities, offers standardized retrieval endpoints, filtering and incremental-read options, and webhooks where integrations support them, enabling products such as goal tracking, review workflows, recognition tools, compensation planning, engagement analytics, and AI-assisted manager check-ins.

ERP integration connects an application to customers’ enterprise resource planning platforms, enabling access to financial, employee, inventory, order, fulfillment, and payment data. Unified treats an ERP as a single authorized connection spanning five specialized APIs—HR & Directory, Accounting, E-Commerce, Shipping, and Payments—rather than as one flattened category, allowing deeper data models for each domain while requiring developers to identify the appropriate API for each object. Orders, purchase orders, and sales orders are handled through Accounting because they post to the ledger, while catalog and inventory data use E-Commerce. Unified routes real-time reads and writes directly to the source ERP without storing an intermediary copy, supports multi-entity accounting structures, exposes raw provider fields, and offers passthrough access to native ERP endpoints for unsupported data. Supported platforms include NetSuite, SAP S/4HANA Cloud, Microsoft Dynamics products, Oracle Fusion ERP, Sage Intacct, Acumatica, and others, with capabilities varying by each platform’s API. The discussion contrasts this category-based approach with ERP-labeled APIs, build-your-own integration infrastructure, and embedded iPaaS workflow tools.

Toast webhook subscriptions must be configured manually through the Toast Developer Portal or Toast Integrations because Toast does not provide a programmatic subscription API, and each subscription should use Unified’s workspace-specific Toast webhook URL. Prerequisites include a Toast partner account, a Unified Toast connection containing the restaurant GUID, and Unified native webhooks configured for the relevant object types and events. Toast subscriptions are created separately for each event category, with distinct secrets and separate sandbox and production configurations; Unified can optionally verify Toast’s HMAC-SHA256 signatures when category-specific secrets are stored in the connection metadata. Toast order, inventory, menu, restaurant availability, and partner events map to corresponding Unified accounting, commerce, payment, HRIS, and location objects, which Unified then distributes to matching native webhooks. Troubleshooting focuses on confirming the workspace URL and region, restaurant GUID and subscription marker alignment, existence of matching native webhooks, correct per-category signing secrets, and the expected behavior of menu events as catalog re-list signals rather than complete payloads.

Software integration connects separate applications so they can exchange data and trigger actions without manual copying, but the term also refers to customer-facing product integrations and to combining code modules during software development, making context essential. Commercial integration has no universal standards definition, and related terms such as application, system, data, API, and enterprise application integration overlap in scope and implementation. Integrations typically begin with user authorization, commonly through OAuth 2.0, then support data reads, writes, and event notifications through approaches including direct connections, hubs, API-led architectures, event-driven systems, file transfers, ETL/ELT, reverse ETL, iPaaS, embedded iPaaS, and unified APIs. Although many underlying technologies have specifications, webhooks lack a universal standard and newer agent-access protocols such as MCP are still evolving. Maintaining integrations is often more difficult than building them because API providers differ in authentication behavior, rate limits, pagination, error formats, version policies, webhook support, and deprecation practices. Decisions to build integrations internally or use a vendor depend on scale, customer-facing support requirements, write capabilities, data handling, and responsibility for ongoing API changes, while AI-agent access introduces additional concerns around authorization, tenant isolation, and protecting personal data.

TikTok Shop OAuth 2.0 setup is managed through Partner Center using an “app,” with the App Key serving as the client ID and the App Secret as the client secret, while the Service ID is TikTok-specific and not a standard OAuth credential. Developers must complete app-developer registration, then create an app under App & Service, select either a Public app for App Store distribution or a Custom app for direct seller use, configure its details and redirect URL, and enable API access. After creation, the app detail page provides the required credentials, while API permissions must be requested separately through Manage API and determine which data the application can access. TikTok Shop also separates US and non-US Partner Centers, meaning organizations serving sellers in both regions may need separate applications and credentials.

Unified has introduced a Customer Data Platform (CDP) API that allows users to access customer profiles, audience segments, and events across multiple CDPs with a single interface. This API supports real-time data retrieval directly from the customer's existing CDP without caching or storing end-customer data, ensuring data freshness and compliance with data residency requirements. The integration process is streamlined by normalizing six objects—Profile, Segment, Event, Source, Destination, and Activation—across different platforms like Twilio Segment, Adobe Experience Platform, and mParticle. Each CDP has unique API structures, requiring specific integration builds, and differences in identity models and data handling are addressed through Unified's standardized fields and authorization components. The API also supports webhooks for profile and segment changes, facilitating real-time feature updates without polling. Unified's approach simplifies cross-platform data handling, making it easier for developers to build applications that leverage customer data for AI-driven recommendations and audience targeting without the complexity of managing multiple distinct CDP integrations.

Rutter and Unified.to are platforms offering integrations for accounting, commerce, payments, and advertising, with key differences in data handling and integration coverage. Rutter syncs customer data into its own infrastructure, providing stored data access with potential latency issues, while Unified.to routes requests directly to source APIs, ensuring real-time data without third-party storage. Unified.to supports a broader range of integrations across 140 unique platforms, compared to Rutter's 47, and offers published pricing with unlimited connections. Rutter, however, is advantageous for specific needs like bank feeds, payment reconciliation on certain ledgers, and meeting ISO 27001 requirements. Unified.to’s architecture allows direct data delivery to clients' infrastructure, enhancing compliance and eliminating the need for a data migration if switching vendors, whereas Rutter's sync-and-store approach may benefit heavy analytical querying. Both platforms facilitate direct writes to source platforms, but Unified.to offers additional flexibility with its Passthrough API and Database Sync features, enabling robust data querying without retaining customer records.

The text discusses the integration of customer data platforms (CDPs) using a Unified API, which allows products to access customer audiences through a single connection regardless of the CDP used, such as Twilio Segment, Adobe Experience Platform, Lytics, or Tealium. It highlights the complexities of integrating with different CDPs due to varying data models and terminologies, and explains how the Unified API normalizes these differences into a single Segment object, simplifying the process by allowing developers to build a single integration that can handle multiple platforms. The text also emphasizes the importance of real-time updates through webhook subscriptions to maintain the current state of audience lists without relying on scheduled jobs. It addresses practical considerations such as handling different data fields, understanding compute modes for real-time versus batch processing, and ensuring compatibility across platforms with varying feature support. Additionally, the text offers insights into best practices for managing data synchronization and querying, and includes a section of frequently asked questions to clarify common integration challenges.

In July 2026, Unified.to achieved significant milestones, including winning the 2026 API Award for Best Business Software API, adding 108 new integrations to its extensive catalogue, and launching a Customer Data Platform API to streamline data management across various integrations like Adobe Experience Platform and Salesforce Data Cloud. Additionally, they introduced SAML SSO login to enhance security for enterprise customers and implemented the Core Unified API mode for better workspace management. A notable update was the support for the stateless 2026-07-28 Model Context Protocol revision, which simplifies request handling by eliminating the need for session initialization and enables efficient routing via HTTP headers. These advancements emphasize Unified.to's commitment to expanding integration capabilities while reducing the need for custom logic across different vendors.