Change detail
6 changes across 3 operations
- PATCH/abonnement/{uuid}
- breaking
the
///request property's minLength was increased from0to1 - warning
the
///request property's maxLength was set to1000
- breaking
- PUT/abonnement/{uuid}
- breaking
the
///request property's minLength was increased from0to1 - warning
the
///request property's maxLength was set to1000
- breaking
- POST/abonnement
- breaking
the
///request property's minLength was increased from0to1 - warning
the
///request property's maxLength was set to1000
- breaking
Change detail
4 changes across 4 operations
- PATCH/abonnement/{uuid}
- breaking
the
request property's minLength was increased from0to1
- breaking
- PUT/abonnement/{uuid}
- breaking
the
request property's minLength was increased from0to1
- breaking
- POST/abonnement
- breaking
the
request property's minLength was increased from0to1
- breaking
- POST/kanaal
- breaking
the
request property's minLength was increased from0to1
- breaking
- View all changes (30)
Change detail
30 changes across 10 operations
- PATCH/abonnement/{uuid}
- breaking
removed the required property
from the response with the status - info
the security scope
notificaties.consumerenwas added to the endpoint's security schemeJWT-Claims - info
the security scope
notificaties.scopes.consumerenwas removed from the endpoint's security schemeJWT-Claims - info
added the required property
to the response with the status
- breaking
- PUT/abonnement/{uuid}
- breaking
removed the required property
from the response with the status - info
the security scope
notificaties.consumerenwas added to the endpoint's security schemeJWT-Claims - info
the security scope
notificaties.scopes.consumerenwas removed from the endpoint's security schemeJWT-Claims
- breaking
Change detail
2 changes across 1 operation
- POST/notificaties
- breaking
the response property
became optional for the status - info
the request property
became optional
- breaking
Revisions go back to the API's first capture.