Add createdAt and updatedAt fields to brand registration

[GillesInnov35]

Added createdAt and updatedAt fields with filters to the brand registration API definition.

What type of PR is this?

• enhancement/feature

What this PR does / why we need it:

include 2 new fields createdAt and updatedAt to the brand registration API definition allowing full management of customer registrations.
To be more useful for operational purposes, fields format is date-time (e.g. 2026-07-16T11:51:30+03:00)

Which issue(s) this PR fixes:

Fixes #123

[camara-validation]

CAMARA Validation — PASS (with warnings)

0 errors, 4 warnings, 24 hints | Profile: standard

View full results

[mohdfarhanakram]

Nice one, @GillesInnov35 the createdAt/updatedAt response fields are exactly what's needed here, and the full-timestamp format matches what @alpaycetin74 suggested on #123. 👍

One small thought on the added filters: since these are to-the-second timestamps, an exact match is hard to query against - would a range (createdAtAfter/createdAtBefore & updatedAtAfter/updatedAtBefore) be more practical? Happy to help with that as a follow-up either way.

[GillesInnov35]

@mohdfarhanakram , you're right not easy to query with an equal operator.
In that case of timestamp, .gt or .gt operators are mainly used. It should be specified.
WDYT ?

[alpaycetin74]

Hello, in design guidelines section 4.3.2, there is an example to include gt, gte,lt,lte filters for a date type.
I think we can follow this approach for createdAt & updatedAt.
For expiresAt query, we can also include equality.

https://github.com/camaraproject/Commonalities/blob/main/documentation/CAMARA-API-Design-Guide.md#43-filtering

[alpaycetin74]

LGTM, thank you