is there any difference between eBonding and REST API ?

[Ronak3]

Hello Community,

We are actually trying to setup integration between ADDM and CMDB to get data to CMDB. The question i have is, Can we use eBonding for such integration (which will be through REST API) OR since eBonding is bi-directional integration and our integration is one way, do we still call it as eBonding or just REST integration?

I want to know the difference between eBonding and REST?

Is the term eBonding used only for Bidirectional data synchronization or even one side?

It's being difficult to make customer understand why eBonding and why REST. Pls someone clear my questions.

[DScroggins]

Hello. eBonding is merely a term to describe an integration. In the case of Flow Designer eBonding is the use of REST based integration. For an integration between ADDM and your CMDB you would use either the OOB REST API or build a custom Scripted REST API to handle your requirements. Hope this helps.

--David

[Ronak3]

Thank you David! This information would help. Can you let me know one more thing. eBonding (or integration) can be used for Bi-directional data sync or it can be one direction data sync too? We do the same when it comes to REST API right? So when i have to say what is the difference b/w eBonding and REST API what can it be? eBonding term is specifically used where?

[DScroggins]

It can be one way or bidirectional. They are one in the same. ebonding vs REST API is the same thing. ServiceNow uses the term ebonding.