When accessing a table via REST API, authentication is required for every request.

When accessing a table via REST API, authentication is required for every request.

• A. True
• B. False
• C. Only for read operations
• D. Depends on endpoint

Answer: (A)

When you call the Table API in ServiceNow, every HTTP request must prove who you are. REST calls are stateless, so the server treats each request independently and requires valid authentication on each one. You provide credentials or a token for every call (for example, using Basic authentication or an OAuth access token, or a session cookie that represents a logged-in user), and the server will only perform the operation if the authentication check passes. If you omit authentication, you’ll get a 401 Unauthorized, regardless of whether you’re reading or writing data. The idea that authentication is needed only for reads or depends on the endpoint doesn’t apply to the typical Table API behavior—the default is that every request must be authenticated.

When you call the Table API in ServiceNow, every HTTP request must prove who you are. REST calls are stateless, so the server treats each request independently and requires valid authentication on each one. You provide credentials or a token for every call (for example, using Basic authentication or an OAuth access token, or a session cookie that represents a logged-in user), and the server will only perform the operation if the authentication check passes. If you omit authentication, you’ll get a 401 Unauthorized, regardless of whether you’re reading or writing data. The idea that authentication is needed only for reads or depends on the endpoint doesn’t apply to the typical Table API behavior—the default is that every request must be authenticated.