synchronous to yes in the request body to block until the write has been applied and is readable, and receive a 200 with the resource instead of a 202. Route writes are published to the SBUS NmsRoute channel and applied asynchronously, so without this flag an immediate read-back can miss the record. The API polls for up to 2 seconds; if the write has not landed by then the usual 202 Accepted is returned and the write still completes normally. Note that synchronous must be sent in the JSON body — including on DELETE — as query parameters are not read for write methods.Authorization: Bearer ********************synchronous=yes and the write has been confirmed readable.curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/routes/' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"route-destination-match-pattern": "string",
"route-source-match-pattern": "*",
"route-class": "*",
"route-match-server-hostname": "*",
"route-is-enabled": "yes",
"description": "string",
"route-method": "fixed",
"synchronous": "no"
}'{
"route-id": "string",
"route-destination-match-pattern": "string",
"route-source-match-pattern": "*",
"route-class": "*",
"route-match-server-hostname": "*",
"route-is-enabled": "yes",
"description": "string",
"route-method": "fixed"
}