Create User Domo API with R in Rstudio HTTR 400 status

Reply
Highlighted
White Belt

Create User Domo API with R in Rstudio HTTR 400 status

------Where I got the instructions------

 

https://developer.domo.com/docs/users-api-reference/users-2#Create%20a%20user

 

POST https://api.domo.com/v1/users?sendInvite=true

Content-Type: application/json

Accept: application/json

Authorization: bearer <your-valid-oauth-access-token>

{

"title": "Software Engineer",

"email": "leonhard.euler@domo.com",

"alternateEmail": "leonhardeuler@email.com",

"role": "Admin",

"phone": "888-361-1078",

"name": "Leonhard Euler",

"location": "American Fork",

"timezone": "",

"locale": "",

"employeeNumber": 23432

}

 

------------What was the result-------------

I'm trying to create a new user using HTTR in Domo. I keep getting a 400 error. I believe that the issue is with my "body = w" from below.

 

                   response [https://api.domo.com/v1/users?sendInvite=true]
                   Date: 
                   Status: 400
                   Content-Type: application/json;charset=utf-8
                   Size: 

 

 

 

------What I did------

library(DomoR)
library(curl) #interface to libcurl (to make API calls)
library(jsonlite) #convert json to list objects in R
library(httr) #GET and POST methods through https, etc.


#create 

name <- 'Joshua James'
email <- 'Joshua.James@domo.com'
role <- 'Participant'


#build API call
auth <- 123456789........
url <- paste('https://api.domo.com/v1/users?sendInvite=true', 200, sep='')

 

#dynamically build the body of the post
w = paste('{ \"title\":[',"",'],
\"name\":[',name,'],
\"email\":[',email,'],
\"role\":"Participant,
}',sep = " ")

 

#create the new user
httr:Smiley TongueOST(url=url, add_headers("Content-Type" = "application/json", "Accept" = "application/json", "Authorization" = auth), body = w)

Tags (3)
Major Brown Belt

Re: Create User Domo API with R in Rstudio HTTR 400 status

Hi Joshua

 

There are a number of reasons that a 400 error can be returned. I would reach out to support and see if they have any logs that give anything specific. Before that, though I would double your access tokens and other account-specific information.

 

Jarvis

Announcements
Check out these great solution videos! The new iSolveditWithDomoboard is live, share yours and earn higher rankings in Dojo click here!