Sandbox vs. Production
The Sandbox environment enables you to familiarize yourself and experiment with the Middesk API before going live in a Production environment. Listed below are some key differences between the two environments:
Depth of report information
Middesk provides a rich set of information for its Businesses. In Production, a Business could have a significant number of Resources associated with it such as multiple registration records, multiple addresses, multiple officers, and so on. The Sandbox environment provides enough information to build an integration, but the variance in the data that is returned is limited in order to address the most common integration use cases.
Business lifecycle
As referenced in the Lifecycle of a Business section, Middesk transitions a Business through multiple statuses, from pending
to in_review
. The Sandbox environment supports all of these statuses, with the exception of the in_audit
status. When building in Sandbox, it's important to take this difference into consideration.
Documents
In Sandbox, Documents can be ordered for every Business that is created. Ordering Documents automatically is a premium feature which must also be enabled in Production. If interested in learning more, please contact sales.
Liens
In Sandbox, Liens can be ordered for every Business that is created. Ordering Liens Searches automatically is a premium feature which must also be enabled in Production. If interested in learning more, please contact sales.
Litigations
In Sandbox, Litigations are not automatic. Ordering litigations is a premium feature and to enable the support in Sandbox, it has to be enabled in production and configured to order automatically. If interested in learning more, please contact sales.
Additional features
Business Batches
Businesses can be created in Batches in both the Sandbox and Production environments. Use this feature to create many businesses at once, and provide attributes as detailed in the table above to trigger different verification scenarios as desired.
Industry Classification
Classifications can be created for Sandbox businesses if a website URL is inputted or as stand-alone classifications. For both products, the possible inputs to get different results are described below:
Website URL | Results |
---|---|
Contains highrisk | Includes a result in a high-risk category. |
Anything else | Results only in low-risk categories. |
Subscriptions
To test subscriptions, create a business with the inputs described below. The business will automatically have a subscription with the corresponding event type. After a minute, the business and its records will be updated accordingly to simulate the occurrence of that event, which you can receive by creating a webhook or polling for updates.
Event Type | Input Field | Value | Description |
---|---|---|---|
watchlist_result.created | Business Name | Watchlist Result Created Inc | A new Watchlist Result will be created for the Business |
tin.retrieved | TI | 111222333 | The TIN will initially be unknown and then become verified. |
Lien Filing
To test Lien Filing, you'll need to have Lien Filing enabled in production. If it is not currently enabled, you can contact [email protected] to get that set up. Once enabled, you can test with the File a Lien endpoint in Sandbox. Approximately thirty seconds after you hit the File a Lien endpoint, we'll transition the Lien status to filed
to mimic the time it takes Middesk to process your request. At this point, a production filing would have been submitted to the government, but no UCC-1 Document would be associated with the Lien, and this is the case in Sandbox too. After approximately another thirty seconds, we'll transition the Lien status to open
to mimic the time it takes the government to process the filing. At this point, a production filing would have a UCC-1 document, and a blank UCC-1 document will be present on the Lien in Sandbox to reflect this. lien.updated
Webhook Events are sent when the Lien status changes.
User Roles and Permissions
Each Middesk user has a role that allows for specific capabilities:
- Member: Basic team member; can create and view Businesses
- Developer: Includes all Member privileges as well as the ability to view (and edit where appropriate) API Keys, Webhooks, APILogs, IPAllowLists, and add Batches
- Admin: All privileges; including Developer privileges as well as the ability to add team members and to customize Policies
Updated 7 months ago