[POST] - New Token

Follow

Use the New Token endpoint to generate a new token.  The new token can subsequently be used in the accessToken HTTP header with other API to authenticate and authorize the request.  Refer to Authentication and Authorization Overview article for more details.

Endpoint

POST https://login.insideview.com/Auth/login/v1/token

Request

HTTP Headers

Header Name Type Required Description
Accept String Yes Selects the response's content type.  
Valid values are application/json and application/xml.

Query Parameters

Parameter Name Type Required Description
clientId String Yes Your client ID.
clientSecret String Yes Your client secret.
grantType String Yes Valid values are "cred" and "code".
Use cred for "normal" use of the API.  Use "code" when the token will be used to access the Watchlist API.  An authorization code should be provided.
code String No Authorization code.  Refer to Authentication and Authorization Overview article for more details on how to obtain an authorization code.

 

Responses

HTTP 200

Returns either a JSON or XML data structure depending on the request Accept header. 

application/json Example

{
   "accessTokenDetails":{
      "accessToken": "StVIpD4gwfq8Mlm8+dZd+VeX0n8/oz9sgP7oVdLf3Kml0y+XSkbW2s77mfYZfRvp+Kdv8w4cvC1QZkMPrAPX1VvA/E/n5rT+K8X3Sso+H/ycWPfhdSUfA6sODdSX9nc5vcjYYRvW7qSCAaXPxHDgcWBpm8u/vAmGKkn4BKkq1cM=.eyJncmFudFR5cGUiOiJjcmVkIiwianRpIjoiOTQ2YjFjZmEtNDdhMC00ZjI1LTkwODktM2ViNzJmZDZmYTJmIiwidHRsIjoiMzE1MzYwMCBiLCJpYXQiOiIxNDA1OTc2ODE2IiwiY2xpZW50SWQiOiIzMjhjY252ZXVwbWthMmlqbGk5dCJ9",
      "tokenType":"bearer", 
      "expirationTime":"Tue, Jul 21, 2015 09:08:17 PM GMT" 
   } 
}

application/xml Example

<?xml version="1.0" encoding="UTF-8"?>
<accessTokenDetails>
   <accessToken>StVIpD4gwfq8Mlm8+dZd+VeX0n8/oz9sgP7oVdLf3Kml0y+XSkbW2s77mfYZfRvp+Kdv8w4cvC1QZkMPrAPX1VvA/E/n5rT+K8X3Sso+H/ycWPfhdSUfA6sODdSX9nc5vcjYYRvW7qSCAaXPxHDgcWBpm8u/vAmGKkn4BKkq1cM=.eyJncmFudFR5cGUiOiJjcmVkIiwianRpIjoiOTQ2YjFjZmEtNDdhMC00ZjI1LTkwODktM2ViNzJmZDZmYTJmIiwidHRsIjoiMzE1MzYwMCBiLCJpYXQiOiIxNDA1OTc2ODE2IiwiY2xpZW50SWQiOiIzMjhjY252ZXVwbWthMmlqbGk5dCJ9</accessToken>
   <expirationTime>Tue, Jul 21, 2015 09:06:56 PM GMT</expirationTime>
   <tokenType>bearer</tokenType>
</accessTokenDetails>

HTTP 400

An HTTP 400 error code may have several causes:

  • Validation of inputs failed with one of the following messages:
    • "Bulk enrichment API accepts minimum 1 and maximum 3000 records at a time."
    • "Invalid input (i.e. invalid JSON or XML input)."
  • "2 jobs are already running. Please try again once the previous jobs are finished."

HTTP 401

Unauthorized Error - Cannot use API's without setting a valid accessToken in header.

HTTP 415

The Content-Type mandatory header is not provided.

HTTP 429

Request is throttled.

 

Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk