Optimizely Admin User Profile Preferences API
The Admin User Profile Preferences API from Optimizely — 7 operation(s) for admin user profile preferences.
Operations 14
Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay
GET
/api/v1/admin/AdminUserProfilePreferences
List admin user profile preferences · Returns the EntitySet AdminUserProfilePreferences
#
Ask an LLM
“Which saved preferences exist across all admin user profiles?”
“Can I filter admin preferences by name and page through them with $top and $skip?”
Tell an agent
List all admin user profile preferences.
Find admin user profile preferences matching the filter {filter}.
POST
/api/v1/admin/AdminUserProfilePreferences
Create a preference for an admin user profile · Post a new entity to EntitySet AdminUserProfilePreferences
#
Ask an LLM
“How do I save a named preference for a specific admin user profile?”
“What fields are required when adding an admin preference for any profile?”
Tell an agent
Create preference {name} with value {value} for admin profile {adminUserProfileId}.
Add an admin user profile preference named {name} set to {value} for profile {adminUserProfileId}.
GET
/api/v1/admin/AdminUserProfilePreferences({id})
Get an admin user profile preference by ID · Returns the entity with the key from AdminUserProfilePreferences
#
Ask an LLM
“What value is stored in one admin preference record by its ID?”
“Can I fetch a single admin user profile preference by its key?”
Tell an agent
Get admin user profile preference {id}.
Show the name and value of admin preference record {id}.
PUT
/api/v1/admin/AdminUserProfilePreferences({id})
Replace an admin user profile preference · Replace entity in EntitySet AdminUserProfilePreferences
#
Ask an LLM
“How do I overwrite an entire admin preference record by ID?”
“Does replacing an admin preference require sending both name and value again?”
Tell an agent
Replace admin preference {id} with name {name} and value {value}.
Overwrite the whole admin user profile preference {id} using a full PUT.
DELETE
/api/v1/admin/AdminUserProfilePreferences({id})
Delete an admin user profile preference by ID · Delete entity in EntitySet AdminUserProfilePreferences
#
Ask an LLM
“Can I delete one admin preference record by its ID?”
“Does deleting an admin preference support an If-Match ETag check?”
Tell an agent destructive · confirm first
Delete admin user profile preference {id}.
Delete admin preference record {id} only if its ETag matches {ifMatch}.
PATCH
/api/v1/admin/AdminUserProfilePreferences({id})
Update an admin user profile preference by ID · Update entity in EntitySet AdminUserProfilePreferences
#
Ask an LLM
“How do I change the value of one admin preference record by ID?”
“Can I partially update an admin user profile preference?”
Tell an agent
Update admin preference record {id} to value {value}.
Patch admin user profile preference {id}, setting {name} to {value}.
GET
/api/v1/admin/AdminUserProfilePreferences/Default.Default()
Get a default admin preference template · Call operation Default
#
Ask an LLM
“What default values does a new admin user profile preference start with?”
“Is there a blank admin preference template I can fetch before creating one?”
Tell an agent
Fetch the default admin user profile preference template.
Show me the default values for a new admin preference.
GET
/api/v1/admin/AdminUserProfilePreferences/Default.Current()
Get my admin preferences via the Current() function · Call operation Current
#
Ask an LLM
“How do I read the signed-in admin's preferences through the OData Current() function?”
“Can the Default.Current() function return only selected preference fields?”
Tell an agent
Call the OData Default.Current() function to get my admin preferences.
Get my admin preferences through Current() selecting only {select}.
GET
/api/v1/admin/adminuserprofilepreferences/Current
Get my admin preferences via the /Current route · Admin user profile preferences get preferences for current user 2
#
Ask an LLM
“What preferences are saved for me, using the plain /Current route?”
“Can I read the logged-in admin's preferences without the OData function syntax?”
Tell an agent
Read my own admin preferences from the /Current route.
Fetch the current admin's preferences from the /Current route, expanding {expand}.
POST
/api/v1/admin/adminuserprofilepreferences/Current
Save a preference for the signed-in admin · Admin user profile preferences create preferences for current user
#
Ask an LLM
“How do I save a new preference for myself as the logged-in admin?”
“Can I store a named setting on my own admin profile without knowing my profile ID?”
Tell an agent
Save my admin preference {name} with value {value}.
Add a new preference {name} = {value} to my own admin profile.
DELETE
/api/v1/admin/adminuserprofilepreferences/Current
Remove one of my own admin preferences by name · Admin user profile preferences delete preferences for current user
#
Ask an LLM
“Can I delete one of my own admin preferences by its name?”
“What happens to my admin setting when I remove it from the current profile?”
Tell an agent destructive · confirm first
Remove my admin preference named {name}.
Delete the {name} setting from my own admin profile.
PATCH
/api/v1/admin/adminuserprofilepreferences/Current
Change one of my own admin preferences · Admin user profile preferences update preferences for current user
#
Ask an LLM
“How do I change the value of a preference on my own admin profile?”
“Can I update my current admin setting by name rather than by record ID?”
Tell an agent
Change my admin preference {name} to {value}.
Update my own {name} setting to {value}.
DELETE
/api/v1/admin/adminuserprofilepreferences/delete
Bulk delete admin user profile preferences · Admin user profile preferences delete route
#
Ask an LLM
“How do I delete several admin preference records at once?”
“Can I pass a list of IDs to remove many admin user profile preferences?”
Tell an agent destructive · confirm first
Bulk delete the admin user profile preferences with IDs {ids}.
Remove all of these admin preference records in one call: {ids}.
GET
/api/v1/admin/adminuserprofilepreferences({key})/customproperties({custompropertyKey})
Get a custom property on an admin preference · Admin user profile preferences get custom property by key and custompropertykey
#
Ask an LLM
“Where do I read a custom property stored on an admin user profile preference?”
“Can I fetch one extra property value from an admin preference record?”
Tell an agent
Get custom property {custompropertyKey} on admin preference {key}.
Show the custom property {custompropertyKey} of admin user profile preference {key}.