From 62e1458e466459e71fcfda7c2af1ca8d83de293a Mon Sep 17 00:00:00 2001 From: Jeff Johnson Date: Mon, 10 Nov 2025 13:43:44 -0800 Subject: [PATCH] docs: update documentation for Gusto API v2025-06-15 upgrade --- CHANGELOG.md | 1 + docs/getting-started/getting-started.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 7df27dbfd..33d5b4543 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -23,6 +23,7 @@ ### Chores & Maintenance +- Upgrade to Gusto Embedded API v2025-06-15 - Bump react-hook-form from 7.65.0 to 7.66.0 - Bump typescript-eslint from 8.46.2 to 8.46.3 - Bump @ladle/react from 5.1.0 to 5.1.1 diff --git a/docs/getting-started/getting-started.md b/docs/getting-started/getting-started.md index 9f83674af..7031b5a33 100644 --- a/docs/getting-started/getting-started.md +++ b/docs/getting-started/getting-started.md @@ -40,7 +40,7 @@ When building with the React SDK, a backend proxy is required. React SDK compone 1. Authentication 2. Providing the user IP address for form signing operations -The React SDK is designed to mirror the [Gusto Embedded API Reference](https://docs.gusto.com/embedded-payroll/reference/whats-new-in-v2024-04-01) with a 1:1 mapping of endpoints. The SDK maintains consistent naming conventions, parameters, and response structures with the Gusto API. +The React SDK is designed to mirror the [Gusto Embedded API Reference](https://docs.gusto.com/embedded-payroll/reference/whats-new-in-v2025-06-15) with a 1:1 mapping of endpoints. The SDK maintains consistent naming conventions, parameters, and response structures with the Gusto API. Your proxy server simply needs to forward any incoming SDK requests to the corresponding Embedded API endpoints. The proxy's main task is adding the necessary authentication headers before forwarding the request onwards. Since the SDK requests are already in the Embedded API format, no extra endpoint mapping or request transformation is required.