Authentication
To authenticate to the API, a JWT request token is encoded and sent as the jwt param in a POST to /auth/token. The access_token in the response is the JWT bearer token that is included as the Authorization value in the Header of all subsequent API calls.
If you do not have a NETOSECRET API key, see Create a Netography API Key. The NETOSECRET string is a base64 encoded JSON string that contains the secrets needed to construct a JWT request token. It is NOT a JWT request token itself -- you must generate it from that value.
Generating a JWT request token in code
To authenticate to the API on this page, you need to copy the token string from the JWT Request Token field directly above, and paste it into the jwt field directly below.
A JWT token encoded using your Accounts API Key Shared Secret.
asd8asd9f87ass...asdf9A JSON object which contains the access_token to use in all subsequent calls to the API
Missing or invalid credentials
Not Found
Unknown Error Occurred
Obtain an access_token via User Credentials
[email protected]A JSON object which contains the access_token to use in all subsequent calls to the API
Missing or invalid credentials
Unknown Error Occurred
Obtain a new access_token via a refresh_token
eyJhbGciOiJIUzI1NiIsInR5c...jUZ8Ud9wGCYilcqEML2fRkWZUA JSON object which contains the access_token to use in all subsequent calls to the API
Wrong or expired refresh token, or user/api-key removed
Unknown Error Occurred
Last updated