(Preview) Manage user credentials and integrations

post

/20260430/aiDataPlatforms/{aiDataPlatformId}/userSettings

(Preview) The User Settings API allows you to manage user-specific configurations and credentials within an AI Data Platform instance. What you can do -> Store user credentials and integrations, including: -> IAM user credentials -> Git account configurations (e.g., GitHub PAT) -> Create and manage multiple settings -> Mark a setting as default for a given type -> Retrieve and filter settings by type or default status Supported setting types -> IAM_USER_CREDENTIAL ??? OCI user credentials for API access -> GIT_ACCOUNT ??? Git provider configuration (e.g., GitHub personal access token) Core operations -> Create a user setting -> List all user settings (with filtering and pagination) -> Get a specific setting by key -> Update an existing setting -> Delete a setting

Request

Path Parameters
Header Parameters
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash.
  • Minimum Length: 1
    Maximum Length: 64
    A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of running that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and removed from the system, then a retry of the original creation request might be rejected.
Body ()
Details for the new setting.
Root Schema : CreateUserSettingDetails
Type: object
Settings details for the new user.
Match All
Settings details for the new user.
Show Source
Nested Schema : CreateSettingDetails
Type: object
Details of creating setting.
Show Source
Nested Schema : SettingData
Type: object
Discriminator: type
Setting Data
Show Source
  • Allowed Values: [ "IAM_USER_CREDENTIAL", "GIT_ACCOUNT", "OAUTH" ]
    Setting data type discriminator
Back to Top

Response

Supported Media Types

200 Response

Successful operation. Settings are created or updated.
Headers
  • For optimistic concurrency control. See `if-match`.
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : UserSetting
Type: object
User Setting
Match All
User Setting
Show Source
Nested Schema : Setting
Type: object
Setting details.
Show Source
Nested Schema : SettingData
Type: object
Discriminator: type
Setting Data
Show Source
  • Allowed Values: [ "IAM_USER_CREDENTIAL", "GIT_ACCOUNT", "OAUTH" ]
    Setting data type discriminator

400 Response

Bad Request (invalid query parameters, malformed headers, and so on).
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

401 Response

Unauthorized (missing or expired credentials, and so on).
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

404 Response

Not Found. The requested resource was not found.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

409 Response

Conflict. Request conflicts with the current state of the resource.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

429 Response

Too Many Requests. Too many requests sent to the server in a short period.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

500 Response

Internal Server Error. The server encountered an unexpected condition preventing fulfilment of the request.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

Default Response

Unknown Error. Error is not recognized by the system.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source
Back to Top