ServiceNow REST API

Name: ServiceNow REST API
Brand: ServiceNow REST API
Availability: InStock

✓ Official Vendor SpecStorageDatabasebasic, oauth220 EndpointsREST

For Agents

Programmatically create a record, retrieve multiple records. Covers 20 operations with basic, oauth2 authentication.

Install Jentic One Beta

Connect the ServiceNow REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ServiceNow REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fservicenow.com%2Fservicenow" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fservicenow.com%2Fservicenow" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ServiceNow REST API.

Create a record

Retrieve multiple records

Update a record

Partially update a record

GET STARTED

Start building with ServiceNow REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ServiceNow REST API for, with concrete tasks.

★ Storage and Databases Operations

Use the ServiceNow REST API to perform storage operations programmatically. The API provides 20 endpoints covering core functionality including create a record, retrieve multiple records, retrieve a record.

Call POST /now/table/{tableName} to create a record

Automated Table API Management

Automate table API operations by combining multiple ServiceNow REST API endpoints. Agents can retrieve multiple records and then retrieve a record in a single workflow.

Call GET /now/table/{tableName} to retrieve multiple records, then verify the result

AI Agent Integration via Jentic

AI agents discover and call ServiceNow REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic, oauth2 tokens manually.

Search Jentic for 'create a record', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

20 endpoints — servicenow rest apis for managing records, attachments, aggregations, import sets, and cmdb configuration items.

METHOD

PATH

DESCRIPTION

POST

/now/table/{tableName}

Create a record

GET

/now/table/{tableName}

Retrieve multiple records

GET

/now/table/{tableName}/{sys_id}

Retrieve a record

PUT

/now/table/{tableName}/{sys_id}

Update a record

PATCH

/now/table/{tableName}/{sys_id}

Partially update a record

DELETE

/now/table/{tableName}/{sys_id}

Delete a record

GET

/now/stats/{tableName}

Retrieve aggregate statistics

POST

/now/attachment

Upload an attachment

POST

/now/table/{tableName}

Create a record

GET

/now/table/{tableName}

Retrieve multiple records

GET

/now/table/{tableName}/{sys_id}

Retrieve a record

PUT

/now/table/{tableName}/{sys_id}

Update a record

PATCH

/now/table/{tableName}/{sys_id}

Partially update a record

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring ServiceNow by hand means putting your instance name into the base URL, choosing basic auth or an OAuth 2.0 flow, and attaching credentials to every table call yourself. Through Jentic you install once, import ServiceNow from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

ServiceNow puts the table name and record sys_id in the URL path (/now/table/{tableName}/{sys_id}), so a rule can pin your agent to one table: it can read and update records there and nothing else. You choose the operations it may call, so a record delete via DELETE is not included unless you add it.

Credential isolation

Your ServiceNow credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a record in a table' or 'query records', and Jentic returns the matching ServiceNow operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ServiceNow REST API through Jentic.

What authentication does the ServiceNow REST API use?

The ServiceNow REST API uses basic, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create a record with the ServiceNow REST API?

Yes. Use the POST /now/table/{tableName} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the ServiceNow REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a record through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a record'. Jentic returns the matching ServiceNow REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the ServiceNow REST API have?

The ServiceNow REST API exposes 20 endpoints covering table API, aggregate API, attachment API operations.

Can I limit what my agent is allowed to do with the ServiceNow REST API?

Yes. Because you run Jentic One yourself, your own rules decide which ServiceNow operations and credentials the agent can use. ServiceNow puts the table name and record sys_id in the URL path, such as /now/table/{tableName}/{sys_id}, so a rule can pin the agent to a single table where it may read records with GET and update them with PATCH and nothing else. You choose the exact operations it may call, so a destructive DELETE /now/table/{tableName}/{sys_id} or an Attachment upload is available only if you add it.

ServiceNow REST API

Connect the ServiceNow REST API to your agent

Capabilities

Start building with ServiceNow REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs