Service Filings overview

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

Compliance filings (multi-state)

• Foreign Qualification
• Registered Agent (standalone)
• State Unemployment Insurance (SUI)
• Withholding Tax
• New Hire Reporting

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: the SwyftFilings External API OpenAPI specification 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 Services to list services enabled for your account:

Step	Method	Endpoint
List Services	GET	/service-carts

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).

Example: List services

GET {baseUrl}/service-carts
Authorization: Bearer {token}

{
  "success": true,
  "data": [
    {
      "slug": "foreign-qualification",
      "name": "Foreign Qualification",
      "description": "Service to file a foreign qualification",
      "allows_addons": false,
      "is_standalone": true,
      "nested_services": []
    },
    {
      "slug": "registered-agent",
      "name": "Registered Agent",
      "description": "Designate a registered agent in a specific state",
      "allows_addons": false,
      "is_standalone": true,
      "nested_services": []
    },
    {
      "slug": "state-unemployment-insurance",
      "name": "State Unemployment Insurance",
      "description": "Employer registration for state unemployment insurance",
      "allows_addons": false,
      "is_standalone": true,
      "nested_services": []
    }
  ]
}

Shared API flow

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

Step	Method	Endpoint
1. Service configuration and catalog	GET	/service-carts/{service}
2. Business classification (when NAICS is required)	GET	/business-classifications
3. Create order	POST	/orders
4. Get order (optional)	GET	/orders/{order_uuid}
5. Receive and respond Information Requests and Order Rejections over Webhooks

See Standalone Service Example for full request/response examples of each of these endpoints, and the per-product guides below for service-specific input_fields and catalog payloads.

Fulfillment and notifications

• Webhooks: Subscribe to order status, processing events and Rejection notifications (Information Requests). See Webhooks.

Review checklist (engineering and product)

Use this list before publishing integration guidance to partners:

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