202 on an instance whose NsHttpStatusCodeSuccess* settings are set to 202, and 200 where they are left at the default — the same convention every other v2 write follows. Either way the write is synchronous and already committed when the response is sent: a read issued immediately afterwards sees it. The 202 does not mean queued work.Authorization: Bearer ********************curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/parks' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"park": "5000",
"description": "Park Lot 1",
"domain": "example.com",
"site": "HQ",
"department": "Front Desk"
}'{
"code": 0,
"message": "string"
}