Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
POST method of REST web service inserts a record but does not generate a response - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • POST method of REST web service inserts a record but does not generate a response
KB0596738

POST method of REST web service inserts a record but does not generate a response


11036 Views Last updated : Aug 22, 2022 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

Irrespective of using Table or Import Set API, when you use POST method from a REST web service, a record is inserted in the target table but does not see anything in the Response body. Only "Response Headers" brings some inputs, but "Response Body" is empty.

This is considering you have already assigned the rest_service role to the sys_user record you're using for this integration. Additionally, when you assign the admin role to your integration user record, the response appears in "Response Body".

Cause

This is an ACL-related issue. There is a write ACL in every ServiceNow instance with the name *.sys_id. In general, this ACL comes as inactive in the base system. When customers activate this ACL, they face this problem.

Investigation steps:

  1. Enable system property glide.rest.debug.
  2. Run the POST method and insert a record in target table.
  3. When you check REST debug logs, you see the following message:
    WARNING *** WARNING *** [REST API] TableAPIService : Created record can't be read. No Record found

Resolution

Choose one of solutions below that suits you best:

  1. Deactivate this ACL.
  2. If you activated this ACL due to some business requirement, create one more write ACL and give it the role rest_service.

 

Note: REST Logging includes processing durations, headers, and the request body. Prolonged use of this property can affect performance, so it is best to use it while debugging REST processing, and then set the property back to false.

 

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.