Organization
Users and User Groups
    API tokens
    Users - Entity APIs
    Users - Declarative APIs
    UserGroups - Entity APIs
    UserGroups - Declarative APIs
    User Authorization
      Invite UserpostGet all usersgetCreate a userpostGet a usergetUpdate a userputDelete a userdeleteGet Profileget
    User Settings
    User Identifiers
    User management
Permissions
Data Source
Workspaces
Logical Data Model
Analytical Objects
Reports
Reporting
Export & Automations
AI Lake
AI Assistant
Agents
Other
Schemas
powered by Zudoku
OpenAPI definition

User Authorization

Endpoint:/

Invite User

POST
/api/v1/actions/invite

Puts a new invitation requirement into the invitation generator queue. This is a GoodData Cloud specific endpoint.

Invite User › Request Body

  • emailstring · email · required
  • userIdstring · required
  • firstNamestring
  • forceSendboolean

    Force resend invitation email even if a pending invitation exists. Maximum 3 emails can be sent per invitation (1 initial + 2 resends)

  • lastNamestring

Invite User › Responses

No Content

No data returned
POST /api/v1/actions/invite

Get all users

GET
/api/v1/auth/users

Get all users - dedicated endpoint for user management in the internal OIDC provider. GoodData.CN specific

Get all users › Responses

OK

  • displayNamestring · required

    User description, which will be visible in application.

    Example: jeremy
  • emailstring · email · required

    Email - used as lookup (must be unique). For PUT method, it must be same as in URL

    Example: zeus@example.com
  • authenticationIdstring

    Field which is stored as the authenticationId in metadata. Must be absent on POST. On PUT it must be absent, or equal to the value calculated by the backend (e.g. as returned from a previous GET).

  • passwordstring · writeOnly

    User password. Write-only - accepted on POST and PUT, never returned in a response.

GET /api/v1/auth/users

Create a user

POST
/api/v1/auth/users

Create a user - dedicated endpoint for user management in the internal OIDC provider. GoodData.CN specific

Create a user › Request Body

  • displayNamestring · required

    User description, which will be visible in application.

    Example: jeremy
  • emailstring · email · required

    Email - used as lookup (must be unique). For PUT method, it must be same as in URL

    Example: zeus@example.com
  • authenticationIdstring

    Field which is stored as the authenticationId in metadata. Must be absent on POST. On PUT it must be absent, or equal to the value calculated by the backend (e.g. as returned from a previous GET).

  • passwordstring · writeOnly

    User password. Write-only - accepted on POST and PUT, never returned in a response.

Create a user › Responses

Created

  • displayNamestring · required

    User description, which will be visible in application.

    Example: jeremy
  • emailstring · email · required

    Email - used as lookup (must be unique). For PUT method, it must be same as in URL

    Example: zeus@example.com
  • authenticationIdstring

    Field which is stored as the authenticationId in metadata. Must be absent on POST. On PUT it must be absent, or equal to the value calculated by the backend (e.g. as returned from a previous GET).

  • passwordstring · writeOnly

    User password. Write-only - accepted on POST and PUT, never returned in a response.

POST /api/v1/auth/users

Get a user

GET
/api/v1/auth/users/{userEmail}

Get a user - dedicated endpoint for user management in the internal OIDC provider. GoodData.CN specific

Get a user › path Parameters

  • userEmailstring · required

Get a user › Responses

OK

  • displayNamestring · required

    User description, which will be visible in application.

    Example: jeremy
  • emailstring · email · required

    Email - used as lookup (must be unique). For PUT method, it must be same as in URL

    Example: zeus@example.com
  • authenticationIdstring

    Field which is stored as the authenticationId in metadata. Must be absent on POST. On PUT it must be absent, or equal to the value calculated by the backend (e.g. as returned from a previous GET).

  • passwordstring · writeOnly

    User password. Write-only - accepted on POST and PUT, never returned in a response.

GET /api/v1/auth/users/{userEmail}

Update a user

PUT
/api/v1/auth/users/{userEmail}

Update a user - dedicated endpoint for user management in the internal OIDC provider. GoodData.CN specific

Update a user › path Parameters

  • userEmailstring · required

Update a user › Request Body

  • displayNamestring · required

    User description, which will be visible in application.

    Example: jeremy
  • emailstring · email · required

    Email - used as lookup (must be unique). For PUT method, it must be same as in URL

    Example: zeus@example.com
  • authenticationIdstring

    Field which is stored as the authenticationId in metadata. Must be absent on POST. On PUT it must be absent, or equal to the value calculated by the backend (e.g. as returned from a previous GET).

  • passwordstring · writeOnly

    User password. Write-only - accepted on POST and PUT, never returned in a response.

Update a user › Responses

OK

  • displayNamestring · required

    User description, which will be visible in application.

    Example: jeremy
  • emailstring · email · required

    Email - used as lookup (must be unique). For PUT method, it must be same as in URL

    Example: zeus@example.com
  • authenticationIdstring

    Field which is stored as the authenticationId in metadata. Must be absent on POST. On PUT it must be absent, or equal to the value calculated by the backend (e.g. as returned from a previous GET).

  • passwordstring · writeOnly

    User password. Write-only - accepted on POST and PUT, never returned in a response.

PUT /api/v1/auth/users/{userEmail}

Delete a user

DELETE
/api/v1/auth/users/{userEmail}

Delete a user - dedicated endpoint for user management in the internal OIDC provider. GoodData.CN specific

Delete a user › path Parameters

  • userEmailstring · required

Delete a user › Responses

No Content

No data returned
DELETE /api/v1/auth/users/{userEmail}

Get Profile

GET
/api/v1/profile

Returns a Profile including Organization and Current User Information.

Get Profile › Responses

OK

  • entitlementsobject[] · required

    Defines entitlements for given organization.

  • featuresrequired
  • linksobject · required
  • organizationIdstring · required
  • organizationNamestring · required
  • permissionsstring[] · required
    Enum values:
    MANAGE
    SELF_CREATE_TOKEN
    BASE_UI_ACCESS
  • telemetryConfigobject · required

    Telemetry-related configuration.

  • userIdstring · required
  • namestring
GET /api/v1/profile
UserGroups - Declarative APIsUser Settings