I have looked through the SDK, API and GraphQL documentation and have been unable to find any way to retrieve information for Series/Recurring Invoices (NOT Subscriptions). I’d like to programmatically retrieve series information to track payment behavior.
AI queries make references to “sibling” references, but I can find nothing in the APIs.
Any pointers would be appreciated.
I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:
Retrieve, List, or Search Invoices
Invoices API
Square GraphQL
If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.
Not Helpful. Doesn’t take information presented in Topic Name “(NOT Subscriptions)” into context.
Currently, Square’s APIs, including the Invoices API, do not support direct retrieval of series or recurring invoice information. The Invoices API allows you to create, manage, and retrieve individual invoices, but it does not provide functionality for handling recurring invoice series as a distinct entity separate from individual invoices.
For recurring payments, Square offers the Subscriptions API, which is designed to handle recurring billing scenarios. However, this is distinct from recurring invoices, which are not natively supported as a series in the current API offerings.
If you need to track payment behavior for a series of invoices, you would need to manage this logic within your application. You could do this by tagging or associating individual invoices with a custom identifier that represents the series, and then using the Invoices API to retrieve and manage these invoices individually.
For any updates or changes to the API capabilities, keeping an eye on Square’s developer documentation and release notes would be beneficial.
This answer was reviewed by @Bryan-Square.
This is unfortunate. We tried Subscriptions, but after many attempts, they did not work for us. We had to revert to Recurring Invoices, entailing a lot of manual labor (no API then either), to enable our workflows.