Hi @MattH,

I just tried your API call and the issue is that `properties` needs to be nested inside of `attributes`.

{
  "data": {
    "type": "event",
    "attributes": {
      "properties": {},
      "metric": {
        "data": {
          "type": "metric",
          "attributes": {
            "name": "Test Event"
          }
        }
      },
      "profile": {
        "data": {
          "type": "profile",
          "attributes": {
            "email": "matt@emails.com",
            "properties": {
              "Existing Property": 500,
              "Totally New Property": "some_value"
            }
          }
        }
      }
    }
  }
}

Cheers,

Kevin.

Ah, yep, that does it and I’m now able to both add new properties and update existing ones too!

Thanks Kevin, appreciate your help.

I just found this thread and it’s saved me a lot of time.

But, does that mean the JSON example shown on the create_event documentation page is wrong for the JSON request example?

https://developers.klaviyo.com/en/reference/create_event

Another Flow I am upgrading has a webbhook that called the v1-2 identify method.

I changed to https://developers.klaviyo.com/en/reference/create_or_update_profile and, again, the properties array needs moving inside the attributes array to successfully update / create custom profile properties. Which doesn’t match the example given on the documentation page.

Hey @teamcooperuk! I think these are showing in the correct spot in the JSON examples for both, but please let me know / share screenshots if you’re seeing something different on your end. 

For Create Event, there are actually two properties keys in play. One that is used for event properties and one that is used for profile properties. The profile properties key appears in the correct spot for me:

For Create or Update Profile, I’m seeing properties under attributes:

I see my mistake now - I don’t generally have to use the location object, and with that removed it meant I missed the correct positioning.