Support · avg. response time 2h

How can we
help you?

Search our docs, recover credentials, or raise a ticket. We're here.

⌘K

Email support

Send us a detailed message. We read every email and respond with a real engineer, not a bot.

Response within 4–8 hours · Mon–Fri

support@tickitz.io

Live chat

Chat with our team in real time for fast answers on integration questions, billing, or incidents.

Available 9 AM–6 PM IST · Typically < 5 min wait

Documentation

Comprehensive guides, API reference, SDK docs, and runbooks for every Tickitz module.

Always up to date · Versioned

Browse docs →

All systems operational

Last checked 2 min ago

API Webhooks Queue (degraded) Dashboard Check-in

Full status page →

04 — Credentials

Lost your API key
or suspect a leak?

API keys are only shown once at creation. If you've lost yours or believe it may be compromised, act immediately — don't wait.

Lost API key — recovery steps

You cannot retrieve an existing key. The only option is to revoke it and issue a new one. Here's how:

1Go to Dashboard → Settings → API Keys
2Locate the key (identified by name/prefix, e.g. sk_live_abc…)
3Click Revoke — this immediately invalidates the key
4Click Create new key, give it a descriptive name
5Copy and store it securely (password manager, secrets vault)
6Update your environment variables and redeploy

Think your credentials are compromised?

Revoke immediately, then:

Check your API logs for unusual activity in Dashboard → Logs
Audit any bookings or events created in the last 24–72 hours
Rotate all keys in the affected environment (staging + production)
Email security@tickitz.io with the incident details
We'll flag and freeze suspicious activity on our end

API key best practices →

05 — Raise a ticket

Tell us
what's wrong.

New support ticket

We respond to every ticket within 4 hours

Your name

Common
questions.

Can't find what you're looking for? Raise a ticket and we'll get back to you.

Raise a ticket →

No. API keys are displayed only once at creation time. If you've lost access, revoke the key immediately via Dashboard → Settings → API Keys and generate a new one. Store it securely in a secrets manager or password vault.

Revoke the key immediately — this cuts off access within milliseconds. Then check your API logs for unauthorized requests, rotate all keys in the affected environment, and email security@tickitz.io with the approximate time and scope of exposure. We'll investigate and freeze any suspicious activity.

Create a new key first, update your environment variables and deploy, confirm the new key is live and responding, then revoke the old key. Both keys are valid simultaneously during the transition — there's no need for a maintenance window.

First check Dashboard → Webhooks → Delivery Logs to see if events are being sent and what status code your endpoint is returning. Common causes: endpoint returning non-2xx status, SSL certificate issues, HMAC signature validation failures, or the event type not being subscribed. Tickitz retries failed deliveries up to 5 times with exponential back-off.

This means the ticket was already scanned and the attendee was admitted. The response also includes checkedInAt (the timestamp of the first scan) and scannedBy (the staff ID that performed it). Use this to identify duplicate tickets or potential fraud.

The free tier includes up to 1,000 bookings per month, all 10 SDK modules, webhook delivery, QR check-in, and community support. No credit card required to start. Paid plans unlock higher volume, dedicated support SLAs, and fraud detection thresholds.

Yes. Pro plans include a 99.9% monthly uptime SLA. Enterprise plans include 99.99% SLA with dedicated incident response and a named account engineer. Downtime credits are applied automatically — no need to raise a claim.

Use GET /v1/events/:id/bookings with ?format=csv or ?format=json to export programmatically. You can also download exports from the Dashboard under each event's "Attendees" tab. All exports include PII fields; ensure you handle them according to your privacy policy.

Still need help?

A real engineer reads every ticket. Typical response time is under 4 hours on business days.

Raise a ticket → Email us

support@tickitz.io · security@tickitz.io

How can wehelp you?