The User API

The User API is a REST API that gets, adds and updates user/group/department information.

User Authentication

The User REST API requires password authentication, with the appropriate Keys and Values set in the header of the request. If the Basic authentication security feature is also set on your domain, both headers for the Password Authentication and the Basic Authentication will be required for the request.

Password Authentication

Set “X-Cybozu-Authorization” on the request header, with a BASE64 encoded login name and password as the value.
If your log in name is “kintone” and your password is “developer”, BASE64 encode “kintone:developer” and set it on the header as follows:

1

X-Cybozu-Authorization: a2ludG9uZTpkZXZlbG9wZXI=

Session Authentication

Session authentication is a method of authentication where the a session ID is assigned to a user by the web server, and saved as a cookie. This cookie is used to identify and authenticate the user. When using session authentication with any method aside from the GET method, a CSRF token is necessary. Refer to the Get CSRF Token documentation for more details on retrieving a CSRF token.

Authentication priority

The priority of authentication is as follows.

1. Password authentication
2. Session authentication

Basic Authentication

If your Kintone environment has set the Basic authentication security feature, add “Authorization” in the request header, with the string “Basic " and a BASE64 encoded login name and password of the Basic authentication as the value.
If the basic authentication log in name is “chocolate” and the basic authentication password is “pudding”, place “Basic " in the value, followed by a BASE64 encoded “chocolate:pudding” as follows:

1

Authorization: Basic Y2hvY29sYXRlOnB1ZGRpbmc=

* Domains created after the September 6, 2019 update are unable to use basic authentication.

Refer to the API Updates for September 2019 for details.

Request Headers

These request headers are used for the REST API.

Request URI

Responses

HTTP status code 200 denotes that the request was successful.
Treat any other status code as errors. Errors will respond with JSON data including the following information.

Sample Error Response

1
2
3
4
5

{
  "message": "Invalid JSON string.",
  "id": "1505999166-897850006",
  "code": "CB_IJ01"
}

Data structures used with the User API

ID type

Used for entities (user/group/departments) in Kintone.
An integer between 1 - Long.MAX.

user type

Only Users & System Administrators are able to get data of Custom Fields that have the “Visibility” option unchecked.

department type

title type

group type

organizationTitle type

userTitle type

customItemValue type

Custom fields may have their “Visibility” option’s “Make this field public” setting unchecked. Only Users & System Administrators are able to get data of Custom Fields that have the “Visibility” option unchecked.

Notes

X-HTTP-Method-Override Header

• Add the X-HTTP-Method-Override header to work around the Request URI Too Large error that occurs when the request URI exceeds 4KB. All User APIs support this header.
• If a GET request of a User API is sent using Kintone REST API Request method , and the URI length exceeds 4KB, the X-HTTP-Method-Override header will automatically be added and the request will be sent as a POST request. This allows User API requests with long URIs to be executed without errors.