Manually cause a consent object to expire

The key of the consent object to expire.

Indicates whether or not a webhook event should be sent to notify your application that the consent has been expired.

By default, a new webhook event is not sent if a previous one has already been sent for this consent object. However, you can set this parameter to true to force another webhook event to be sent.

If the consent was previously expired, then it is sent back unchanged. Otherwise, the

The key (ID) to use to retrieve the underlying object from the API.

The time at which the object was created, expressed as a Unix timestamp with microseconds.

The time at which the object was last modified, expressed as a Unix timestamp with microseconds.

Indicates whether or not the data on this object has been verified.

Indicates the status of the verification.

not_started means that the verification process has not been started.
processing means that the verification process has started but no results have come back.
succeeded means that the data has been verified. In this case, verified should also be set to true.
failed means that the verification process finished but the data was not able to be verified.
reset means that the previous verification results have been discarded.

not_started processing succeeded failed reset

The time at which the data was last verified, expressed as a Unix timestamp with microseconds. This property will only be set if the data was successfully verified at some point in the past.

The key of the child person object for whom the consent is for.

The key of the guardian person object who is giving the consent.

The time at which this consent object expires, expressed as a Unix timestamp with microseconds. When a consent object expires, it is recommended that you delete the data belonging to the child associated with the consent object. If you have a webhook endpoint configured, StandardCode will also send you a webhook event when the consent expires, so that you can perform any data cleanup automatically.

By default, consent objects will expire 30 days from when they are created. You can get in touch with us to set a different maximum age though.

An error indicating why the server could not process the request.

A human readable description of what went wrong.

The specified key does not resolve to a consent object.

A human readable description of what went wrong.

200If the consent was previously expired, then it is sent back unchanged. Otherwise, the expires_at timestamp will be set to the current time.

400An error indicating why the server could not process the request.

404The specified key does not resolve to a consent object.

`expires_at` timestamp will be set to the current time.