POST /tickets not backwards compatible

Develop, Build & Integrate
1

I posted the body below to /crm/v3/objects/tickets and it responded with 201 Created
I posted the same body to /crm/objects/2026-09/tickets and it responds with 400 Bad request. See error below.
Since I want to create tickets from an external system, I dont want the external system to know about owners/users. Is this as designed or a flaw in the newer api?

Request body:
{
"properties": {
"subject": "test subject",
"content": "test body",
"hs_pipeline": "0",
"hs_pipeline_stage": "1",
"hs_ticket_priority": "LOW",
"source_type": "FORM",
"country": "NL",
"product": "My product"
}
}

Response from /crm/objects/2026-09/tickets

{
    "status": "error",
    "message": "Cannot create object with type: TICKET. The following required properties were missing: [hubspot_owner_id]",
    "correlationId": "01a1a118-a997-71ad-981a-84c716a62016",
    "category": "VALIDATION_ERROR"
}
2

I need to elaborate a bit here.

  • Manually, tickets can be created without an owner.
  • On a free hubspot account, both requests succeed.

So I’m looking for the cause in my setup.

3

Hey @wvhooijdonk,

Welcome to the Community!

Since the older endpoint accepts the same body, it’s worth looking at what changed between the two API versions. Here are a couple of resources that may be able to point you in the right direction!

I’m tagging a few folks from the community to see if they have some more insight on this!

Hey @Alex_Boissonneault, @evaldas, @MichaelMa – have you come across this before?

Thanks!

Sam, Community Manager

5

I have an update.

In the ‘create ticket form’, the ‘owner’ property/field was set to required.
Removing the requirement solved the issue (tested).