Skip to main content

Standalone Service Example

Standalone services follow a multi-step fulfillment flow in which baseline information is collected at order creation, and additional requirements may be identified during processing.

This example uses the EIN application to illustrate the typical lifecycle. Other standalone services follow the same pattern, with service-specific requirements and statuses.

The following list summarizes the steps to submit a Standalone order.

StepMethodEndpoint
1. Get Service Configuration and Catalog informationGETView reference
2. Get Business Classification DataGETView reference
3. Create orderPOSTView reference
4. (Required for some services) Submit OrderPOSTView reference
5. Get order information (optional)GETView reference
6. Process order updates and requirements via Customer Portal-View reference

1. Get Service Configuration and Catalog information

Calling this endpoint will return the service configuration and catalog information for the Standalone order. Important information includes:

  • input_fields: The input fields that are required to create the Standalone order. You can build your front end dynamically based on this information.

    📝 Note: The input_fields response provides the baseline required fields for order creation. Additional requirements may be identified during processing and surfaced through follow-up actions.

  • catalog: The list of products that are available for the Standalone order.

2. Get Business Classification Data

Calling this endpoint will return the business classification data for the Standalone order. You will be required to provide a NAICS code from this list to create the order data in the next step.

3. Create order

Calling this endpoint will create the Standalone order whose status can be either Created or Under Review (status = "Created" or status = "Under Review"). Orders with Created status are just placeholders and do not represent valid orders that need to be processed by SwyftFilings. However, orders with Under Review status are valid orders that are ready to be processed by SwyftFilings.

Make sure to store the order uuid returned in the response to use it in the next steps.

⚠️ Important: If an order is submitted after creation (status = "Under Review"), this will trigger the order processing, so after this point SwyftFilings will start processing the order and you will receive updates via Customer Portal, emails and webhooks according to your integration setup.

4. Submit Order (required for some services)

📝 Note: Some standalone services don't have an option to add additional services to the order, therefore they don't need to be submitted. In those cases please skip this step. You can check the Get Order endpoint to verify the submit_date field to know if the order has been submitted.

Calling this endpoint will submit the Standalone order to SwyftFilings. This only applies to Standalone orders that allow you to add additional services to the order, here you send a list of products that will be added to the order and the order changes its status to Under Review.

⚠️ Important: This will trigger the order processing, so after this point SwyftFilings will start processing the order and you will receive updates via Customer Portal, emails and webhooks according to your integration setup.

5. Get order information (optional)

Calling this endpoint will return the order information. You can use this information to display the order details to the user or your internal systems.

6. Process order updates and additional requirements via Customer Portal

After the order is submitted, partners should implement a portal integration to support ongoing order updates and completion of any additional required information.

Depending on the service, jurisdiction, and order details, Swyft may identify additional requirements during processing. These will be surfaced to the customer through the Customer Portal.

Customers can:

  • provide any requested information or corrections
  • respond to follow-up requirements
  • track order status and progress

Processing continues once all required information is received.

Check Customer Portal Integration for more information.