Skip to main content

Partner products overview

This section documents how to discover, order, and fulfill partner standalone services through the SwyftFilings External API.

Compliance filings (multi-state)

Tax and governance documents

State-specific field requirements and catalog pricing are returned by the API for the jurisdiction you select. Use State requirements reference together with the product guides below.

Validated against: OpenAPI api.json and API Reference as of April 2026. Published enums may lag behind your sandbox; always confirm service slugs and catalog SKUs in your environment.

Discover service slugs

Partners do not hard-code product names. Call Get Service Carts to list carts enabled for your account:

StepMethodEndpoint
List cartsGETView reference

Each item includes slug, name, description, allows_addons, and is_standalone. Use the slug that matches the product your partner agreement includes (labels may vary slightly by partner program).

Shared API flow

All three products use the same core endpoints as Standalone Service Example:

StepMethodEndpoint
1. Service configuration and catalogGETView reference
2. Business classification (when NAICS is required)GETView reference
3. Create orderPOSTView reference
4. Submit order (if the service uses add-ons / submission)POSTView reference
5. Post-checkout fields (optional)GETView reference
6. Get order (optional)GETView reference
7. Customer PortalSwyft Customer Portal Integration

Fulfillment and notifications

Review checklist (engineering and product)

Use this list before publishing integration guidance to partners:

  1. Sandbox JSON: GET /service-carts returns the expected service for each product; GET /service-carts/{service} returns input_fields and catalog for a test state.
  2. Create order: POST /orders succeeds with the documented service value and representative business_data for each product.
  3. Submit (if applicable): POST /orders/{order_uuid}/submit accepts the catalog sku values you intend to sell.
  4. State coverage: Product confirms any states that are not offered or require a manual exception; document those in State requirements reference.
  5. Copy: Product approves customer-facing descriptions in these pages.