POST request. This recipe walks through gathering those ids and making that request.
Gather the required ids
Every id below must belong to your organization (and, where noted, to the specific company you’re creating the project under):Create the project
With those ids in hand, create the project along with its street address:201 Created with the full project:
Conditional requirements
Two fields are required only in certain configurations, and one field is company-specific to look up:workflow_idis required when the company you’re creating the project under has workflows enabled as mandatory. The company resource doesn’t expose this setting, so the practical check is attempting the create without it — a422namingworkflow_idmeans it’s required. When required, it must be an active workflow belonging to that company (see List workflows).nameis required when the company requires project names. Otherwise it’s optional and can be left out or set tonull.company_custom_fieldsis required only when the company defines active required custom fields. Discover the field definitions with List company custom fields; every active, required field’s id must be present, and each value’s type must match its field’s type (aYYYY-MM-DDdate fordatefields, one of the field’soptionsforselectfields, a number fornumberfields,true/falseforcheckboxfields, or a string forinput/textareafields).
After creation
A brand-new project’snumber is a placeholder, literally the string "Lead" — set a real value with Update project, the only endpoint that can change it:
projects.created — see Webhooks. And if most of your projects originate from an external source (a web form, a lead vendor, a spreadsheet), consider Leads instead of calling this endpoint directly — a lead connection validates and converts inbound submissions into projects automatically.