OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Table API returns paginated records with sysparm_limit/offset, selected fields and display-value options. Reference IDs and display text need separate treatment.
ServiceNow Table API retrieval ↗
GET records, sysparm_query, fields and pagination · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Table API returns paginated records with sysparm_limit/offset, selected fields and display-value options. Reference IDs and display text need separate treatment.
ServiceNow Table API retrieval ↗
GET records, sysparm_query, fields and pagination · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
sysparm_query and sysparm_fields support encoded predicates, ordering and field selection. Invalid-query behavior and inaccessible fields depend on instance controls.
ServiceNow Table API retrieval ↗
GET records, sysparm_query, fields and pagination · Checked 2026-10-16
Access cost barrier -
-
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Product/table entitlement and purchased integration rights depend on the customer agreement. A complete lowest-plan and fixed API-fee statement remains unresolved.
ServiceNow inbound REST rate rules ↗
Configured rules, response headers and Retry-After · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
The instance supports authenticated external REST integrations with Basic/OAuth and API ACL checks. Customer administrators configure access; the reviewed sources do not establish every third-party distribution/program requirement.
ServiceNow REST integration security ↗
Authentication, API ACLs and external integration requests · Checked 2026-10-16
Downstream permission -
-
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
ServiceNow REST integration security ↗
Authentication, API ACLs and external integration requests · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Table API documents POST insert, PATCH update and DELETE operations. Table/field ACLs, data policy and business behavior remain constraints for each target.
ServiceNow Table API mutation operations ↗
POST, PATCH and DELETE records · Checked 2026-10-16
Custom application path -
-
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Customer API authorization is documented; eligibility and approval requirements for the chosen third-party application remain unresolved.
ServiceNow REST integration security ↗
Authentication, API ACLs and external integration requests · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Table queries can filter sys_updated_on for overlapping incremental reads. Hard deletes and business-rule side effects require separately configured audit or reconciliation routes.
ServiceNow Table API updated-time queries ↗
Encoded sysparm_query and sys_updated_on selection · Checked 2026-10-16
Limit visibility 7.5/10
Service-specific limits disclosed in runtime headers
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Customer-configured inbound REST rate rules govern users/roles/resources. Rate-limit headers and 429 Retry-After are documented; the example limit is not a universal platform quota.
ServiceNow inbound REST rate rules ↗
Configured rules, response headers and Retry-After · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
sys_updated_on polling identifies changed records; complete deleted-record identity capture is not established by the selected Table API route.
ServiceNow Table API updated-time queries ↗
Encoded sysparm_query and sys_updated_on selection · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Current table snapshots can rebuild accessible records; no retained ordered update/deletion event stream is established.
ServiceNow Table API updated-time queries ↗
Encoded sysparm_query and sys_updated_on selection · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Customers can export selected lists as CSV/XML or retain Table API records. Export row limits, references, attachments, audit history and executable application configuration need separate checks.
ServiceNow selected list exports ↗
CSV/XML URL exports and query limits · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
ServiceNow selected list exports ↗
CSV/XML URL exports and query limits · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Customers can export selected lists as CSV/XML or retain Table API records. Export row limits, references, attachments, audit history and executable application configuration need separate checks.
ServiceNow selected list exports ↗
CSV/XML URL exports and query limits · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
ServiceNow REST integration security ↗
Authentication, API ACLs and external integration requests · Checked 2026-10-16
Rights to custom logic -
-
ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
ServiceNow REST integration security ↗
Authentication, API ACLs and external integration requests · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
The instance supports authenticated external REST integrations with Basic/OAuth and API ACL checks. Customer administrators configure access; the reviewed sources do not establish every third-party distribution/program requirement.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Table API returns paginated records with sysparm_limit/offset, selected fields and display-value options. Reference IDs and display text need separate treatment. sysparm_query and sysparm_fields support encoded predicates, ordering and field selection. Invalid-query behavior and inaccessible fields depend on instance controls.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | HTTP Basic | Customer | Not confirmed | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Product/table entitlement and purchased integration rights depend on the customer agreement. A complete lowest-plan and fixed API-fee statement remains unresolved.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Table API documents POST insert, PATCH update and DELETE operations. Table/field ACLs, data policy and business behavior remain constraints for each target.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Table queries can filter sys_updated_on for overlapping incremental reads. Hard deletes and business-rule side effects require separately configured audit or reconciliation routes. Customer-configured inbound REST rate rules govern users/roles/resources. Rate-limit headers and 429 Retry-After are documented; the example limit is not a universal platform quota.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. sys_updated_on polling identifies changed records; complete deleted-record identity capture is not established by the selected Table API route. | ServiceNow Table API updated-time queries ↗Encoded sysparm_query and sys_updated_on selectionChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Current table snapshots can rebuild accessible records; no retained ordered update/deletion event stream is established. | ServiceNow Table API updated-time queries ↗Encoded sysparm_query and sys_updated_on selectionChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Customers can export selected lists as CSV/XML or retain Table API records. Export row limits, references, attachments, audit history and executable application configuration need separate checks.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Table API returns paginated records with sysparm_limit/offset, selected fields and display-value options. Reference IDs and display text need separate treatment. | ServiceNow Table API retrieval ↗GET records, sysparm_query, fields and paginationChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Table API returns paginated records with sysparm_limit/offset, selected fields and display-value options. Reference IDs and display text need separate treatment. | ServiceNow Table API retrieval ↗GET records, sysparm_query, fields and paginationChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. sysparm_query and sysparm_fields support encoded predicates, ordering and field selection. Invalid-query behavior and inaccessible fields depend on instance controls. | ServiceNow Table API retrieval ↗GET records, sysparm_query, fields and paginationChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. The instance supports authenticated external REST integrations with Basic/OAuth and API ACL checks. Customer administrators configure access; the reviewed sources do not establish every third-party distribution/program requirement. | ServiceNow REST integration security ↗Authentication, API ACLs and external integration requestsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Product/table entitlement and purchased integration rights depend on the customer agreement. A complete lowest-plan and fixed API-fee statement remains unresolved. | ServiceNow inbound REST rate rules ↗Configured rules, response headers and Retry-AfterChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | ServiceNow REST integration security ↗Authentication, API ACLs and external integration requestsChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Table API documents POST insert, PATCH update and DELETE operations. Table/field ACLs, data policy and business behavior remain constraints for each target. | ServiceNow Table API mutation operations ↗POST, PATCH and DELETE recordsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | -ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Customer API authorization is documented; eligibility and approval requirements for the chosen third-party application remain unresolved. | ServiceNow REST integration security ↗Authentication, API ACLs and external integration requestsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Table queries can filter sys_updated_on for overlapping incremental reads. Hard deletes and business-rule side effects require separately configured audit or reconciliation routes. | ServiceNow Table API updated-time queries ↗Encoded sysparm_query and sys_updated_on selectionChecked 2026-10-16 |
| How are integration limits disclosed? | Service-specific limits disclosed in runtime headersServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Customer-configured inbound REST rate rules govern users/roles/resources. Rate-limit headers and 429 Retry-After are documented; the example limit is not a universal platform quota. | ServiceNow inbound REST rate rules ↗Configured rules, response headers and Retry-AfterChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Customers can export selected lists as CSV/XML or retain Table API records. Export row limits, references, attachments, audit history and executable application configuration need separate checks. | ServiceNow selected list exports ↗CSV/XML URL exports and query limitsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | ServiceNow selected list exports ↗CSV/XML URL exports and query limitsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | ServiceNow REST integration security ↗Authentication, API ACLs and external integration requestsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -ServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Native workflow ownership, reusable export and independent execution rights remain unresolved. | ServiceNow REST integration security ↗Authentication, API ACLs and external integration requestsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedServiceNow / customer instance Table API, ACL-permitted incident/task-style records and selected CSV/XML exports; application-specific licensing, custom integrations and complete instance backup are separate. Customers can export selected lists as CSV/XML or retain Table API records. Export row limits, references, attachments, audit history and executable application configuration need separate checks. | ServiceNow selected list exports ↗CSV/XML URL exports and query limitsChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Applicable downstream processing and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.