API client libraries

Gusto Embedded offers official client libraries for several programming languages to help you integrate with our API quickly and reliably. These libraries handle authentication, request formatting, error handling, and provide convenient methods for accessing all Gusto API endpoints. We also offer a React SDK for frontend development.

Frequently asked questions

Why use a Gusto Embedded client library instead of direct API calls?

Faster Implementation

• Skip boilerplate code for auth, error handling, and serialization
• Start building business logic immediately
• Reduce your time-to-launch by 2-3 weeks

Reduced Risk

• Built-in best practices for rate limiting and retries
• Consistent error handling
• Request validation before submission

Developer Experience & Maintenance

• Stay compatible with API versioning and updates
• Simplified upgrade path
• Type-safe interfaces with IDE autocompletion and inline documentation
• Minimal learning curve for new team members

Get to market faster while building a more reliable, maintainable integration. Focus your engineering resources on your core product instead of API infrastructure maintenance.

When should I use direct API calls instead of a Gusto Embedded client library?

You may want to consider building your own client library and making direct API calls to the Gusto Embedded API if:

• You need deep customization beyond what our clients provide
• Your tech stack has specific requirements our clients don't address
• Your team has extensive experience with our API and unique workflow needs

Which API version do these libraries support?

API clients support v2024-04-01 and later.

How do I report issues or request features?

Each repository (linked above) has an Issues section where you can report bugs or new feature requests. You can also get in touch with your Gusto Embedded representative to pass the feedback directly to the team.

How often are the libraries updated?

Updates are released automatically within 24 hours of backwards-compatible changes to our documentation. For a new dated version of the API, we aim to make API clients available within a week. We will continue to maintain legacy dated versions of the API clients as separate packages for as long as that version of the API is stable.

What does an API client being in beta mean?

Beta libraries have complete API coverage but may undergo interface changes before reaching v1. v1 libraries have stable interfaces.