Hi @gustavog,

You absolutely do not need to do that. I’ve never used this exact API (I’m using an older version of a POST event api), but you should only need a profile identifier (ID, email, phone), and an event name.

The API in the article you linked to is extremely verbose and unnecessary. I wish they showed a simplified version.

It should be something like this, but even this is verbose.

{
  "data": {
    "type": "event",
    "attributes": {
      "properties": {
        "newKey": "New Value"
      },
      "time": "2022-11-08T00:00:00",
      "value": 9.99,
      "metric": {
        "data": {
          "type": "metric",
          "attributes": {
            "name": "Viewed Product"
          }
        }
      },
      "profile": {
        "data": {
          "type": "profile",
          "id": "01GDDKASAP8TKDDA2GRZDSVP4H"
       }
    }
  }
}

With an older endpoint my request body is as simple as this…

{
  "token": "<...>",
  "event": "EVENT_NAME",
  "customer_properties": {
    "$email": "<ID>" // This is the profile identifier
    "new field": "whatever you'd like" // this will add this new field to the profile
  },
  "properties": {
    // Anything you want here, object, array, etc. These are the event properties.
  }
}