Kindly, can anyone differentiate between System api and Process api? Please provide answer in Generic terms, as i am unable to find on internet.
The Experience API lets you expose the API to the end user. The Process API lets you validate the file extension as . csv or not. A system API will carry out the system level processes, such as validating the file contents and processing them to the database.
Process APIs: Process APIs interact with and shape data within a single system or across systems — breaking down data silos. Process APIs provide a means of combining data and orchestrating multiple System APIs for a specific business purpose.
In your system API you have retrieved data or any transformation done after that you want to consume it all in you process API then you must have use " HTTP request" connector as endpoint in System API and in process API you need to use "HTTP Listener connector" and configured with same port number whatever you have ...
A system api abstracts from an existing system. It talks to the system in the language of the system (e.g. SOAP, direct Java calls, SAP calls, etc.). To the outside world it offers a clean API (usually REST with http and json). When you do a good job implementing your system api, you can exchange your existing system with a different/new one without changing the api of your system api to the outside world: Just implement a new system api with different adapter logic.
A process api should talk REST on "both ends". It calls one or several system apis to do its job. The process api orchestrates different jobs.
When you need more information, do a search with "api led connectivity"
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With