400 error while create a ticket in Freshdesk

Product
, ,
1

Hi Team,

Greetings!!

When I try to create a ticket in Freshdesk, we get a 400 error stating this.

{
  "description": "Validation failed",
  "errors": [
    {
      "field": "requester_id",
      "message": "There is no contact matching the given requester_id",
      "code": "invalid_value"
    }
  ]
}

There is no requester_id field set as mandatory in the instance.

And please find the post payload below.

{
    "name": "testUser",

   "email":    "randommail@test.com",

   "subject": "test subject",

   "description":

    "<div>test ticket </div>",

   "source": 2,

   "status": 2,

   "priority": 1,

   "tags": [ "test" ],

   "custom_fields":

    { "cf_reviewid":

       "AbFvOqnH0bs7ztEH08mj7hNBaa5QWP5grxnVdHTJ7wbB0Bs-610vQS2bMKWJkN6ojWbgtuZxfADH",

      "cf_review_type": "Google Review",

      "cf_review_rating": "5 stars"

} }

Kindly let me know what I’m missing.

Thanks

3

Hi team,

Greetings!

Is there any update on this?

Thanks in advance.

4

According to the documentation:

image
image1280×960 105 KB

And the marker indicates:

image

Although there are different conditions that users can apply in their Freshdesk instances, the API consumption requires developers use one of those † marked fields to be used in the API call in order to create ticket successfully.

5

Hi @Saif,

Yes, as per the documentation, one of the fields must be provided in the payload.

But as you could see in the payload that I gave, the email field is included. So could you please debug this deeper?

Thank you.

6

I tried to create a ticket:

Here’s what I tried:

image
image2552×1450 275 KB

And I was able to create ticket:

image
image966×770 38.9 KB

I wonder if the email address you used is an existing user in the system?

7

Hi @Saif,

Good morning,

We have tried the same in another instance, and it worked!

But we face this issue only with this instance. koskii.freshdesk.com

Could you please check on this, @Saif?

Thank you.

1 Like
8

It appears like this is a specific issue to an account.

To discuss this further, I put you in touch with the Freshdesk Support team. You are welcome to follow up (with them) and share what you learn on this thread.

Cheers!

9

This issue turned out to be account specific bug. The fix was offered by Freshdesk team about a month ago.