Is it bad practice to require nested JSON data, on my API endpoints?

Question

I've made an endpoint for creating events: POST /events/new

The request should have JSON data on the body. This is the JSON structure that is required for creating a new event:

{
    "label": "my first event",
    "description": "lorem ipsum dolor sit amet",
    "meta": {
        "status": "draft",
        "isOnline": true,
        "visibility": "visible",
        "customID": "my-first-event",
        "tags": ["foo", "bar"],
        "categories": ["concert", "sports"]
    }
}

My problem being: I don't think I've ever seen services requiring nested properties (like in meta.status). Is it a bad practice?

I'm doing it like that because it's more organized.

Answer 1

No, I think this is fine.

The object is still flat, it just has namespaces.

Where it might be "bad" though is if you have a collection of child objects

{
   "name": "A",
   "children" : [
     { "name":"B"},....
    ]
}

Now if you are posting this to a "resource" style endpoint you have an open question about whether you can update/change the child objects without sending the entire object.

Not a massive issue, but perhaps something to be avoided if you don't have to go that route.