Is there any update on this?
1 Like
At this time there aren’t any additional updates on this particular feature request. 
Hi Bryan, is there any update on this? or any other workaround to add this feature?
1 Like
I’d love to add support for this long-awaited feature! Just tested a coupon QR code created from the dashboard on the Square for Retail POS app and worked like a charm, so being able to programmatically create a discount code would be so ideal to support this workflow.
1 Like
We would all really like a coupon API to create coupons like you would here:
https://app.squareup.com/dashboard/customers/marketing/coupons/new
Please help!
1 Like
Hi, I’d like to be able to create promo codes or discount codes via the API. Is that possible?
+1 to interest. Figured we’d post, as we’ve been keeping an eye on this feature request for over a year..
We create 50+ individualized coupons on a monthly basis for our growing Patreon subscriber base for them to use towards “Events” we have available on our site (e.g. Online (not POS)). It would be great if we can programmatically create these on a monthly basis via a combination of workflow automation and Square API.
We even considered a workaround to utilize the Customer/Customer Group feature with Discounts - but are unable to tie both a Category and/or individual Catalog item to a Customer Group within a Discount. Even if it were possible, Customer Group “Discount Rules” only allow POS.
If this is such a “very popular feature request” - why has this gone with no updates or movement for over 3-5 years…? Could we get a genuine update or an idea of the timeline? If API exposure is not a possibility or not projected to be available for another 3-5 years, what about simply implementing a bulk import feature like the Item Library has?
1 Like
Another +1 for this feature.
Use case is to provide a “button” on an internally developed custom page (we’re a very small volunteer org) to permit our treasurer to generate and email a one-time-use coupon code to someone who’d like to cancel a reservation they’ve purchased for an annual event. We don’t do refunds, but far enough in advance, we’d like to offer a single-use coupon code to the person for next year’s event. We don’t want a blanket code because it would likely get shared, so single use means a new coupon for each person. Yes, our treasurer could log into the square console and create a new coupon with all the same settings for each person, but that’s just a time-waster for someone who’s already a volunteer, especially when, as has already been pointed out, the APIs must exist somewhere.