# Squarespace transactions **URL:** \ **Category:** Ask a question\ **Tags:** Using-APIs\ **Created:** [August 15, 2020, 2:05pm UTC](https://community.parabola.io/t/squarespace-transactions/938 "2020-08-15T14:05:39Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Gabrielle\_Lods](https://avatars.discourse-cdn.com/v4/letter/g/58f4c7/32.png) [@Gabrielle\_Lods](https://community.parabola.io/u/Gabrielle_Lods)\ **Post date:** [August 15, 2020, 2:05pm UTC](https://community.parabola.io/t/squarespace-transactions/938/1 "2020-08-15T14:05:39Z")
Hello! I managed to use Squarespace API for orders and export to google sheet. I’d like to do the same with the Squarespace API for transactions but for some reason, I’m getting the “no result” error message. The API endpoint URL I am using is: [https://api.squarespace.com/1.0/commerce/transactions](https://api.squarespace.com/1.0/commerce/transactions) and I made a specific API key in Squarespace for transactions that I entered in the Bearer Token field. Any tips on how to make it work? Thanks 🙂 ---
**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/brian/32/11_2.png) [@brian](https://community.parabola.io/u/brian)\ **Post date:** [August 17, 2020, 8:26pm UTC](https://community.parabola.io/t/squarespace-transactions/938/2 "2020-08-17T20:26:10Z")
Hey Gabrielle, Can you try hitting the refresh button next to the name of the name of the step, after you open it up? It looks like it should work. Best, Brian ---
**Author:** ![Gabrielle\_Lods](https://avatars.discourse-cdn.com/v4/letter/g/58f4c7/32.png) [@Gabrielle\_Lods](https://community.parabola.io/u/Gabrielle_Lods)\ **Post date:** [August 18, 2020, 12:52pm UTC](https://community.parabola.io/t/squarespace-transactions/938/3 "2020-08-18T12:52:08Z")
Hi Brian, I still get the “No data recieved” after refreshing the step. Best, Gabrielle ---
**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/brian/32/11_2.png) [@brian](https://community.parabola.io/u/brian)\ **Post date:** [August 18, 2020, 4:24pm UTC](https://community.parabola.io/t/squarespace-transactions/938/4 "2020-08-18T16:24:23Z")
I took a deeper look on my end. Looks like a setting was stuck in some weird state. I cleared that up for you and you should be good to go now! Just set the Max Pages to Fetch to the number of pages that you need to pull in! Keeping in mind that each page represents 50 transactions. ---
**Author:** ![Gabrielle\_Lods](https://avatars.discourse-cdn.com/v4/letter/g/58f4c7/32.png) [@Gabrielle\_Lods](https://community.parabola.io/u/Gabrielle_Lods)\ **Post date:** [August 18, 2020, 4:39pm UTC](https://community.parabola.io/t/squarespace-transactions/938/5 "2020-08-18T16:39:51Z")
Indeed it’s working now! Many thanks 🙂 ---
**Author:** ![Gabrielle\_Lods](https://avatars.discourse-cdn.com/v4/letter/g/58f4c7/32.png) [@Gabrielle\_Lods](https://community.parabola.io/u/Gabrielle_Lods)\ **Post date:** [August 18, 2020, 6:02pm UTC](https://community.parabola.io/t/squarespace-transactions/938/6 "2020-08-18T18:02:58Z")
Hummm the last data it’s able to fetch is from 2018-11-06T21:35:41.227Z despite increasing the number of pages to gather data from. Is this a transaction API thing versus the order API that can go back to 2016? ---
**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/brian/32/11_2.png) [@brian](https://community.parabola.io/u/brian)\ **Post date:** [August 21, 2020, 5:19pm UTC](https://community.parabola.io/t/squarespace-transactions/938/7 "2020-08-21T17:19:36Z")
Hey Gabrielle - thanks for your patience. I believe this API is pretty new, so it certainly could have a limitation on how far back it can pull. Could you reach out to their team and ask that? I won’t be able to answer it, but I think it would be valuable for the community to know! Happy to help you answer any questions they have about how you are fetching the data. ---
**Author:** ![Gabrielle\_Lods](https://avatars.discourse-cdn.com/v4/letter/g/58f4c7/32.png) [@Gabrielle\_Lods](https://community.parabola.io/u/Gabrielle_Lods)\ **Post date:** [August 24, 2020, 2:38pm UTC](https://community.parabola.io/t/squarespace-transactions/938/8 "2020-08-24T14:38:45Z")
Hi Brian, Here is there reply: _Would you please be able to share the request you’re currently making when attempting to pull all transactions? My guess here is that if you are using the `modifiedBefore` and `modifiedAfter` parameters, it may be preventing you from pulling the dates you’re looking for. The reasoning behind this is that sometimes if a mass import or something similar has occurred, it will update the modification date to whenever that event happened. By leaving out those parameters, you should be able pull all transactions, regardless of modification date, and then sort by `createdOn.`_ Is this what’s happening here? ---
**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/brian/32/11_2.png) [@brian](https://community.parabola.io/u/brian)\ **Post date:** [August 24, 2020, 7:40pm UTC](https://community.parabola.io/t/squarespace-transactions/938/9 "2020-08-24T19:40:33Z")
Hmm as far as I can tell you are not using those parameters. Your request is as follows: GET [https://api.squarespace.com/1.0/commerce/transactions?nextPageCursor={pagination.nextPageUrl}](https://api.squarespace.com/1.0/commerce/transactions?nextPageCursor=%7Bpagination.nextPageUrl%7D) With `pagination.nextPageUrl` being replaced by the URL in that position in the prior response to page through all available pages. That parameter is omitted from the first call. ---
**Author:** ![Gabrielle\_Lods](https://avatars.discourse-cdn.com/v4/letter/g/58f4c7/32.png) [@Gabrielle\_Lods](https://community.parabola.io/u/Gabrielle_Lods)\ **Post date:** [August 27, 2020, 8:15am UTC](https://community.parabola.io/t/squarespace-transactions/938/10 "2020-08-27T08:15:21Z")
Here is Squarespace reply: Our accounting database and service were both established in 2018, so there are no guarantees for accounting data in our system prior to 01-01-2018. Since the accounting database didn’t go live until Fall of 2018, any 2018 transactions prior to that date had to be backfilled. Whenever there is a backfill, the modifiedOn date of the transaction will be listed on the date when the transaction was backfilled, which is why you will see all 2018 transactions starting in mid-2018. I’ve made a note to our team to add this information to our documentation. In the meanwhile, you can always export your entire order history through the CMS by navigating to Orders --\> Export.