Hi @hkhan317,

Which endpoint are you using to update the profile properties? Can you share your full request body (please redact any personal information)?

Let us know.

Best,

Kevin.

I’m testing two endpoints using the curl command. For my original error, this was the endpoint 

curl -X PUT "https://a.klaviyo.com/api/v1/person/01J0QR5B2WG3Z25Y060J7VDDV7?api_key=pk_64e8cca14a9509af40d2e8458d9c1f6a0f" \
-H "Content-Type: application/json" \
-d '{"properties": {"Pesticides": ""Acephate", "Tetraconazole", "Endrin", "Pyrimethanil", "Penthiopyrad", "Thiabendazole", "Cyantraniliprole", "Pentachloroaniline (PCA)", "Acetamiprid", "Methamidophos"]}}'

I read the API doc’s and tried another

curl --request PATCH \
     --url https://a.klaviyo.com/api/profiles/{profile_id}/ \
     --header 'Authorization: Klaviyo-API-Key your-api-key' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'revision: 2024-06-15' \
     --data '{"properties":{"Pesticides":i"Acephate"]}}'

With this method I get this error. 

{"errors":r{"id":"b7c5d32b-8a1e-4ea4-aae0-c9c9db9dc4c5","status":400,"code":"invalid","title":"Invalid input.","detail":"The payload provided in the request is invalid.","source":{"pointer":"/data"},"links":{},"meta":{}}]}%

the custom property Pesticides exist and is a list, I am able to edit the values through Klaviyo. The json when I actually go to the URL shows Pesticidess] in the properties, is it because my data payload is only for one property instead of the whole profille.

Hi @hkhan317,

I think your request body is not including all of the required fields. I am doing it through postman/JSON and it’s working with this request body. I am using the PATCH endpoint.

// Endpoint: PATCH https://a.klaviyo.com/api/profiles/{profileId}

{
    "data": {
        "type": "profile",
        "id": "{profileId}",
        "attributes": {
            "properties": {
                "list": "1, 2, 3] // your list here...
            }
        }
    }
}

Cheers,

Kevin.

Hello @hkhan317  I have already posted the solution to this on a different thread you created earlier.
 

Confirming @KeviSunshine’s response is correct - the payload is missing required fields and @Maxbuzz’s response linked is also valid. Let us know if you need any further assistance!