REST API Explorer / task
Investigate inbound REST API rate limit violations
Investigate rate limit violations to determine which rate limit rules are being exceeded and which users are exceeding those rate limits.
THE SERVICENOW DOCUMENTATION LIBRARY
Search the documentation here. No installation, database download, or account needed.
Source: ServiceNow’s public documentation · Australia release · refreshed daily when the sync worker is running.
51,657 documents indexed · Last published Oct 30, 2026 at 06:29 UTC
REST API Explorer / task
Investigate rate limit violations to determine which rate limit rules are being exceeded and which users are exceeding those rate limits.
Authentication / task
You can activate the REST API Auth Scope plugin (com.glide.rest.auth.scope) to link the OAuth entity with authentication scopes.
ERP Integration Framework / concept
Access data from Workday using REST APIs.
REST API Explorer / task
Path-based Access Control Levels (ACLs) enable you to define access control rules for scripted REST API endpoints using their resource path. This can be done independently of the ACL references on the operation record.
Security Incident Response / task
You use the LogRhythm REST API key to gather additional event details for individual alarm fields. The API key provides details that are unavailable using the LogRhythm REST API.
REST API Explorer / reference
This example demonstrates how to send an image attachment to a requesting user as a binary stream.
REST API Explorer / concept
To prevent excessive inbound REST API requests, set rules that limit the number of inbound REST API requests processed per hour. You can create rules to limit requests for specific users, users with specific roles, or all users.
REST API Explorer / task
Create rate limit rules to limit the number of inbound REST API requests processed per hour.
Authentication / task
Create an API access policy and map an authentication profile to restrict the authentication type for a REST API. For example, you can create an API access policy that allows only ID token authentication for a REST API.
DevOps Change Velocity / concept
You can use the Azure Invoke REST API in your YAML or Classic Azure pipeline to configure change control for DevOps.
Developer Guides / reference
The Mobile SDK provides functionality that enables Android applications to call the public REST API on a ServiceNow instance.
Intelligent experiences / task
Increase the maximum allowed inbound content length for scripted REST APIs when automated agentic evaluation runs fail due to inbound payload size limitations.
Authentication / task
You can activate the REST API Access Policy plugin (com.glide.rest.policy) if you have the admin role.
Financial services operations / concept
Financial Services Operations (FSO) leverages the REST Table API to enable external sources, such as bank applications, to interact with the FSO data stored on a ServiceNow instance.
Telecommunications Service Operations Management / reference
Examples of Retrieving Data from Nokia Altiplano via REST API.
Virtual Agent / task
Create a scripted REST API, add a scripted REST resource, set security and content negotiation, and set REST API rate limits.
Usage Insights / task
Submit an export request to the Usage Insights data export API to extract usage data asynchronously and consume results from a Kafka topic.
Order management / reference
Sales Customer Relationship Management (Sales CRM) APIs provide endpoints to create and manage Sales CRM entities such as pricing, leads, quotes, and orders from external systems.
REST API Explorer / concept
Follow these guidelines when designing and implementing scripted REST APIs.
Instance Security Hardening Settings / reference
Use the glide.basicauth.required.databrokerrestapiprocessor property to require basic authorization for all inbound Data Broker Rest API requests.
The same documentation is available through the public REST API.
GET /api/docs/search?q=GlideRecord&limit=20 GET /api/docs/document?path=… GET /api/docs/:id?revision=…
Search returns document paths, IDs, snippets, and an index revision. Read by path for a stable reference; numeric IDs should be used with the returned revision. Document bodies are Markdown.