Developer FAQs

General

What’s required to launch an integration?

Requirements can vary by tier but we require the following for all integrations at minimum to launch:

  1. API integration between your software and Gusto with the ability to create a new Gusto company (company provisioning) and OAuth2 to enable the integration
  2. Video walkthrough of the end-to-end experience of the integration once it is built (example)
  3. Integration instructions to use in Gusto Help Center article (e.g Integrate with Partner)
  4. Partner/Gusto Help Center article (e.g. partner.com/help/gusto)
  5. Generate co-branded landing page and tracking URL that can track converted customers (e.g. partner.com/gusto)
  6. Partner Terms of Service URL (e.g. partner.com/tos)
  7. 120 Character Platform Description (for Integrations page)
  8. 75 Word Platform Description for App Directory
  9. 3-5 images of the application in PNG format (minimum 1160 x 778 px in landscape)
  10. 3-5 images of the integration in PNG format (minimum 1160 x 778 px in landscape)
  11. Square dimension company logo in SVG (preferred) or PNG image format type with no background (i.e., “transparent”); JPEGs will not be accepted.

What kind of support will I get when building my integration?

We have a fully staffed Developer Relations team to assist in the build process. Reach out to developer@gusto.com with questions.  SLA for a first response depends on the tier.

How long does it usually take for a partner to build?

It depends on the type of integration, but given the state of the Gusto API the integration build typically takes between 1 and 2 months from the time your demo keys are issued to the time your production keys are issued (includes quality review). We recommend scoping your integration before you start building, and be sure to reference our Quality Review overview for best practices, requirements, and a preview of the approval process.

Can I make test calls in production after my integration has passed QA and launched?

We cannot support demo or test accounts in production at this time since our Assurance team will not approve accounts for testing. The APIs in demo are the same in production so further testing should be completed in demo.

Previous: Developer FAQs | Next: Getting Started