In a payment system, what we need to track and use as data for further analysis is related to what is happening in our system.įor example, we would like to track when a new payment has happened, when something went wrong with a transaction, etc. However, we do not need to access these endpoints for analytic purposes. The Square Connect API allows us to use the Square platform to execute payment transactions, so many endpoints are related to these tasks. In this post, we will focus on how to get meaningful data out of the Square Connect API that can be used for analytics. Thus each one offers different opportunities for pulling useful data out of it. Pull data from the Square platformĪs mentioned earlier, Square exposes a number of APIs for different applications. This might change in the future and is not officially documented to handle our requests and responses properly. The current rate is on the order of 10 QPS. If this occurs, try your request again at a later time. If Connect API endpoints receive too many requests associated with the same application or access token in a short time window, they might respond with a 429 Too Many Requests error. This token gives your application full access to your own Square account. One of these credentials is the personal access token. The application dashboard displays your new app’s credentials.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |