{"__v":0,"_id":"5818e06dbeb0c20f000d445e","category":{"__v":19,"_id":"5615790d0f5ed00d00483dd5","pages":["5615790e0f5ed00d00483dd7","561d48e46386060d00e06003","561d48fe31d9630d001eb5bd","561d49b657165b0d00aa5d8b","561d4a879463520d00cd11e2","561d67f48ca8b90d00210234","561d6a0bf0cff80d00ca22c3","561d6c5b071cd60d000d3221","562f9c2543c5570d001fe6bd","56311c99eae7ef0d00270e3d","56311d6702aff217007dba23","56311f96f1c0580d00fac719","563120b7242cda1900198b79","5631229bf1c0580d00fac721","563131559ead230d00a188f6","563134a324014b0d00bd9a4f","5631392082d96a0d00b0fb1d","56313c584b36120d00fdebfb","5642658ef424a10d00118360"],"project":"5615790c0f5ed00d00483dd1","version":"5615790d0f5ed00d00483dd4","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-10-07T19:57:01.871Z","from_sync":false,"order":0,"slug":"opendns-investigate-rest-api","title":"Umbrella Investigate REST API"},"parentDoc":null,"project":"5615790c0f5ed00d00483dd1","user":"560b40145148ba0d009bd0b5","version":{"__v":6,"_id":"5615790d0f5ed00d00483dd4","project":"5615790c0f5ed00d00483dd1","createdAt":"2015-10-07T19:57:01.307Z","releaseDate":"2015-10-07T19:57:01.307Z","categories":["5615790d0f5ed00d00483dd5","56157b2af432910d0000f9fe","56157cfb0f5ed00d00483ddb","562684d95db46b1700fd4f48","573b7ea9ef164e2900a2b8ff","582e285d8373c20f00810608"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-11-01T18:35:25.285Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"The information provided in the Umbrella Investigate API is the result of statistical analysis run against DNS traffic and oriented toward security research. These results are generated from the terabytes of DNS traffic to the Umbrella DNS resolvers and not from samples of infected websites or clients. As such, they are considered to be predictors or indicators of potentially malicious domains or IPs. With the exception of the Domain Status categorization, the scores generated for any given IP or domain are intended to assist with predictive analysis and to find additional information regarding network activity deemed suspicious as part of research into security incidents.\n\nCisco Umbrella reserves the right to add fields to the API endpoints and methods listed below. However, we will not remove any of the endpoints listed below in future versions of the API.\n\n##Authentication \n\nAuthenticate to the Investigate API by providing one of your API access tokens in the request. You can create and manage your API access tokens from your account settings. You can have multiple API access tokens active for use at a given time. Your API access tokens carry many privileges, so be sure to keep them secret and do not expose them on public web resources!\n\nAuthentication to the API occurs by providing your access token in the authorization header via HTTP Basic Auth. Provide your API access token as the basic auth username for API queries; there's no need to provide your username or password from the Investigate user interface.\n\nAll API requests must be made over HTTPS. Calls made over plain HTTP will fail. You must supply a valid access token in all requests.\n\nAuthentication to the Investigate GUI is controlled by the account settings. This is where you can add additional administrative accounts and provision or delete API tokens. Create and manage your API access tokens from the Investigate interface by clicking on the Setting gear in the upper right corner of the page, and selecting \"API Access\"\n\nThis page will be empty when you first visit it. \n1. To create your first API Access token, simply click **create new token**. \n2. Give the token a name and click **Create**. The generated token includes the email address of the person who created it and the creation date. The token is revokable by clicking the delete icon.\n\n---\n[Introduction to Cisco Umbrella Investigate](https://docs.umbrella.com/developer/investigate-api/introduction-to-cisco-investigate/) < **About the API and Authentication** > [Coding Examples](https://docs.umbrella.com/developer/investigate-api/coding-examples-1/)","excerpt":"","slug":"about-the-api-authentication","type":"basic","title":"About the API and Authentication"}

About the API and Authentication


The information provided in the Umbrella Investigate API is the result of statistical analysis run against DNS traffic and oriented toward security research. These results are generated from the terabytes of DNS traffic to the Umbrella DNS resolvers and not from samples of infected websites or clients. As such, they are considered to be predictors or indicators of potentially malicious domains or IPs. With the exception of the Domain Status categorization, the scores generated for any given IP or domain are intended to assist with predictive analysis and to find additional information regarding network activity deemed suspicious as part of research into security incidents. Cisco Umbrella reserves the right to add fields to the API endpoints and methods listed below. However, we will not remove any of the endpoints listed below in future versions of the API. ##Authentication Authenticate to the Investigate API by providing one of your API access tokens in the request. You can create and manage your API access tokens from your account settings. You can have multiple API access tokens active for use at a given time. Your API access tokens carry many privileges, so be sure to keep them secret and do not expose them on public web resources! Authentication to the API occurs by providing your access token in the authorization header via HTTP Basic Auth. Provide your API access token as the basic auth username for API queries; there's no need to provide your username or password from the Investigate user interface. All API requests must be made over HTTPS. Calls made over plain HTTP will fail. You must supply a valid access token in all requests. Authentication to the Investigate GUI is controlled by the account settings. This is where you can add additional administrative accounts and provision or delete API tokens. Create and manage your API access tokens from the Investigate interface by clicking on the Setting gear in the upper right corner of the page, and selecting "API Access" This page will be empty when you first visit it. 1. To create your first API Access token, simply click **create new token**. 2. Give the token a name and click **Create**. The generated token includes the email address of the person who created it and the creation date. The token is revokable by clicking the delete icon. --- [Introduction to Cisco Umbrella Investigate](https://docs.umbrella.com/developer/investigate-api/introduction-to-cisco-investigate/) < **About the API and Authentication** > [Coding Examples](https://docs.umbrella.com/developer/investigate-api/coding-examples-1/)