What’s the proper way to inject AU DID formatting into the Agent Scripting REST API without triggering validation failures? Pushed a compliance prompt flow through Architect yesterday. Everything routes fine in the simulator, but production rejects the POST to /api/v2/scripting/scripts when the payload contains local 02-prefix numbers. Console throws a 400 Bad Request with invalid_number_format on the media step. Tried swapping the E.164 wrapper for ACMA dialing standards. API still chokes on that leading zero. Latency to the Sydney edge sits around 180ms. Packet loss is doing jack all here. Stripping the country code entirely breaks telephony provisioning on mypurecloud.com.au. Recording toggle is enabled for ACMA retention, which might be locking the schema. Logs show the request hits the gateway but bounces back before the script ID generates. Payload structure looks identical to the docs, except for the regional compliance flags. Here’s the exact error body:
{“error_code”: “invalid_number_format”, “message”: “DID must match E.164 without national prefix”}
Not sure how to force the parser to accept local switching rules.