![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\"){kind=icon}
<\/p><\/div>
With the exceptions listed below, all API documentation has been moved to JumpCloud API Docs<\/a>. Depending on the functionality desired, you may need to call either, or both endpoints in v1 and v2 of our API.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Supplemental scripts and precompiled binaries can be found on our public Github Support Repository<\/a>. To leverage any of JumpCloud’s available API options, an API key is required during the configuration.<\/p>\n\n\n\n Considerations<\/strong>:<\/p>\n\n\n\n Considerations for free trial accounts:<\/strong><\/p>\n\n\n\n To access your API key:<\/strong><\/p>\n\n\n\n If your data is stored outside of the US, check which login URL you should be using depending on your region. If your organization uses LDAP, RADIUS, or requires firewall allow list configuration, the Fully Qualified Domain Names (FQDNs) will also be region specific. See JumpCloud Data Centers<\/a> for the URLs, FQDNs, and IP addresses.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Note:<\/strong> Admin accounts created before July 15, 2024 will have no expiration date for their API keys. This can be changed at any time. <\/p><\/div><\/div><\/div>\n\n\n\n Note:<\/strong> If you generate a new API key, the default expiration for the key will be set to 90 days. <\/p><\/div><\/div><\/div>\n\n\n\n It’s very important to exercise strong security posture when handling your API key, as it gives unfiltered access to your JumpCloud instance through API calls. If you believe for any reason that your API key may have been shared or compromised, we suggest generating a new API key.<\/p>\n\n\n\n If your data is stored outside of the US, check which login URL you should be using depending on your region. If your organization uses LDAP, RADIUS, or requires firewall allow list configuration, the Fully Qualified Domain Names (FQDNs) will also be region specific. See JumpCloud Data Centers<\/a> for the URLs, FQDNs, and IP addresses.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Warning:<\/strong> Generating a new API key will revoke access to the current API key. This will render all calls using the previous API key inaccessible. You will have to update any existing integrations that use an API key with the newly generated value.<\/p><\/div><\/div><\/div>\n\n\n\n This will impact any of the following integrations: <\/p>\n\n\n\n
Additional client code can be found in the following repos:<\/p>\n\n\n\n\n
Accessing Your API Key<\/h2>\n\n\n\n
\n
\n
\n
\n
\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/important-icon.png\"\/){kind=icon}
<\/p><\/div>\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/important-icon.png\"){kind=icon}
<\/p><\/div>\n
To set a Time to Live (TTL) for your API Key:<\/strong><\/h3>\n\n\n\n
<\/p><\/div>\n
<\/p><\/div>Generating a New API Key<\/h2>\n\n\n\n
\n
<\/p><\/div>\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\"){kind=icon}
<\/p><\/div>\n
\n
FAQ<\/h2>\n\n\n\n