Passing a custom callback function to `plsql_rest_sender_api.call_rest_endpoint` (rather than the `_empty_body` variant) fails with a wrong-number-or-type-of-arguments error inside the platform's own common callback handler.

Q: Passing a custom callback function to `plsql_rest_sender_api.call_rest_endpoint` (rather than the `_empty_body` variant) fails with a wrong-number-or-type-of-arguments error inside the platform's own common callback handler.

The built-in REST_Common_Callback procedure needs to be called with a specific, complete argument list (including a key reference and the requesting FND user, alongside the result and application-message ID) in order to correctly forward the response through to your actual custom callback function — a mismatch or missing argument in that specific call is what produces the wrong-number-of-arguments error; passing the full expected argument set resolves it and lets the response reach your own callback logic correctly.

Answer

The built-in REST_Common_Callback procedure needs to be called with a specific, complete argument list (including a key reference and the requesting FND user, alongside the result and application-message ID) in order to correctly forward the response through to your actual custom callback function — a mismatch or missing argument in that specific call is what produces the wrong-number-of-arguments error; passing the full expected argument set resolves it and lets the response reach your own callback logic correctly.

← Browse Integrations and APIs questions