---
title: "Comment by FJ on \"APEX_WEB_SERVICE The Definitive Guide\" | Hashnode"
description: "SOLVED: In my scenario, I'm calling the ORDs endpoint through the OCI API Gateway, so I have something like: OCI APEX -> OCI API Gateway -> ORDS Endpoint"
url: "https://hashnode.com/posts/apexwebservice-the-definitive-guide/65a92ca47fcab2cafb794b34/comment/67dc72d29f99247ebe01c6e6"
---

[Discussion](https://hashnode.com/posts/apexwebservice-the-definitive-guide/65a92ca47fcab2cafb794b34)

Comment [APEX\_WEB\_SERVICE The Definitive Guide](https://hashnode.com/posts/apexwebservice-the-definitive-guide/65a92ca47fcab2cafb794b34)

[FJ](https://hashnode.com/@fjs1)

[Mar 20, 2025](https://hashnode.com/posts/apexwebservice-the-definitive-guide/65a92ca47fcab2cafb794b34/comment/67dc72d29f99247ebe01c6e6)

SOLVED: In my scenario, I'm calling the ORDs endpoint through the OCI API Gateway, so I have something like: OCI APEX -> OCI API Gateway -> ORDS Endpoint (On-Prem APEX on Tomcat/ORDS).

So, by default, withing APEX Restful Services, when REST-Enabling the Schema where the endpoint is, the sample API methods (Resource Templates) are created with an "/" at the end (e.g. "version/". Well, hard to believe but that "/" is the cause of the error (ORA-01031) in this case.

By simply removing the "/" from the name of the API methods everything works as expected.

I hope this may be useful for anyone to save some hours/days of frustration.

Thank you again John for this great article.