Suggestion to improve UUID naming for clarity in API responses

[FaridAmroun]

Hi

I would like to suggest an improvement to enhance the clarity of the API responses in kong, specially for the id field used in resources like consumers.

In the current API response for consumers, the field 'id' represents a UUID, but its naming doesn't explicitly reflect its nature : { "id" : "bb1bcb0c-878d-4135-a298-1723f1af36dc",
"username": "flask_client"
"created at:: "1736447804",
"updated_at": "1736447804"
}

By renaming id to UUID, the field's purpose and format will be more explicit, improving developers experience and aligning with standard naming conventions.

{
"UUID" : "bb1bcb0c-878d-4135-a298-1723f1af36dc",
"username": "flask_client"
"created at:: "1736447804",
"updated_at": "1736447804"
}

Thank you for considering this suggestion. I'm open to any feedback for further discussion.
Best regards.
Fred