Netuitive's RESTful API allows you read and write Netuitive data programatically. This means that you can perform a wide variety of tasks, including adding a new integration, returning a filtered list of Events, removing elements from your account, and more. Consult the custom ingest pages for helpful tips and information.
Netuitive requires users to authenticate their requests with HTTP basic auth. Basic authentication uses a standard HTTP header that includes encoded versions of your Netuitive username and password. Basic authentication is required for all endpoints except ingest and ingestevents, which require API keys. To explore Netuitive's REST API and test some requests, go here.
All request parameters associated with date and time (duration, startTime, endTime) must be written in ISO 8601 format. Table 1-13 below demonstrates ISO 8601 formatting.
|Date (Year, Month, and Day)||YYYY-MM-DD or YYYYMMDD|
|Date (Year and Month)||YYYY-MM not YYYYMM|
|Time (hours, minutes, and seconds)||
hh:mm:ss or hhmmss
Note that ISO 8601 uses a 24-hour clock system.
|Time (hours and minutes)||hh:mm or hhmm|
|Combined date and time||
For example, a combination of the date January 13, 2015 and the time 11:30 PM is written as 2015-01-13T23:30.
For duration, an upper case letter indicating a unit of date or time follows its corresponding numerical value. So, where n equals the value of each date or time, duration is written as follows: PnYnMnDnTnHnMnS.
A duration of 1 year, 4 months, 6 days, 12 hours, 35 minutes, and 20 seconds, for example, is represented as P1Y4M6DT12H35M20S.
Also, a duration of 1 month is represented as P1M, while a duration of 1 minute is represented as PT1.
All request parameters associated with conditions (used in the Policy API) must follow a particular format. An example is below to show the syntax and ordering; a table follows to demonstrate the values and valid options.