Choosing an industry

The create-company endpoint classifies a company by NAICS through the industry field. Each value maps to a single classification, so what you send is precisely what the company is filed as. Source the value from List NAICS codes: pick an entry and send its industry label verbatim on the create-company request. Treat the reference list as the source of truth rather than hard-coding labels.

{
  "doolaCustomerId": "31pLCw7sN2aQ9fJkRtY3vXbHmLe",
  "state": "WY",
  "...": "...",
  "industry": "Custom Computer Programming Services"
}

The create response and Get a company echo the resolved industry, so you can confirm the classification that was persisted.

Errors

Send industry on every create; a blank string counts as absent. Failures come back as 400 E_VALIDATION_FAILED in the standard validation envelope; branch on error.fields.industry.code, or on error.fields.naicsCode.code if you still send naicsCode without industry. The deprecated naicsCode field is still accepted for backward compatibility: a request with no industry succeeds if it carries a valid naicsCode, and when both are sent industry wins and naicsCode is ignored. Don’t build on it. Its removal will be announced in the changelog.

HTTP	Field code	Meaning
400	`E_INDUSTRY_INVALID`	`industry` not an entry in the reference list, or neither `industry` nor `naicsCode` sent. Reported on `error.fields.industry.code`
400	`E_NAICS_INVALID`	No `industry`, and the deprecated `naicsCode` is not a valid NAICS code. Reported on `error.fields.naicsCode.code`

{
  "payload": null,
  "error": {
    "code": "E_VALIDATION_FAILED",
    "message": "one or more fields are invalid",
    "requestId": "4bf92f3577b34da6a3ce929d0e0e4736",
    "fields": {
      "industry": { "code": "E_INDUSTRY_INVALID", "message": "invalid industry" }
    }
  }
}

See Errors for the response envelope and the global codes.

Get started

Core concepts

Reference

API reference

Help

Updates

Errors

​Errors

Errors