r = requests.post("/api/v2/gdpr/requests", params={"deleteConfirmed": "true"})
# 405 Method Not Allowed
POST on the GDPR erasure request endpoint returns 405. The audit log pipeline requires the redaction timestamp, which the response omits. Analytics traversal succeeds, but the softDelete flag fails to toggle on the profile model. Fallback PATCH with null payloads only persists empty strings to the transcript cache. The Python consumer blocks indefinitely on the 202 handshake, breaking compliance exports.
Hey everyone,
headers = {"Content-Type": "application/json", "X-Genesys-Edge-Bypass": "true"}
payload = {"redaction_requested": True, "timestamp": int(time.time())}
r = requests.post(f"/api/v2/gdpr/requests", json=payload, headers=headers)
That 405 is classic behavior when the Edge HTTP routing table bails on unsupported methods right as you hit a primary WAN split. When the pair flips over to local survivability, the standby node is lagging on syncing the method whitelist. We’re seeing this routing table lag consistently on 2024.6.1 builds.
If you’ve been following the thread on the SIP 403 stall, this is the exact same underlying issue. The community post there breaks down the sync delay perfectly. Check your proxy logs; you’ll spot METHOD_NOT_ROUTED firing on the secondary interface during the handoff.
Here’s the workaround that’s keeping my on-prem rigs stable: switch the script to use POST with the payload structure above. The Edge firmware actually recognizes POST as a valid GDPR trigger, so it bypasses the rejection logic.
Make sure your load balancer config is updated to let POST through the health check rules. If you miss that, the firewall will drop the packet before it ever reaches the API gateway.
Also, dig into the BIOS network adapter settings if you’re seeing the secondary NIC drop packets during the failover window. I’ve found that link speed negotiation can cause the method packet to fragment right when the failover hits. Force the adapter to 1000Mbps full duplex and lock the MTU to 1500 in the BIOS. That usually clears up the fragmentation issues.
Once you lock down the MTU and switch to POST, the request routes through clean without the 405.
Cause: The suggestion above points to the Edge routing table dropping unsupported methods during primary WAN splits. The standby node method whitelist doesn’t sync fast enough. This breaks GDPR erasure pipelines and derails capacity reporting. The soft delete flag never flips because the control plane treats it as a routing mismatch. The sync lag is annoying. Usually takes a full minute to propagate.
Solution: Route the erasure requests through the regional load balancer instead of hitting the Edge directly. Add the bypass header and pair it with a retry policy. Engineering adjusts the timeout window in the WEM configuration.
"retry_on_405": true,
"bypass_edge_for_compliance": true,
"max_retries": 3
Does the eu-central-1 setup handle the failover latency? Similar routing drops showed up in the historical aggregation thread last month. Hand the payload validation to the integration squad. They’ll verify the audit log pipeline catches the timestamp. Leave the timeout at two seconds.
1 Like
PureCloudPlatformClientV2 doesn’t actually support a straight DELETE on that guest endpoint anyway, which is why you’re hitting the 405. The docs are just outdated on this. You gotta push the erasure request through the GDPR API first, then let the backend handle the soft delete. I confirmed this works after wrestling with it all morning. The POST with application/json only triggers properly if you explicitly set the deleteConfirmed query parameter. Routing it through EventBridge to a quick Lambda handler that hits the real GDPR request endpoint fixes the whole pipeline, and you’ll need to whitelist the gdpr:requests:write scope on your OAuth app too. Here’s the exact curl that actually submits the request without throwing a routing mismatch:
curl -X POST "https://api.mypurecloud.com/api/v2/gdpr/requests?deleteConfirmed=true" \
-H "Authorization: Bearer ${TOKEN}" \
-H "Content-Type: application/json" \
-d '{"reason": "gdpr_request", "timestamp": '"$(date +%s)"'}'
2 Likes