# API cleanup for freshly created projects

[date: 2022-12-06T18:03:40.493+01:00]

We want our APIs to be as clean as possible, but we also do not want to disrupt the work of our customers. With that in mind, **we have decided to apply some changes to the API only for the websites created from January 1st, 2023 onwards.** Therefore, websites created in the new year will have a slightly different API:

-   `createdAt` and `updatedAt` fields will be available on the content management API as part of the `meta` object of the `item` and `item_type` entities;
-   the fields `createdAt` and `updatedAt` won’t be available via GraphQL in the CDA: the existing `_createdAt` and `_updatedAt` will remain as they currently are (quick take-away: in our GraphQL API, meta fields always start with an underscore 😉);
    
-   legacy fields with wrong spelling like `appeareance` and `collection_appeareance` , already marked as deprecated, won't be available anymore.
    

The changes will only impact new websites: nothing will change for existing ones or their duplicates. For any further info, please get in touch with our customer support.