May 2026 Summaries

Accessing the Reddit Ads API involves registering an OAuth 2.0 application, requesting specific Ads-related OAuth scopes, and obtaining allow-list approval from Reddit's ads or partner team for full campaign management capabilities. Unlike the heavily restricted and monetized Reddit Data API, the Ads API has been expanded and refined, with the introduction of version 3, enhanced documentation, and a partner program to encourage ad integrations. Advertisers can use the Conversions API without full allow-listing, which simplifies server-side conversion event tracking. The approval process for full Ads API access is informal and often based on advertiser status or spending levels, with no public trial tier like Pinterest. By July 13, 2026, a new schema requirement mandates that all ad groups and Campaign Budget Optimization (CBO) campaigns include a conversion_pixel_id. Unified.to offers a single API solution to manage multiple advertising platforms, including Reddit, while handling OAuth credentials and operational details, although end advertisers must still navigate Reddit's allow-list approval independently.

Snapchat's Marketing API, open to advertisers, agencies, and developers since 2018, offers production access without the restrictive gating seen in platforms like Pinterest and Reddit. It uses OAuth 2.0 credentials instead of static API keys, requiring a client ID, client secret, access tokens, and refresh tokens, all managed through Snapchat Business Manager. This process eliminates the need for developer-token tiers or approval gates and allows users to directly register their OAuth app, request necessary scopes, and begin API calls. Key scopes include campaign management, conversions tracking, and public profile reads, with a straightforward authorization flow that contrasts with the more complex access models of its peers. Snapchat's refresh tokens don't expire but can stop working if user access is revoked or the client secret is regenerated. The API's stability since its launch makes it an attractive option for long-term integrations, while Unified.to offers a single API solution across multiple advertising platforms, abstracting the complexities of individual integrations.

Microsoft Advertising requires a combination of a Developer Token, OAuth 2.0 credentials from a Microsoft Entra ID app registration, and user authorization flow to access its API, as there is no single API key for access. In 2026, developers must choose between the soon-to-be-deprecated SOAP API and the newer REST API, with the latter being recommended for new integrations due to the SOAP API's feature freeze starting October 1, 2026, and complete decommissioning by January 31, 2027. The process involves creating an app registration in Microsoft Entra ID, requesting a Developer Token, and implementing OAuth user authorization, with Microsoft Advertising's REST API requiring specific headers for authenticated calls. Notably, Microsoft Advertising does not support service-principal OAuth flows, instead relying on delegated user OAuth, and offers a separate sandbox environment for testing. The document also highlights the importance of credential management, such as storing sensitive information securely and refreshing tokens proactively, while comparing Microsoft Advertising's approach with other platforms like Google Ads and discussing the potential benefits of using a unified API solution for managing multiple advertising integrations.

The process of obtaining Amazon Ads API access in 2026 involves navigating a complex setup that uses OAuth 2.0 through Login with Amazon (LWA) rather than a single API key, requiring five distinct credentials: Client ID, Client Secret, Access Token, Refresh Token, and Profile ID. The procedure spans two portals—developer.amazon.com for LWA Security Profile creation and the Amazon Ads Partner Network Console for API application—and necessitates application approval, which varies in duration depending on whether the applicant is a Direct Advertiser or a Tool Provider/Agency. Given the absence of a sandbox environment for the Advertising API, only production access is available, necessitating careful planning. The approval process for Direct Advertisers takes 2-3 business days, while it can take several weeks for Tool Providers and agencies due to a more thorough review. Amazon's API framework emphasizes secure credential handling, regional endpoint specificity, and proactive token refresh to address common error-prone areas such as account confusion and profile propagation delays. Unified.to offers an integrated solution that simplifies the complexities of Amazon Advertising's OAuth flow and credential structure by providing a single API across multiple advertising platforms, thus abstracting many of the ongoing maintenance challenges associated with Amazon's API.

Pinterest requires separate credentials for its Ads API, with OAuth 2.0 credentials necessary for general marketing activities such as managing campaigns, ad groups, and creatives, while a Conversions API (CAPI) token is used solely for server-side conversion event tracking. The process to obtain these credentials involves registering an app using a Pinterest Business account, navigating trial and standard access tiers, and ensuring the correct OAuth scopes are requested. OAuth credentials are user-centric and require periodic re-authorization, with a demo video often needed for standard access approval. The CAPI token, generated within Pinterest Ads Manager, is specific to server-side event tracking and not interchangeable with OAuth tokens. Pinterest's API model is distinct from Meta's, emphasizing user-centric access without a Business Manager equivalent. The Unified API offers a consolidated solution for managing Pinterest and other platforms, simplifying the credential handling and maintenance required for direct integration.

In 2026, the X Ads API, previously known as the Twitter Ads API, remains operational and distinct from the general X API, which underwent a significant pricing change. The Ads API is not affected by the $42,000/month enterprise pricing and continues to be available at no additional cost to approved developers. However, gaining access requires a separate application and approval process. The API is technically mature, with version 12 being the current iteration, but it exists within a platform undergoing numerous changes, including branding migrations and field-level schema updates. Engineers working with the X Ads API should anticipate a higher maintenance overhead compared to other platforms, partly due to the unusual reliance on OAuth 1.0a for write operations while other platforms have transitioned to OAuth 2.0. The API structure includes unique terminologies such as "Line Item" for what other platforms refer to as "Ad Group," and the core mechanic remains the promotion of organic Tweets as ads. Despite these complexities, the X Ads API provides capabilities for campaign management, reporting, audience syncing, and conversions tracking, all of which are managed through a hierarchical model that includes Accounts, Campaigns, Line Items, and Promoted Tweets.

The Trade Desk API access in 2026 is not publicly accessible and requires an existing commercial relationship with the company, such as being a customer, agency, or approved adtech partner. Unlike other ad platforms that use OAuth 2.0, The Trade Desk uses a credentialed API user model with long-lived tokens, managed through a closed partner infrastructure. API access requires approval from a TTD account team, potentially involving additional fees and contractual terms. The API supports various functions like campaign management and data integration, each with specific credentials and endpoints. Those without a direct relationship can access the API through agency partners or integration partners like Unified, which offer a single API for multiple ad platforms. The Kokai rebrand represents a UI evolution but does not change the underlying API structure or authentication methods.

In 2026, obtaining API access for Google's Campaign Manager 360 (CM360) requires navigating a complex process that emphasizes the use of OAuth 2.0 for authentication, specifically through service accounts for multi-tenant SaaS integrations. Unlike Google Ads, CM360 does not use API keys or a developer-token tier system, instead requiring Google's account team to enable API access at the account level. Each API call necessitates a userProfileId, which scopes the request and must be included in the URL path. The guide outlines steps for enabling the API in Google Cloud, creating service account credentials, and managing user profiles for each customer account. The service-account flow is recommended for multi-tenant SaaS, despite requiring manual setup for each customer, due to its stability and security advantages over user OAuth, which is more suited for single-tenant or internal tools. CM360's API structure maintains legacy DoubleClick naming conventions and demands careful management of service-account credentials and OAuth scopes to avoid common pitfalls like 403 errors. Additionally, Unified.to offers an alternative integration approach by providing a single API that abstracts away many of CM360's complexities, potentially easing the burden of maintaining direct integrations.

TikTok's Marketing API, as of 2026, requires a multi-step process for access, involving the creation of a developer app, OAuth 2.0 authorization, and passing a rigorous app review and data-security compliance check for production use. Unlike Snapchat and Pinterest, TikTok's API is highly gated, necessitating Business Center onboarding and business verification for higher-volume access. The API features a unique authorization pattern for Spark Ads, which relies on creator-granted codes, and does not allow for the hard deletion of creatives, instead supporting state changes. The US has not banned the API, but stricter approval processes and compliance checks reflect increased scrutiny. Developers planning to integrate TikTok's API must prepare for a lengthy approval process and ensure compatibility with both the Marketing and Events API, which have different authentication models. Unified.to offers a consolidated API solution for TikTok and other platforms, simplifying integration by managing OAuth and endpoint structures through a single authorization step.

The Display & Video 360 (DV360) API, part of Google's Marketing Platform, relies exclusively on OAuth 2.0 for authentication, eschewing traditional API keys or static tokens. For backend integrations, service account authentication is recommended, while three-legged user OAuth is suitable for multi-tenant SaaS where customers connect their own DV360 accounts. Access in DV360 is determined by user roles within its hierarchy of partner, advertiser, campaign, insertion order, and line item, without the need for userProfileId or developer-token reviews, which simplifies setup compared to other Google products like Campaign Manager 360. The API has specific OAuth scopes and hard rate limits, and integrating it involves enabling the API in Google Cloud, creating either service account or user OAuth credentials, assigning the necessary user roles in DV360, and managing access scopes carefully. Unified.to offers an alternative by providing a single API across multiple advertising platforms, simplifying integration and maintenance tasks such as credential management and role auditing for DV360.

In May 2026, Unified announced significant updates to its platform, including the introduction of Regional Sync, which provides fully segregated data environments across the EU, US, and Australia under one subscription, addressing data residency and compliance needs for global enterprise customers. The company expanded its integration offerings by adding full write coverage for QuickBooks Desktop across all core accounting objects and launched OpenAI Ads as part of its Advertising API, alongside existing integrations like Google Ads and LinkedIn Ads. Additionally, Unified enhanced its virtual webhook coverage for NetSuite across 27 objects, allowing teams to receive change events without maintaining polling logic, and extended its API capabilities across various CRM, ATS, HR, marketing, advertising, enrichment, and file storage systems. The updates also included OAuth2 sign-in authentication, expanded field-level capabilities for platforms like Sage Intacct and Zoho CRM, and significant improvements in pagination across multiple objects, further streamlining enterprise processes by reducing the need for vendor-specific custom logic.

To obtain a Meta Ads API key, users must navigate a detailed process involving token management, app creation, and access verification, as Meta Ads does not issue a permanent API key. Initially, users generate a short-lived access token via a Meta Business app, which expires within one to two hours, necessitating an exchange on the server-side for a long-lived token lasting about 60 days. For continuous automation, a System User token, designed for long-running backend tasks, is preferable. Production use requires Advanced Access, entailing App Review and Business Verification, a process that can take several days to weeks. Meta is also phasing out some legacy APIs, urging users to migrate to newer structures, while emphasizing the importance of securing credentials and managing permissions efficiently. Unified.to offers a simplified integration model that consolidates various ad platforms, including Meta Ads, into a single connection, managing the token lifecycle and authorization across platforms seamlessly.

Obtaining a Google Ads API key involves navigating a complex setup that requires four credentials: a developer token from a Google Ads manager account and OAuth credentials, including a client ID, client secret, and refresh token from Google Cloud Console. The process is complicated by the need to apply for a developer token upgrade from Test Account to Basic or Standard access, which Google reviews, often causing delays. Understanding the role of the login-customer-id is crucial to avoid permission errors when managing client accounts. Additionally, platforms like Unified offer solutions by providing a single integration model for managing multiple ad platforms, including Google Ads, through a normalized Advertising API, simplifying cross-platform performance tracking and campaign management.

Airtable has transitioned from using API keys to personal access tokens (PATs) as of February 1, 2024, necessitating users to create PATs for authentication in the Builder/Developer hub. These tokens are configured with two-dimensional permissions: scopes, which define actions the token can perform, and base/workspace access, which determines the data it can interact with. Misconfigurations in these settings often lead to 401/403 errors, and the token is displayed only once at creation, requiring immediate storage. For scenarios involving multiple users connecting their Airtable accounts, OAuth 2.0 should be used instead. This change aligns with practices from companies like Mailchimp and Stripe, distinguishing between internal use and customer access. Unified.to offers a solution to manage these credentials across multiple integrations, streamlining the connection process for products that interact with various applications.

To obtain a Mailchimp API key, users must log in to their Mailchimp account, navigate to the profile section, and follow the path Profile → Extras → API keys, where they can create and name a new key, making sure to copy it immediately as it will only be displayed in full once. It's crucial to note that every API key ends with a data center suffix that dictates the API base URL, and forgetting this suffix is a common mistake leading to connection errors. Mailchimp advises using an API key for personal integrations while recommending OAuth 2.0 for multi-tenant applications where multiple users connect their accounts. Additionally, the text emphasizes the importance of treating API keys like passwords by keeping them secure, using descriptive names for each integration, and revoking keys that are no longer in use. Unified.to is introduced as a solution to streamline integration with Mailchimp and other platforms by providing a single unified Marketing API that simplifies the authorization process and reduces the need for complex credential management.

To obtain your Stripe API key, users must log into the Stripe Dashboard and navigate to Developers → API keys, where they can access their publishable and secret keys, differentiated by test or live modes, which often cause integration issues due to confusion between the two. Stripe provides three types of keys: publishable keys for client-side UI, secret keys for server-side privileged calls, and restricted keys with limited permissions recommended for specific integrations. Keeping keys secure is crucial, requiring server-side storage, using environment variables, and rotating keys if compromised. When switching from test to live environments, users need to ensure they replace all test keys with live ones to avoid errors. For those managing multiple billing platforms, Unified.to offers a solution by providing a consistent integration framework that simplifies authorization and event handling, allowing teams to manage various payment and billing services efficiently.

To access the LinkedIn Ads API, users must create a LinkedIn Developer app, undergo an approval process for the Advertising API, and utilize a 3-legged OAuth flow to obtain access tokens, as there is no simple API key. This process involves submitting a detailed access-request form, specifically for qualified ads management, reporting, or marketing-platform use cases, while generic data collection requests are typically rejected. The OAuth flow requires an exact redirect URI and is necessary for any ads or marketing activities, as the 2-legged client-credentials flow is not permitted for these APIs. Developers must securely store client secrets, manage tokens per member, and adhere to LinkedIn's rate limits. Unified.to offers a streamlined solution by collapsing multiple ad platforms into a single integration, handling platform-specific authorization processes, and providing a unified API for cross-platform ad management.

Google Workspace integrations offer two authentication methods for connecting with the Unified API: the standard OAuth2 flow and a service account for server-to-server access without user intervention. This guide focuses on using a service account, detailing the steps to create it, enable necessary APIs, and grant access to data either through domain-wide delegation or resource sharing, depending on the API requirements. For most Workspace data like Gmail, Calendar, and Drive, the service account must impersonate a user via domain-wide delegation, requiring the configuration of OAuth scopes for each integration. The process involves creating a Google Cloud project, generating a service account key, and configuring domain-wide delegation or sharing resources directly with the service account's email for APIs like Google Analytics or Merchant Center. The key file, which includes the service account email and private key, is essential for configuring API calls in the Unified API, allowing secure and automated interactions with Google services. Proper security measures, such as storing the private key in a secret manager and authorizing only necessary scopes, are crucial to maintaining data security and minimizing risks.

An LLM gateway serves as an intermediary infrastructure layer between applications and various model APIs such as OpenAI and Google Gemini, managing model routing, failover, observability, latency, and AI expenditure across providers. While gateways efficiently handle networking issues, they do not address the challenge of providing models with authorized access to current customer data from CRM, ATS, and other business integrations. The core problem lies in obtaining and normalizing this data for real-time use, which is critical for AI features that require operational data from customer integrations. Solutions include building custom integrations, using unified integration layers like Merge or Unified, or leveraging real-time reads and writes from source APIs. The market for LLM gateways and unified APIs is evolving, with platforms moving towards integrating data access and model routing as cohesive solutions, though challenges such as latency and cost still complicate real-time data access. The priority for AI infrastructure should be resolving data access issues before optimizing model routing, as the former determines the utility of AI features.

OpenAI's Ads API enables users to manage advertising campaigns within ChatGPT through programmatic interactions, requiring a specific API key distinct from the general OpenAI developer keys. This API is currently in beta, limited to U.S. advertisers, and mandates prerequisites like account verification and billing setup before an API key can be issued through the OpenAI Ads Manager. The key functions as a Bearer token for authentication and is scoped to a single ad account, necessitating separate keys for multi-account management unless coordinated through OpenAI support. The API supports comprehensive campaign management, including creation, modification, and reporting of campaigns, ad groups, ads, and creative assets. It operates on a prepaid credit model, where a zero balance halts billable API calls, and it enforces rate limits with specific strategies for handling request overloads. OpenAI Ads can be integrated into a unified advertising platform alongside other major ad networks like LinkedIn, Google, and Meta, using a consistent connection ID pattern for streamlined management across different advertising integrations.

Knit and Unified.to are both unified API platforms that offer multi-category integration capabilities with pass-through architectures, providing unique strengths tailored to different user needs. Knit offers a more accessible entry point with a true free tier and low-cost options for smaller-scale HR-focused integrations, emphasizing deep field-level normalization in HR and related systems, and provides managed integration support at higher tiers. Unified.to, on the other hand, boasts a broader integration catalog across 26+ categories, including non-HR domains, and offers robust enterprise security features like SAML SSO and customer-managed secrets without tier gating, which makes it more suitable for high-volume, multi-category use cases with stringent compliance requirements. Both platforms offer similar no-storage data policies and first-party MCP capabilities, but they differ significantly in integration breadth, pricing structures, and the operational model of data delivery, influencing the choice depending on specific business requirements such as integration needs, security preferences, and budget constraints.

To integrate AI agents with Workday for accessing worker data and other functionalities, a Workday MCP server is necessary, although Workday does not provide an official server. Users have three options: building their own server for full control, using hosted vendor MCP servers for fast prototyping with potential vendor lock-in, or opting for a unified MCP server like Unified.to for broad integration coverage without infrastructure maintenance. All paths require setting up an Integration System User and registering an API client with Workday, including OAuth2 setup. Each method presents different trade-offs in terms of control, speed, maintenance, and cost, with the choice largely depending on whether Workday is the sole integration or part of a broader ecosystem. The unified approach typically offers the most flexibility and scalability, especially for agents that may require multiple integrations beyond Workday.

Unified.to provides customers with private support channels via Slack, Discord, and Microsoft Teams, catering to different organizational needs. Slack Connect is the preferred method for private support, where customers can request their account manager to create a channel for their team. Discord offers both public and private channels, with private ones set up upon request for dedicated integration efforts. For enterprise customers restricted by IT policies from using Slack or Discord, Microsoft Teams is available, necessitating configuration via Microsoft Entra B2B direct connect. This setup allows seamless collaboration without adding external users as guests, maintaining each organization's directory privacy. The detailed guide outlines the steps for enabling B2B direct connect, which requires Microsoft Entra credentials and specific configuration steps to allow access for Unified.to users and applications. This setup ensures that both inbound and outbound access are configured for resource sharing, with any changes easily reversible.