Hi everyone,
We’re automating gift card fulfilment via the REST API v2 + Make.com and hit one specific blocker. We want to solve this the intended way, not with a hack.
Setup
Customers buy gift cards on our own website (external checkout + payment provider). For each paid order our automation does:
- Create client – POST /admin/clients
- Issue gift card via the “Issue a Gift Card” action (Personalized = Yes, Send Email = Yes, Clients ID = the new client)
The goal is that the buyer receives the single gift card email containing the generated code and the attached gift-card PDF – exactly what happens when we issue it manually in the admin panel.
Problem
Clients created via the API always get email_promo_subscribed = false. As a result the gift card email is not delivered (same as the manual case, where we have to manually uncheck “remove from Email” first).
We tried to set the flag via API:
- PUT /admin/clients/{id} with {“email_promo_subscribed”: true} → HTTP 200, but value stays false (GET confirms false)
- POST /admin/clients with {“email_promo_subscribed”: true} → HTTP 200, but created client still has false
So the field appears read-only via API on both create and update.
Important context
This is NOT marketing. We only want to deliver the ONE transactional email (code + PDF) for a product the customer already paid for – order fulfilment, not promotion. We fully respect marketing-consent rules.
Questions
- Is there an intended way to deliver the gift card email (code + PDF) to an API-created client as a TRANSACTIONAL notification, independent of the
email_promo_subscribedmarketing flag? - Is there any supported API method to set
email_promo_subscribed(or otherwise make an API-created client eligible for this email)? If PUT/POST isn’t correct, what is? - Is there an API endpoint to retrieve the generated gift card CODE and/or the gift card PDF for an issued card? (The issue action doesn’t return the code, and I couldn’t find a PDF endpoint in the docs.) If we could fetch code + PDF, we’d send the email ourselves.
Thanks a lot – any pointer on 1–3 would be hugely appreciated.