RegisterOrganizationUser

Authorization

Requires Organization scoped authorization. See the Enablement Services Authorization guide.

The registerOrganizationUser mutation is used to create a new user in the database. Upon successful creation, the mutation will return the user's unique ID. You should store this ID in your database and associate it with your consumer record, as it will be required for accessing authenticated queries and mutations.

Below is an example of the registerOrganizationUser mutation, detailing all available input fields and the fields included in the output. The connections and tradelines fields in the output require additional inputs, as shown in the example.

Mutation

mutation RegisterOrganizationUser  {
  registerOrganizationUser(
    input: {
      organizationSlug: String!
      email: String!
      phoneNumber: string!
      name: NameInput!
      address: AddressInput!
      dateOfBirth: DateInput!
      nationalId: String
      visitorID: String
    }
  ){  
    user {
            id
            email
            phoneNumber
            status
            createdAt
            updatedAt
            syncedAt
            closedAt

connection(input: ConnectionsInput!): ConnectionsConnection!
       tradelines(input: TradelinesInput!): TradelinesConnection!
    }
  }
}

Input Attributes

Output Attributes - User