403. The API publishes the change on the service bus (SBUS) NmsRoute channel, and core applies it when the event arrives, so 202 means published, not applied.route-id and index identify the connection, and the match fields and index in the body are ignored. Send only what changes: an omitted host keeps the stored one. A connection that does not exist returns 404.synchronous=yes, in the body or the query string, to wait up to 2 seconds for the change to be applied. You then get 200 with every connection of the route. If it is not applied in time, you get the usual 202 and the write still completes.Authorization: Bearer ********************synchronous=yes once the change is applied: every connection of the route.curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/routes/c2lwOjE4MDAqQCo/routecon/1' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"route-connection-integer-percentage": 40
}'[
{
"route-destination-match-pattern": "string",
"route-source-match-pattern": "*",
"route-class": "*",
"route-match-server-hostname": "*",
"route-connection-ordinal-index": 1,
"route-connection-translation-destination-user": "[*]",
"route-connection-translation-destination-host": "string",
"route-connection-integer-percentage": 50,
"route-connection-integer-cost": 0
}
]