Difference between revisions of "Why use an API"
From Charitylog Manual
(Created page with "The are 2 main reasons for using an API: 1) Where you need to access your data in another application. This might be for data analysis, or syncing records where there is some...") |
|||
| Line 1: | Line 1: | ||
| + | [[API Details|Go to API overview]] | ||
The are 2 main reasons for using an API: | The are 2 main reasons for using an API: | ||
1) Where you need to access your data in another application. This might be for data analysis, or syncing records where there is some overlap, e.g. if some of your clients in Charitylog/Crossdata are also donors in your donor management system. | 1) Where you need to access your data in another application. This might be for data analysis, or syncing records where there is some overlap, e.g. if some of your clients in Charitylog/Crossdata are also donors in your donor management system. | ||
2) Where you want more freedom in the way your data is presented. Typically this is where you have complex reporting requirements that go beyond what can do done using the many reports in Charitylog/Crossdata. | 2) Where you want more freedom in the way your data is presented. Typically this is where you have complex reporting requirements that go beyond what can do done using the many reports in Charitylog/Crossdata. | ||
Revision as of 10:56, 10 June 2020
Go to API overview The are 2 main reasons for using an API: 1) Where you need to access your data in another application. This might be for data analysis, or syncing records where there is some overlap, e.g. if some of your clients in Charitylog/Crossdata are also donors in your donor management system. 2) Where you want more freedom in the way your data is presented. Typically this is where you have complex reporting requirements that go beyond what can do done using the many reports in Charitylog/Crossdata.
