Support Center

API Troubleshooting

The JumpCloud REST API is complex, and powerful, but there are a few things to note about using it, which may be causing you some issues during debugging:


Calls with Payload Always Return 400 Error


Make sure that any payload you send to the JumpCloud API is in the form of a string, and not a binary JSON object. JumpCloud will not accept a binary JSON object.

To perform this conversion, you can use: JSON.stringify(payloadObject)


POST/PUT returns 200 OK, but no changes are made


JumpCloud expects to see well-populated JSON objects in the payload. A POST or a PUT with only a small subset of fields may appear to be accepted, but in some cases can silently fail.

A best practice with PUT is to GET the object you want to modify, modify it in memory, and then PUT it. That will ensure that you don't run afoul any required (but missing fields).


PUT on systemuser objects drops all tags

(If your organization was created after Tuesday, April 11 2017, this is not applicable)


When you PUT a systemuser object, you have two options with systemuser.tags:
  1. You can include the tags field, in which case you must enumerate all tags of which the systemuser is a member.
  2. You can exclude the tags field, in which case the systemuser's tag membership will be unaffected.
 

Last Updated: Apr 17, 2017 11:12AM MDT

Related Articles
31b11a79e2c94470a66430cfe6d3eecd@jumpcloud.desk-mail.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete