Is there possibility of any conflict between APIs?When integrating new API, is that going to affect existing APIs integrated in systems in any way?
Hi @Ayushi Kumari ,
It totally depends upon what you are integrating & where, for example if you are adding new API for same integration end point, but this time request/response structure got changed, then it sometimes effect the previous/existing integration method.
If you are integrating the new API in new module or in separate application then there will be very less chance of any conflict.
If you can share your scenario, what kind of new integration you have done and where, then it will be helpful to dig more.
Regards,
Manish Jawla
Hi @Manish Jawla
I’m using an API to fetch data for a few fields on the statement page with NavisionId as the input. I also have a new API that retrieves other fields using NavisionId and ExitDate as input parameters. Both APIs must use the same NavisionId.
You need to check request/response structure of both the API's, if 2 different structures are created by Outsystems, then there will be no conflict but If both API methods are sharing the same structure for (request/response) then there is a chance of conflict.
If you want to avoid such conflict it will be better to have separate request/response structure and do it manually.
check this link as well for reference:
https://success.outsystems.com/documentation/11/integration_with_external_systems/rest/consume_rest_apis/rest_api_structures/
Hope this helps,
regards,
manish Jawla
Thank you for your reply — this will be very helpful in integrating the new API.
Your always welcome
Hello @Ayushi Kumari
Not necessarily. A new API in OutSystems will only affect existing APIs if it changes something they also depend on, such as shared logic, endpoints, authentication, or data structure. If it is implemented separately and backward compatibility is maintained, existing integrations should continue to work normally.
Hi @Goncalo Duarte Almeida
I have a scenario where I’m using an API to fetch data for certain fields on the statement page, with NavisionId as the input. Additionally, I have a new API that retrieves other fields using NavisionId and ExitDate as input parameters. Both APIs must use the same NavisionId to ensure consistency.
Hi @Ayushi Kumari
There is no conflict in this case. Both APIs use the same NavisionId, but they retrieve different data and have different input requirements.
As long as both APIs use NavisionId consistently and do not introduce changes to shared logic or data structures, they can work independently. The main consideration is ensuring that both APIs return consistent data based on the same source..
Hi Ayushi,
When integrating a new API, Service Studio creates seperate structures and methods for this API. I do not know of any conflict that could arise there. But like Manish already wrote, when changing or editing an existing API, e.g. to add a new method manually, or refresh the entire API, the structures can change, as sometimes Service Studio merges two similar structures.
Hi @Kilian Hekhuis
Since the NavisionId is just an integer or a text variable, there is no chance of confusion or mixing things up. You can safely consume both APIs (or both methods of the same API). Only when you are dealing with input or output structures that partially overlap you may need to manually fix things, but in my experience this is almost never needed (and I've consumed quite a number of APIs).