Wanted to check if this actually provides a unified api? E.g. each category of integration will return the exact same data shape? From the looks of the video I'm still making a call to slack's API `users.list` and have to write the code to paginate slacks api (e.g. the next cursor).
Comments
Wanted to check if this actually provides a unified api? E.g. each category of integration will return the exact same data shape? From the looks of the video I'm still making a call to slack's API `users.list` and have to write the code to paginate slacks api (e.g. the next cursor).
I think its easier to market "unified API". In practice, it is more like an API to call another API with some niceties like Auth handled + retries
It does!
Because Nango lets you define input & output models of integrations, it's easy to standardize them across APIs.
So, when syncing users from Slack/Discord/Teams, you define a standard User model, and all 3 integrations map to this model.
You then consume User objects from a unified endpoint, regardless of where they come from.