Help Docs


REST API monitor regularly checks the availability and response of your REST API endpoints over IPv4 or IPv6 enabled locations and alerts you if the API response values does not validate against the specified RegEx/XPath/JSONPath assertions. Additionally, test and validate your JSON response against the JSON schema specified by you. To bulk import REST API endpoints, simply upload your predefined HAR/Swagger (JSON)/ CSV file into Site24x7. 

Add REST API Monitor

  1. Login to Site24x7.
  2. Click Admin > Inventory > Monitors > Add Monitor.
  3. Select REST API in Add Monitor page.
  4. Specify the following details to add the website monitor:
    • Display name: Provide an appropriate name for the website which you want to monitor.
    • Endpoint URL: Type the REST Endpoint URL which needs to be monitored.
    • Check frequency: Choose the required polling frequency. The frequency can be set from 30 seconds  to 1 day. 30 seconds can be configured if you're using Enterprise, Enterprise Web, Enterprise Plus Web, Elite, and Elite Web Packs. For all other users 1 minute will be the minimum supported check frequency.

      Configuring 30 seconds check frequency will be consuming the license of two basic monitors.

    • Connection timeout: Specify time in seconds the connection need to establish with the target server.
    • Prefer IPv6: If you want to monitor your endpoint URL over IPv6 enabled locations, simply move the rocker button to "YES" when creating or editing a monitor form.

      • Site24x7 lets you monitor your dual-stacked IPv4/IPv6 based infrastructure as per you need. IPv4 will be enabled as the default protocol. You'll be able to monitor your IPv6 infrastructure, once you enable the rocker button to IPv6. If the connectivity over IPv6 fails, it will not fall back to IPv4 automatically. Read more.
      • Enabling IPv6 in the monitoring form doesn't make it compatible to monitor IPv4, by default. If you want to monitor a resource, which is compatible with both IPv4 and IPv6–you'll have to set up two separate monitor checks for this.

    • Monitoring locations: Select a location profile from the dropdown list from where the website will be monitored.
      To know more, refer Location Profile.
    • Monitor Groups: You can associate your monitor with multiple monitor groups by selecting the relevant monitor groups from the drop down list. This allows in logical grouping of your monitors. 
      To learn how to create a monitor group for your monitors, refer Monitor Groups.
    • Dependent on monitor: Select a monitor from the drop-down list to choose it as your dependent resource. You can add up to 5 monitors as dependent resources. Alerts to your monitor will be suppressed based on the DOWN status of your dependent resource.

      Configuring a dependent resource and suppressing alerts based on the dependent resource's status is part of providing you with better false alerts protection. Learn more about alert suppression at monitor level.


      If you select "None" in the dependent resource field, alerting will progress as per your normal configuration settings. No alerts will be suppressed in this case as the monitor doesn't have any dependent resource.


      Multiple monitor group support for monitors allow a monitor to be associated with multiple dependent resources in different monitor groups. If during a normal monitor status check, any one of these dependent resources' status is identified as DOWN, the alert for the monitor will be automatically suppressed. However, the dependency configuration at monitor level is always given the higher priority over any other monitor group level dependency configuration for suppressing alerts.

  5. Specify the following details for HTTP Configuration:
    • HTTP Method: Specify the method to be used for connecting with the site–POST, GET, PUT, DELETE, and PATCH. Select the appropriate option from the drop-down to configure your form submission method. Also, select the appropriate body type for POST, PUT, PATCH HTTP, and PROPFIND methods.

      Monitoring WebDav APIs
      Web Distributed Authoring and Versioning, or WebDAV, is a protocol that allows users to edit, share, copy, or move documents through an HTTP web server. 
      The following primary HTTP methods that are used by WebDAV are currently supported in Site24x7:

        • PROPFIND
        • PROPPATCH
        • MKCOL
        • COPY
        • MOVE
        • LOCK
        • UNLOCK

      By using these methods, you can now perform:

      Calendar API monitoring
      Calendaring extension to WebDAV, or CalDAV, is an extension of WebDAV that allows users to access or manage calendar-related information on a remote server. It uses the iCalendar format. Using CalDAV, you can synchronize data across devices,  retrieve calendar events, schedule new events, set reminders, etc. Examples: Google Calendar and Apple Calendar provide CalDAV access to their services.

      Contact API monitoring 
      vCard extension to the WebDAV or CardDav is an address book client or server protocol that allows users to access or share data on a web server. It uses the vCard format for the data. CardDAV helps to retrieve, store, and manage personal contact-related information over a remote server. Examples: Google Contacts and Apple's iCloud Contacts use CardDAV.


      POST method would submit the parameters to access the URL. POST submission method supports request sending in FORM, Text, XML, or JSON formats.


      In the GET method, the entire HTML response is fetched and checked for the presence of your configured keywords.

    • Parameter Type: Choose GraphQL if you wish to define the GraphQL query to be sent to the endpoint.
    • GraphQL Query: Provide the GraphQL query to obtain the specific fields in response from the GraphQL-based API service.
    • GraphQL Variables: Specify the values of the variables referred to in the GraphQL query in JSON format.

      GraphQL query and GraphQL variables will be included in the request body if you're choosing the POST method. In the case of the GET method, the GraphQL query and GraphQL variables will be sent through URL Parameters.

    • HTTP Request Headers: Sometimes, you might want to customize the default HTTP request header information. In such cases, the additional header name and header value can be added here.
    • User Agent: Set a customized user agent (web browser) for sending your request and the HTTP headers. You can choose from the available user agents.
    • Authentication Method: Manage multiple authorization methods for your monitors.
      • Basic/NTLM: Configure your Basic/NTLM-based authorization. Windows NTLM is the authentication protocol used on systems running on Windows.
      • Web Credentials: Choose your web credentials for URLs requiring Basic/NTLM-based authentication from the drop-down. Learn how to add/ edit credentials.
      • OAuth: Pick the OAuth radio button, if you're monitoring a resource that is secured by OAuth framework.
        OAuth Provider Name:
        Select the OAuth Provider Name from your preconfigured list or create a new OAuth profile by clicking the + button.

        Learn how to configure an OAuth Provider.

      • Web Token: Register Site24x7 with your authentication server to monitor protected resources using web tokens.

        Learn how to add a Web Token.

      • AWS Signature: Choose an appropriate Amazon account that is already integrated with Site24x7 from the drop-down. This helps in signing the API request using HMAC to authenticate the API hosted on the AWS APIGateway. Learn how to integrate Amazon account.


        Read to learn more about AWS Signature authentication.

    • Client Certificate: For websites that require client certificate authentication, upload the client certificate (has to be a PKCS#12 file.)
    • Query Authoritative Name Server: Use the toggle button to decide if you want to resolve your domain name by an authoritative name server.
    • Accepted HTTP Status Codes: Provide a comma-separated list of HTTP status codes that indicate a successful response. You can specify individual status codes, as well as ranges separated with a colon. Learn more about Accepted HTTP status codes.
    • SSL Protocol: Specify the version number of the TLS/SSL protocol (TLSv1.3, TLSv1.2, TLSv1.1, TLSv1 and SSLv3 supported) to validate proper SSL handshake. Use Auto mode to enable automatic detection and negotiation.

      SSL Protocol validation works only for HTTPS domains. If you've specified a different SSL protocol version than the actual one, the monitor status fails during the poll.

    • HTTP Protocol: Choose the preferred version of the application-layer protocol (HTTP/1.1 or HTTP/2) to be used for negotiation.
    • Enable ALPN: Enable ALPN to ensure that only supported application protocols are sent as part of the TLS handshake and ensure reduced round trip time. By default, it'll be set to Yes. Enable ALPN option isn't supported by On-Premise Poller. We'll be extending the support in the next update
  6. Check Availability: Once you fill in all the mandatory details related to configuration, you can use the option to test the configurations you've created. Service testing helps you to drill deep into code and get hands-on experience.
  7. Specify the following details for Content Checks:
              Choose the response format of your preference.
    • If the selected Response format is Text
      • Should contain string(s): Get alerted when the specified keywords are not present in the website. Mention the keywords in the check box and use the slider button to trigger the required kind of alert.
      • Should not contain string(s): Get alerted when the specified keywords are present in the website content. Mention the keywords in the check box and use the slider button to trigger the required kind of alert.

        You must adhere to the following conditions while adding keywords in the given field:

        • A single string or keyword can be configured with/without any double quotes (ex: HTML).
        • When you are choosing text as the response format, it can be configured in the below format, “{\”cache\":\"success\",\"WSF\":\"success\",\"bean\":\"success\",\"DB\":\"success\"}"
        • If there are two strings, which comprise a single keyword–add a space in between the two strings and enclose it with double quotes. (ex: "HTML response").
        • In case you have more than a couple of individual keywords configured, you will have to separate them with a space and also use double quotes for each of them ("monitor" "HTML").

      • Case sensitive: Enable the toggle button for this option.
      • Should match regular expression: Configure your alert based on whether a particular pattern matches with the website content. For example when you consider the expression ^[a-z0-9_-]{3,15}$, your website content should contain alphabets from a to z,numbers from 0 to 9 , underscore and a hyphen. Also there should be minimum length of 3 characters and maximum length of 15 characters. When it is not matched, your website will be reported as "Regular expression"^[a-z0-9_-]{3,15}$" does not match" as a reason.
      • Learn more about Content Checks.
    • If the selected Response format is XML
      • XPath expression: Provide XPath expression to enable the evaluation of XPath expression assertion. The assertion must successfully parse the XPath in the XML to throw a success. You can add multiple XML expression assertions by clicking the "+" key.
      • XPath Severity: Specify the Alert Severity as "DOWN or TROUBLE" to decide the status when the specified XPath expression assertion fails due to a mismatch.
      • XPath or XML Path Language is a query language for selecting nodes from an XML document. Use the Site24x7 XPath Evaluator for more help.
    • If the selected Response format is JSON
      • JSONPath expression: You can specify a JSONPath assertion and test an expected data in the JSON response. For a successful test, the assertion must successfully parse the JSON Path in the JSON. If you need help to build a JSONPath assertion to test against your JSON response, you can use Site24x7 JSONpath expression for help. You can always add multiple such JSONPath assertions to test individual use cases. Use the "+" key to add more expression assertions.

        Whenever an assertion is processed, the target value in your JSON assertion compares the actual value in the JSON Response to check multiple test scenarios. Common test scenarios that can be checked include:

        • Actual value is empty
        • Actual value is not empty
        • Actual value equals the target value
        • Validates that the actual value is greater than or equal to the target value
        • Validates that the actual value is less than or equal to the target value
        • Actual value contains target value as substring
        • Target value is not contained in the actual value

      JSONPath Expression                             Description                                               Status                   
      $ Select the value of 'city' property which is the direct child of 'address' property.  Status is Up. City property is the direct child of address property


      Select the value of 'country' property which is the direct child of 'address' property.

       Status is Down. There is no child with property 'country' for address property.

      $..type Select the value of all the 'type' properties in the input json.

      Status is Up. The response json has 'type' property as its child.


      Select the length of the 'address' property.

      Status is Up. Address property is present in the response json.

       $..* Select all the properties and its value.

      Status is Up. Response JSON has more than one property. If the JSON response has no property in it then the monitor will report outage.

      $.phoneNumbers[1] Select the 2nd value from the 'phoneNumbers' array. Status UP if there are 2 or more child entities for the phoneNumber property.
      $.phoneNumbers[?(@.number)] Select the 'phoneNumbers' property if it has 'number' property within it. Status will be Up, if the phoneNumber property includes at least a child with number property.
      $.phoneNumbers[?(@.type ==\"iPhone\")]  Select the 'phoneNumbers' property the 'type' is iPhone. Status will be UP if the phoneNumber property includes at least a childr with property type as iPhone.
      $[?(@.age > 20)]

      Select the JSON objects if the 'age' is greater than 20.

      Status will be UP if the age property value is greater than 20.
  8. JSONPath severity: You can specify the Alert Severity as "DOWN or TROUBLE". When the JSONPath assertion fails during a test, an alert will be automatically triggered.
  9. JSON Schema Check: JSON Schema is a vocabulary that allows you to annotate and validate all JSON endpoints for your web service. To test the HTTP response data against the schema, enable the rocker button to YES and post the JSON schema validation assertion in the text field. In case you've kept the text field empty after selecting the rocker button to YES, the data collection will still occur as usual without any impact on the overall monitor status. 
  10. JSON Schema severity: You can specify the Alert Severity as "DOWN or TROUBLE". When the JSON Schema validation fails during a content check, an alert will be automatically triggered based on your setting.

    Below are the common use cases tested when the API responses are validated against the defined JSON schema:

    • Verifying whether values are of a certain type (e.g. integer, string, etc.)
    • Ensuring the API JSON responses are structured properly
    • Checking for the existence of the required keys in the JSON response
    • Test whether an incorrect HTTP response (like an HTML or XML) validates against your given JSON schema.

  11. Should contain HTTP Response Headers: Enter the desired response header and values for your HTTP request and verify whether the HTTP headers are present or the values match with the desired response. Trigger a trouble or down alert during a check failure.
    While configuring the response header check, you must add values based on the following conditions:
    • You can add multiple headers and each header can accept multiple values.
    • A single value can be configured with/without any double quotes (eg.: keep-alive or "keep-alive").
    • In case you have multiple header values configured, you will have to separate them with a space and also use double quotes for each of them. (eg., "gzip" "br").
    • Header value can also support regex validation. The regex pattern should be "${<regex>}". For example : ${\d{4}} can be used to search for four continuous digit numerical value in the value of the header configured in the header name.
  12. HTTP Response Header Severity: Use the toggle button to specify the Alert Severity as DOWN or TROUBLE. When the test fails, an alert will be automatically triggered.
  13. Specify the following details for Configuration Profiles:
    • Threshold and Availability: Select a threshold profile from the drop down list or choose the default threshold set available and get notified when the resources cross the configured threshold and availability.
      To create a customized threshold and availability profile, refer Threshold and Availability.
    • Tags: Associate your monitor with predefined Tag(s) to help organize and manage your monitors creatively. Learn how to add Tags.
    • IT Automation: Select an automation to be executed when the website is down/trouble/up/any status change/any attribute change. The defined action gets executed when there is a state change and selected user groups are alerted.
      To automate corrective actions on failure, refer IT Automation.
  14. Alert Settings:
    • User Alert Group: Select the user group that need to be alerted during a outage.To add multiple users in a group, see User Alert Group.
    • On-Call Schedule: The On-Call Schedule option helps you to ensure that the notifications are sent to assignees in specific shift hours helping them to quickly respond to alerts or incidents. Choose an On-Call of your preference from the drop-down. 
    • Notification Profile: Choose a notification profile from the drop down or select the default profile available. Notification profile helps to configure when and who needs to be notified in case of downtime. Refer Notification Profile to create a customized notification profile.

    You can receive alerts if the monitors are associated to user groups irrespective of the On-Call shift you've configured.

  15. Third-Party Integrations: Associate your monitor with a pre-configured third-party service. It lets you push your monitor alarms to selected services and facilitate improved incident management. If you haven't setup any integrations yet, navigate across to ”Admin > Third Party Integration” to create one. Tell me more.
  16. Click Save. You can click Check and Save if you want to run the configurations and see whether the monitor is performing well and then get the monitor saved. In case of an error, the monitor will not be saved.


    Once the monitor setup is completed, Site24x7 deep discovery wizard scans your domain and auto detects all related internet resources for your domain that can be added to your account for a comprehensive internet services monitoring. Explore more about internet services deep discovery.

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.

We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.

Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!