The CorpNet Business Formation API lets partners form LLCs, corporations, and other entity types in any U.S. state — with order creation, status polling, document handling, and request-for-information (RFI) management through a single REST API.
Where to start
| If you want to… | Go here |
|---|---|
| Onboard for the first time | Getting Started with the CorpNet Business Formation API |
| Understand the API at a high level | Overview |
| See the package response shape | Business Formation Object |
| Track orders through phases and statuses | Order Lifecycle |
| Set up authentication | Authorization and API Key |
| Find common errors and gotchas | FAQ |
Endpoints
| Operation | Method | Reference |
|---|---|---|
| Retrieve available formation packages | GET | Get Formation Packages |
| Create a new formation order | POST | Create a Business Formation Order |
| Get order summary (price + products) | GET | Get Order Summary |
| Get full order details | GET | Get Full Order Details |
| Update an existing order (RFI response) | PATCH | Update Business Formation Order |
| Cancel an order | POST | Cancel a Business Formation Order |
| Download a filed document | GET | Download Order Document |
| Upload a partner-supplied document | POST | Send Order Document |
Hosts
- Production:
https://api.corpnet.com - Staging:
https://api.staging24.corpnet.com
Both Business Formation and Tax Registration APIs share these hosts.
Authentication
Bearer token, issued by CorpNet during partner onboarding. The same token authenticates both APIs; entitlement follows your partner agreement.
Authorization: Bearer <your_api_key>See Authorization for the full auth model and error semantics.
Notes on the response contract
- POST
/create-order201 echoes the full submitted order back atdata.partnerOrder.*, plus the assignedorderGuid. The order GUID lives atdata.partnerOrder.orderGuid— parsers readingdata.orderGuidwill get null. - Response bodies are double-JSON-encoded — the HTTP body is a JSON-encoded string containing JSON, so clients may need to decode twice. The
Content-Typemay also betext/plainrather thanapplication/json. See FAQ → Why is my response body a string instead of JSON? for code samples, and the autogen Create Order reference for endpoint-specific examples. - Mixed casing on Salesforce-projected responses.
GET /order-summaryprojects from CorpNet's underlying Salesforce records and uses Salesforce JSON conventions — including the capitalizedIdfield. Plan for the casing inconsistency or use case-insensitive parsing. - Async population on
GET /get-order. Child fields (contact, businessAddress, companyInfo) may briefly read null right after order creation due to the underlying Salesforce backend's eventual consistency. Workflow-phase-dependent fields (orderFilingType,filedDate,formedEntityId) stay null until the order phase advances pastOrder Received.
For request bodies, response schemas, error semantics, and the full set of conditional field rules, see the autogen endpoint references above.