CorebanqCorebanq Developer Docs
User Preferencesv1

Delete a preference group

ANSWERS 204 WITH NO BODY — unlike deleting an option below, which answers 200 with a message.

DELETE
/v1/user-preferences/{user_id}/groups/{group_id}

Authorization

BearerAuth
AuthorizationBearer <token>

JWT Bearer token authentication

In: header

Path Parameters

user_id*string

Owner of the preferences. This is the record the preferences belong to, NOT the caller — an actor with the right record permission reads and writes another user's preferences through the same route.

group_id*string

Identifier of the preference group.

Response Body

curl -X DELETE "https://example.com/v1/user-preferences/497f6eca-6276-4993-bfeb-53cbbbba6f08/groups/497f6eca-6276-4993-bfeb-53cbbbba6f08"
Empty
Empty
Empty
Empty
Empty

PATCHChange some fields of a preference

The body is a free-form object of the fields to change; it is not validated against a schema the way PUT's body is.

DELDelete an option

ANSWERS 200 WITH A MESSAGE BODY, not the 204 that deleting a group or a preference answers. The two are inconsistent on purpose here only in the sense that the code is: document what you get.