oRPC Input/Output Structure

To configure oRPC input structures, use detailed mode to separate path parameters and body data into distinct parts of the request, or use compact mode to combine them for simpler data organization.

The detailed output structure in oRPC separates the API response into three distinct objects: status, headers, and body, providing fine-grained control over the response format for complex operations.

You need detailed mode for oRPC request and response objects when performing complex operations like API integrations or third-party data exchanges where predictable data structure separation is critical.

Yes, oRPC supports compact output structures by providing a single response object that combines all response data together, offering a simpler alternative to the detailed mode for basic API handling.

The best way to organize API data in oRPC for third-party exchanges is by configuring detailed input and output structures, which separates request parts and response components to ensure predictable formats.