Error 400 when attempting to delete a phone

[DeeQ]

I am performing API calls from Okta Workflows and am encountering an error when attempting a DELETE call to delete a phone. I don't think it's my environment as I can perform GET's and PATCH's without issue.

Here is the url I am using for the request:

/api/v2/telephony/providers/edges/phones/{phoneID}

Here is the error:

{
  "_error": true,
  "retry_count": 0,
  "flo": 739216,
  "method": "PsM-6ANq4",
  "execution": "bf3e4e31-0f2b-490b-9cfe-98bb67a79152",
  "module": "http.raw",
  "kind": "HTTP Request Error",
  "statusCode": 400,
  "headers": {
    "x-amz-cf-id": "2rFlHlZALZF2RD3DbbaMzPGJ-__MLPSbKCyUCJ6STj--QeNIifAP8Q==",
    "content-length": "0",
    "x-amz-cf-pop": "IAD79-C2",
    "x-cache": "Error from cloudfront",
    "connection": "keep-alive",
    "date": "Wed, 19 Jun 2024 21:42:36 GMT",
    "via": "1.1 1019c7748e9bd9371b8cbc3777f0a40e.cloudfront.net (CloudFront)"
  },
  "body": "",
  "message": "400 Bad Request",
  "code": 400,
  "description": "HTTP Request Error",
  "steps": 9,
  "source": {
    "flo": 739216,
    "method": "PsM-6ANq4",
    "execution": "bf3e4e31-0f2b-490b-9cfe-98bb67a79152",
    "module": "http.raw"
  }
}

From what I know, 400 just means malformed syntax? Did a miss something with trying to use this API?

[jacobshaw]

Hi @DeeQ
This is probably a bug since phoneId is the only parameter for that request. I would expect a 404 not found type response if the phone didn't exist, or something more descriptive if there was some other problem with the phone id.
Please open a case with Genesys Cloud care to report this and get it resolved

[John_Carnell]

Hi guys,

You might want to double-check the value you are passing to the API call. I believe the API is expecting a guid. If you pass a guid and it does not exist you get a 404. If you pass a non-guid you get a 400 which would be more consistent with a malformed syntx.

Thanks,
John Carnell
Director, Developer Engagement

[DeeQ]

The full relative URL I'm passing in my workflow is:

/api/v2/telephony/providers/edges/phones/fa5623fe-3bb7-4ee4-aca2-f302e0334f76

That is the ID of a test phone I created, when I run the GET with that URL it returns the correct phones information.

[John_Carnell]

Hi Dee,

I would definitely open a ticket with our Care team then.

Thanks,
John Carnell

[DeeQ]

So, just a general update on this.

This behavior is being observed on all DELETE calls. I opened a ticket with Genesys Support and they are still looking into it.

We found a lot of issues with the way we were handling the API calls within Okta Workflows. Now that we ironed out all those problems, we can confirm the issue is somewhere beyond Okta Workflows.

My current speculation is that since cloudfront is mentioned in the response data, it's something to do with Genesys' AWS configuration.