Easy API: governed APIs for ServiceNow
Give each team and tool an API that works like the Table API, built without code. Then decide exactly what each user and service can reach.
Who has access to your instance right now?
Connections arrive one project at a time. A department here, a supplier there, a monitoring tool someone set up years ago. Each gets an account and a slice of the Table API, and often nobody keeps the full list.
Shared accounts
One integration user serves several systems, so no log says who did what.
Wide-open tables
The Table API reaches whatever a role allows, not just what each connection needs.
No off switch
When one connection misbehaves, cutting it off can cut off others with it.
Built in minutes. Governed from day one.
Easy API runs on your instance, in front of its tables. Spin up the APIs people and systems need, decide what each one can reach, and the standard Table API can stay switched off.
Built in minutes
Pick the tables and fields to offer and release the API in under five minutes, with no code.
It works like the Table API, so the teams using it have nothing new to learn.
Exposed by choice
Decide exactly which data each user, service and API can reach, and nothing more.
No maze of roles and access controls to untangle first.
Off in one click
Disable any API instantly, or isolate a single service, system or connection.
The rest keep running while you deal with the one at fault.
Change the endpoint. Keep everything else.
Moving teams and tools off the Table API sounds like a rebuild. It isn’t. Easy API keeps your authentication and ACLs as they are, so each one moves on its own schedule.
One address changes
Requests, logins and permissions stay as they were. The only thing that stops working is anything the endpoint doesn’t offer.
More in one request
Add related fields to the endpoint itself. Read an incident and get the caller’s name, email and phone in one response.
Then switch it off
When everything has moved, the standard Table API can stay switched off, and nothing that’s moved will notice.
Every request, seen as it happens.
Easy API tracks every request: who made it, what it touched and when, in real time and on your instance. There’s no gateway to host and no middleware to secure, so the record never leaves ServiceNow.
Unifi for bespoke bonds. Easy API for everyday access.
Unifi can handle any integration, but using it to give a team governed access to a few tables is like using a sledgehammer to crack a nut. Easy API does that job simply and at a lower cost, on its own or alongside Unifi.
Bespoke eBonding between ServiceNow and your customers, suppliers and other teams, on any system they use.
See UnifiWhat changes, and what doesn’t.
The questions teams ask before they move a single integration off the Table API.
When will Easy API be available?
Easy API is in development. If controlling access to your instance is on your list, start a conversation and we’ll tell you where it stands.
Does anything need to change to move to Easy API?
Very little. Whatever tables and fields you choose to offer look and behave like the Table API, so existing requests keep working, parameters such as sysparm_fields included.
Do we have to switch off the Table API?
No. Integrations can move across one at a time, and the Table API stays available for as long as anything still needs it. When nothing does, you don’t have to change every table: a single REST API access policy can restrict the Table API across all of them at once.
Can an Easy API do more than the Table API?
Yes. Each API is entirely custom, so it can match the Table API or go further, such as adding related fields.
Does Easy API replace our ACLs?
No. Authentication and ACLs apply exactly as they do today. Each Easy API adds a control on top: it offers only the tables and fields you’ve chosen, so nothing reaches more than both allow.
Tell us what connects to your instance today.
Easy API is coming soon, but there’s no need to wait to talk. We’ll show you how it works and help you plan the move off the Table API.