Again this may be based on customer type, with higher paying customers receiving a higher usage allowance. You should also think about any usage limits that you want to enforce for your customers. As previously mentioned, this will probably be tied to any existing contracts you have with your customers. Now that you have a clear idea of the sort of functionality you want to make available and your audience, you’ll want to think about exactly which resources you want to expose as well as the operations you want to expose on them. You probably have a pre-existing relationship with your API consumers before they start using your API. As such, you may want to provide API access automatically for all user accounts, or only to customers on certain contracts. Some examples of successful companies that use APIs to enable customers to tightly integrate with their platform through APIs include Zendesk, a customer support platform that exposes an API to allow their customers to automate and enhance their customer support, and Dropbox, which has both a Core API and Dropbox for Business API that allows business customers to easily administer team accounts and monitor usage and activity.Īlthough APIs to enable customer integrations are generally publicly documented and free to use, they’re often restricted for use by existing customers only. You may also choose to expose your API to partners, in which case you might find the partner integrations section useful too. The "customer ecosystem" use case involves using APIs to allow existing customers to automate the processes they run on your system, to use bulk operations or just integrate more tightly with your system. Partner Integration"Ĭollapse section "2.4. Customer Integration"Ĭollapse section "1.4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |