Create and manage a company benefit (plan-level) in Gusto Embedded Payroll
domain: gusto.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
List supported benefit types via GET /v1/benefits to get the canonical benefit_type enum values and whether each type supports employee and employer contributions.
Create a new company benefit plan using POST /v1/companies/{company_id}/company_benefits with the benefit_type, description, active flag, and whether the plan is employee-deductible.
Optionally set employer contribution defaults at the plan level; individual employee overrides are set at the employee_benefit level.
Activate or deactivate the plan by sending a PUT to /v1/companies/{company_id}/company_benefits/{company_benefit_id} with active set to true or false.
Retrieve the updated plan to confirm settings, then proceed to enroll individual employees.
Known gotchas
The benefit_type field uses a fixed enum; submitting an unrecognized type returns a 422 — always fetch /v1/benefits first to get valid values for the current API version.
Deleting a company benefit is not supported once employees are enrolled; you can only deactivate it, which stops future deductions but does not reverse prior ones.
Company benefits tied to carrier integrations (fully-insured medical) may require additional carrier setup outside the API before the benefit appears on pay stubs.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?