Support
Reach unPLUG when you're stuck, and send what we need to answer on the first reply. Some setup still goes through support today; those tasks are listed below.
Contact#
Email support@unplugdining.com. One address covers questions, setup requests and security reports.
Start the subject with "Security:" for anything that could affect guests' data or accounts, such as a leaked key or a vulnerability. See Security.
What to include#
- Your brand name, as it appears in the unPLUG dashboard.
- The environment: sandbox or production.
- The
Request-Idfrom the response header, orrequest_idfrom the error body, for examplereq_7Hq2kD9xLm. It lets us find your exact request. - What you sent and what you got back: the endpoint, the request body and the full error response.
- For webhooks: the event id (the
webhook-idheader) and your endpoint id. - When it happened, with time zone.
Warning Never send a secret key, a member token or a webhook signing secret. Remove them from logs and curl commands before you paste them. If you need to point at a key, send its first few characters. We never ask for a full key.
What support handles today#
Until the developer dashboard ships, these go through support:
| Task | What to send |
|---|---|
| Issue a secret key | Environment and the scopes the key needs. |
| Rotate or revoke a key | The key's prefix and whether to revoke now or after you've deployed the new one. |
| Upload push credentials | Ask for a secure upload link for your Firebase service account JSON and APNs .p8 key, plus Key ID, Team ID, bundle id and package name. See Push and in-app messages. |
| Webhook help | Endpoint id and the event ids involved. Support can also create an endpoint for you. |
| A sandbox | See Request a sandbox. |
| Data sharing Coming soon | See Request data sharing. |
| Go-live review | Your completed checklist. See Going live. |
| IP allowlists and higher rate limits | The key's prefix and the addresses or limits you need, with your expected traffic. |
| Security reports | Subject starting "Security:". See Report a vulnerability. |
Loyalty settings themselves (earn rate, tiers, rewards, campaigns) stay in the unPLUG dashboard, not in the API or in developer support.
Response times#
Target: a first reply within one business day. Leaked keys are revoked within one hour on business days. A go-live review takes about 2 business days once we have your sandbox run.
Developer dashboard Coming soon#
A self-serve dashboard for credentials only:
- Create, roll and revoke secret keys.
- Manage webhook endpoints.
- Upload push credentials.
- Read request logs.
It won't change loyalty settings; those stay in the unPLUG dashboard. The changelog will say when it's available.