Api record update

đź’¬ General Discussion
1

I am trying to do simple update of demo data to work with Api .

After importing the postman collection and fixing the access token i managed to get info so the next step is to update something.

When i tried to update on Account then i got exception that the data option is missing.
I have found 2 posts where the first was talking about attributes missing where the solution was to update the Fields.php to fix a pattern and the second that was talking about missing header for the content type where you have to set the content-type = application json.

In my perspective i did update the php. and my postman call has proper content-type in headers but i still get the same error.

image
image2293Ă—1571 124 KB

image

image
image1230Ă—530 25.7 KB

image
image2202Ă—1220 113 KB

image
image1928Ă—1065 107 KB

image
image3298Ă—1673 239 KB

Any idea what is the problem?

2

You might find this helpful:

3

I suppose you propose not to use the body to add the data but to use the form-urlencoded and also to set the type of data to json. It also did not work. I expect that you do not propose to use 4.1 and soap?

The postman collection is what the /Api/docs provide inside the installation and it is the same with the documentation. Of course the token is working i do not have problem with login.

image
image1384Ă—775 24.6 KB

4
5

Thank you for the link but i have already read the v8 api i have already made the login and the token access and i have successfully run get calls. Based on the documentation and on the previous printscreen from the documentation this patch function that updates an existing record give me the problem. Though the data option is there in the body(which is a json object) the response behaves like it is not there.

6

There is a mistake on setup of the type and id . In the response body the Json values of the type and id have to be text which means they have to be inside quotes

7

Awesome. You found the solution.

Could you please share it here, so it will help others in the future?

8

My initial wrong body was

{
“data”: {
“type”: {{module}},
“id”: {{record_id}},
“attributes”: {
“name”: “Tortoise Corp Updated”
}
}
}

And this was making a body like:

{
“data”: {
“type”: Accounts,
“id”: 1966962c-0725-d759-3167-673614a00e6b,
“attributes”: {
“name”: “Tortoise Corp Updated”
}
}
}

The correct body was:

{
“data”: {
“type”: “{{module}}”,
“id”: “{{record_id}}”,
“attributes”: {
“name”: “Tortoise Corp Updated”
}
}
}

Which makes the request body to be :

{
“data”: {
“type”: “Accounts”,
“id”: “1966962c-0725-d759-3167-673614a00e6b”,
“attributes”: {
“name”: “Tortoise Corp Updated”
}
}
}

The error message is miss-leading but it is what it is

9