Internal web API over an existing third-party web API?
Hey all, got a question for ya.
We are using a third-party web API which takes a bit of work getting set up for use within our internal applications (requires certificate, tokens, etc.), as well as re-creating the C# models for all of the different JSON responses.
I was thinking instead of setting up the boilerplate code for the third-party API each time we need it for a new project, that I could just create an internal API that includes all of the code to access the third-party one. And then for our projects, just use the internal one instead which will then call the external API.
I was thinking that it's also a good way to expose only the methods that we need instead of complete free-range access to all of the methods the external API holds.
Is this something that people do? Or is there another way of going about it that I'm not aware of?
I'm using Core 2.1 if that helps at all.
0 comments:
Post a Comment