April 2023 Summaries

To build data integrations for SaaS software using ADP services, developers must register an ADP Developer application and obtain OAUTH2 credentials. This involves creating an ADP Developer account, registering a new developer app by providing necessary details and agreeing to terms, and then obtaining the app credentials such as Client ID and Client Secret. These credentials are essential for authenticating the app and accessing ADP APIs, although directly using these APIs can be complex due to handling authentication, error management, and synchronization. Unified.to offers a more streamlined approach by managing these complexities, allowing developers to focus on their software while Unified.to handles the integration with ADP. Once registered, developers can activate ADP in Unified.to by entering their client ID and secret to facilitate better and scalable integrations.

Unified.to has introduced a new feature that allows users to send API call logs directly to their Datadog instance, enhancing observability by providing real-time insights into IT infrastructure and application performance. This integration simplifies the process for Unified.to customers by enabling them to paste their Datadog API key into their workspace settings and make a sample API call to confirm the logs are being sent. This feature supports both inbound API and webhook calls, with plans to expand the types of logs supported. Unified.to, known for its unified data model, facilitates seamless integration with third-party systems, eliminating the need for multiple API calls, thus improving efficiency for users.

Unified.to has introduced a feature allowing users to push API call logs directly to a Grafana Loki-compatible endpoint, enhancing external observability options alongside existing support for Datadog. This integration uses Loki's standard HTTP push API, providing easy setup through workspace settings where users can specify their Grafana site, authentication method, and API key. By sending logs to Grafana Cloud or a self-hosted Loki stack, users gain immediate visibility into their environment, facilitating quick debugging and error notifications. Unified.to supports inbound API and webhook calls, with plans to expand log type support based on user feedback. The Unified API simplifies integration with third-party systems through a unified data model, streamlining processes by eliminating the need for multiple API calls.

Ashby enables authentication through API Keys, which can be generated from the account settings by clicking "Admin" in the top navigation, navigating to Integrations > API Keys, and creating a new key with specified permissions. This process involves setting necessary API Scopes, such as "READ" and "WRITE" permissions for various functions, and copying the generated API Key. While generating the key is straightforward, maintaining reliable pipelines as more systems are added presents a challenge. Unified.to offers solutions in integration delivery, providing options like API data delivery, streaming webhooks, database sync, and MCP tools for AI agents, all designed to integrate seamlessly without forcing architectural tradeoffs. The platform supports integration across 463 integrations and 27 categories, and a demo can be booked to explore its capabilities further.

Generating a Lever API Key is an essential first step for connecting Lever to other platforms, requiring users to navigate their account settings and create new credentials. The process involves accessing the Integrations and API section, generating a new key, naming it, selecting permissions, and copying the key for use. However, the more challenging aspect is ensuring the reliability of data pipelines as customers expand their system integrations. Unified.to offers a solution with various data delivery options, such as APIs, streaming webhooks, and database syncs, which are designed to adapt to existing architectures without necessitating trade-offs. They provide a comprehensive integration layer with support for 463 integrations across 27 categories, and users can book a demo to explore how these solutions can simplify integration delivery.

To integrate with HiBob, obtaining a Service User ID and Service User Token is crucial for authenticating API requests, which can be generated from HiBob's account settings. The process involves creating a service user, forming a permission group tailored to the specific API operations needed, and setting the necessary permissions. Service users by default have no access permissions, requiring the creation of a dedicated permission group with only the necessary permissions for the intended API operations. Permissions can be categorized into access to features, people's data, and access rights to manage employee data, with varying levels of view, edit, and history access depending on the requirements. Additionally, for broader integration capabilities across multiple vendors, Unified.to offers a solution that simplifies this process by providing unified objects that work across numerous APIs, reducing the complexity and maintenance of vendor-specific auth flows and schema differences.

Dialpad allows authentication via an API Key, which can be generated from account settings by Company Admins on Pro and Enterprise plans. The process involves navigating through Admin Settings to create, name, and set expiration for the API Key, along with selecting additional scopes. This guide emphasizes that generating an API Key is a repetitive task when scaling integrations, but suggests using Unified.to to streamline the process with its extensive pre-built integrations, normalized schemas, and real-time delivery capabilities, eliminating the need for polling scripts and extensive maintenance.

Connecting SAP SuccessFactors to other platforms requires specific credentials, including a Username, Company ID, Password, and API URL, which can be generated by following a detailed step-by-step process. This involves identifying the appropriate API Server URL based on the user's data center, retrieving the Username and Company ID through the SuccessFactors interface, and configuring security settings to allow OData API access via basic authentication, with options for IP address allowlisting. The process results in the creation of these credentials, enabling seamless integration across multiple vendors, while tools like Unified.to offer a solution to streamline API management by providing a unified approach that reduces the need for maintaining vendor-specific configurations and accelerates the deployment of customer integrations.

HighLevel supports authentication through an API Key and Location ID, essential for connecting to its CRM and HRIS data at the sub-account level. This guide provides a detailed, step-by-step process for generating a HighLevel token-based connection using a sub-account API key in the Unified platform. The process involves navigating to the sub-account settings, creating a new integration with specified scopes, and securely storing the API token and Location ID. The guide emphasizes the necessity of having Admin or Owner access to the sub-account, as well as the importance of following each step carefully to avoid connection issues. Once the API token and Location ID are acquired, users can create a connection in Unified by pasting these credentials in the platform, allowing for efficient management of multiple vendor integrations through Unified's unified objects that streamline across 463 APIs.

Developers seeking to connect applications to Microsoft Active Directory or Entra ID require a Client ID, Client Secret, and Tenant ID for authentication purposes. The process begins with registering an application, which creates a trust relationship with the Microsoft identity platform, followed by generating a Client Secret for authentication in confidential client applications. Next, permissions must be configured for Microsoft Graph, requiring administrator consent, which can be granted tenant-wide if the application is already provisioned. Finally, authentication credentials are set up using the Client ID, Client Secret, and Tenant ID in Unified, a platform that simplifies integration across various APIs by providing unified objects, thereby reducing maintenance and enabling faster feature deployment.

To connect to Greenhouse, developers need to obtain an API Key and a Job board token for authentication, a process that involves navigating through Greenhouse's interface to generate and configure these credentials. This involves creating a "Harvest" API key via the Dev Center, setting necessary permissions, and optionally retrieving a job board token from the Job Boards & Posts settings. However, the real challenge lies in managing the diverse authentication flows and maintenance needs of different vendors, which Unified.to addresses by offering a real-time integration platform that simplifies the process. Instead of creating multiple custom connectors, Unified.to provides a single, secure API layer that integrates with numerous SaaS tools, with a pricing model that aligns with product usage, eliminating per-connection fees and setup charges.

Developers seeking to connect to Ceridian Dayforce require a Username, Password, and Client Namespace for authentication, which can be obtained by logging into Dayforce, navigating to the "Company" tab, and checking the "Client Namespace" field under "Settings". While acquiring these credentials is essential, the more significant challenge lies in managing numerous vendors with distinct authentication processes, schemas, and maintenance needs. Unified.to offers a solution by providing a real-time integration platform that replaces the need for multiple custom connectors with a single secure API layer across 27 SaaS tools. This platform offers usage-based pricing without per-connection fees or setup charges, allowing integration costs to scale predictably with your product.

Connecting ADP Workforce Now to other platforms requires generating an OAuth2 client ID, client secret, PEM certificate, and private key through the ADP API Central portal, which is accessible via a paid application. Users must log into their ADP account, access the portal, and either select an existing project or create a new one to obtain the necessary credentials and certificates. The process involves selecting development credentials and managing certificates to generate a PEM key, which is essential for establishing a connection. For more complex integrations, Unified.to offers solutions to streamline data delivery through APIs, streaming webhooks, or database syncs, providing a flexible integration layer that adapts to various architectures without forcing tradeoffs. The service supports 463 integrations across 27 categories and offers a demo to showcase how it simplifies integration delivery.

To connect iCIMS to other platforms, users must obtain an API Username, API Password, and Customer ID, which are essential for authentication. This process involves contacting iCIMS support to request these credentials, which, once provided, should be securely stored. After receiving the credentials, users need to verify access by entering the details to establish a connection to their iCIMS account. The guide highlights the complexity of managing multiple vendor integrations, each with unique authentication processes and maintenance needs. Unified.to offers a solution with a real-time integration platform that provides a single, secure API layer across 27 SaaS tools, simplifying the integration process and offering scalable, usage-based pricing without additional fees or long-term commitments.

Workable requires the generation of a secure API Token and Subdomain for authentication purposes, which can be done through account settings. The process involves accessing the "Integrations" section and clicking the "Generate new token" button to create an API access token, although the token type does not currently support certain scopes like r_employees. Additionally, users must locate their account subdomain in the company profile settings. Users have the option to revoke the access token, but they must generate a new one and update all scripts and applications using the previous token to maintain functionality. While this method covers the Workable system, scaling integrations can be cumbersome, requiring the process to be repeated multiple times. Unified.to offers a solution with 463 out-of-the-box integrations, which utilize normalized schemas and real-time delivery without the need for polling scripts or additional maintenance, significantly reducing integration time.

Choosing the right API framework for your application involves understanding the differences and use cases of REST, GraphQL, and gRPC. REST, which uses HTTP actions as verbs and typically JSON as a data format, is the most widely used framework for front-end to back-end communication, though its loosely defined structure can lead to disorganized implementations. GraphQL offers a more efficient querying language that can reduce the number of HTTP calls needed for data retrieval, making it appealing to some large companies despite its lower overall popularity compared to REST. gRPC, a newer entrant developed by Google, excels in speed and compact data transmission using the binary Protobuf format, making it popular for internal micro-services; however, its limited front-end support and understanding hinder its use for public APIs. Each framework has its strengths and weaknesses, and the choice may depend on specific project needs, with Unified.to's APIs being compatible with all three.