Opens the EIN application and answers what it owes.

POST /v1/company/ein

Company → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/company/ein`
Method	`POST`
Operation	`post_company_ein`
Auth	`Authorization: Bearer $HANZO_API_KEY`

The answer states whether it can be filed ONLINE, because that is the fact deciding whether the customer waits a sitting or several weeks — and it names each form with what that form is for, so nobody has to already know what an SS-4 is to understand why they are signing one.

Request

7 fields, body application/json (required).

Field	In	Type	Required	Description
`expedited`	body	boolean	—	Expedited asks for prioritised handling.
`naics`	body	string	—	NAICS is the six-digit code for what the business does.
`responsible`	body	Responsible	—
`responsible.country`	body	string	—	Country is where they reside, ISO 3166-1 alpha-2.
`responsible.email`	body	string	—	Email reaches them for signature.
`responsible.name`	body	string	—	Name is their full legal name as the IRS will hold it.
`responsible.usTaxId`	body	boolean	—	USTaxID reports that they hold an SSN or ITIN.

Response

Status	Body	Meaning
`200`	EIN	ok

200 body — 15 fields.

Field	In	Type	Always	Description
`expedited`	body	boolean	—	Expedited reports that prioritised handling was asked for.
`forms`	body	Form[]	—	Forms are the forms this application owes, with what each is for.
`forms[].code`	body	string	—	Code is the IRS designation, e.g.
`forms[].name`	body	string	—	Name is the form's own title, so a reader need not already know the code.
`forms[].signed`	body	boolean	—	Signed reports whether we hold the signature.
`forms[].why`	body	string	—	Why states what this form is for in this application — the same form is owed for different reasons on different paths.
`naics`	body	string	—	NAICS is the six-digit code for what the business does.
`number`	body	string	—	Number is the issued EIN, absent until the IRS issues it.
`online`	body	boolean	—	Online reports that this application can be filed with the IRS online and issued in a sitting, rather than signed and posted.
`responsible`	body	Responsible	—
`responsible.country`	body	string	—	Country is where they reside, ISO 3166-1 alpha-2.
`responsible.email`	body	string	—	Email reaches them for signature.
`responsible.name`	body	string	—	Name is their full legal name as the IRS will hold it.
`responsible.usTaxId`	body	boolean	—	USTaxID reports that they hold an SSN or ITIN.
`status`	body	string	—	Status is how far it has got.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

import { Configuration, CompanyApi } from 'hanzoai';

const api = new CompanyApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postCompanyEin({ expedited: false, naics: "<naics>" });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import CompanyApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = CompanyApi(client).post_company_ein(expedited=False, naics="<naics>")

cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)

resp, _, err := client.CompanyAPI.PostCompanyEin(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_cloud::apis::{configuration::Configuration, company_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = company_api::post_company_ein(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.CompanyApi;

ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));

var result = new CompanyApi(client).postCompanyEin();

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

curl -X POST https://api.hanzo.ai/v1/company/ein \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "expedited": false,
       "naics": "<naics>"
     }'

The door reaches company through the company tool, which names its 22 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "get_company"
         }
       }
     }'

Company API · All Hanzo APIs · Interactive reference

Opens the EIN application and answers what it owes.

Request

Response

Examples

On this page