If you’re making bulk changes or integrating automatically with ElasticBox, you can use the API to handle those functions. Which is why, when making API requests, you don’t want to compromise your login credentials. Use authentication tokens instead!
Gone are the days when you had to fret about an authentication method for API calls. Regardless of how you login to ElasticBox, be it Google, GitHub, username/password, or LDAP, you can connect over the API in an uniform way — using a token.
You can get authentications tokens from your account in the UI and up to 50 of them per account. Since they never expire, you don’t have to worry about breaking API calls either. If you want to invalidate an API call, simply delete its related token. But the most useful part of a token is it securely lets you access your ElasticBox data without compromising your login.
Remember to keep your authentication tokens secret though! They function like ordinary OAuth access tokens so treat them just like passwords. You can use tokens to connect not just over the API, but also the ElasticBox command line interface.
Get a token in 3 simple steps:
- Sign in with your account in ElasticBox.
- Click Authentication Token from the user drop-down menu on the right.
- Enter a descriptive name for the token and click Create Token.
Once you have an authentication token, the ElasticBox API is your OYSTER!