# Contacting us > Which address handles what, what to put in a message so we can act on it, and what to expect back. Source: https://hyperjobs.io/help/contact Four addresses, each read by people who can actually act on that kind of message. Picking the right one is the difference between an answer and a forward. | What it's about | Where to write | | --- | --- | | Technical questions, bugs, wrong data | | | Plans, billing, custom limits, flat-file delivery | | | Security disclosure | | | Data protection, GDPR, account deletion | | If you're genuinely unsure, is the safe default — it gets routed. ## Before you write A lot of questions already have written answers, and they're faster than we are: - **A request is failing, or a filter returns nothing** — [troubleshooting](/docs/support) covers the usual suspects, and zero-results is nearly always a silently-ignored filter value. - **An error code you don't recognise** — [errors](/docs/errors). - **`429`s** — [rate limits](/docs/rate-limits) and [your quota](/help/quotas). - **A key you lost** — it can't be recovered, only replaced. See [managing API keys](/help/api-keys). - **An invoice or a card** — the [Stripe portal](/help/invoices) does it immediately. ## What to include A good report is one we can reproduce. Send: - **The full request URL**, with your API key redacted. - **The response** — status code and body. On a `500`, the `message` field is the server's own exception text and usually identifies the problem outright. - **What you expected**, versus what you got. - **A job or company id**, if it's about specific data. This is the single most useful thing in a data report — see [reporting incorrect data](/help/data-corrections). - **When it started**, if it used to work. Support will never ask for it, and there is nothing we could do with it that we can't already do from your account. If you've pasted a key into a ticket, a screenshot, or a repo, [revoke it](/help/api-keys) and create a new one. For billing, send the **date and amount** of the charge — never your card number. We can't use it and don't want it; Stripe holds the card, not us. ## What to expect We read every message, and a real person answers it. There is **no contractual response-time guarantee on any plan**, including Scale — we're not going to invent an SLA on a help page. In practice, a reproducible report with an id in it gets answered faster than anything else, because it's the only kind we can act on without a round-trip. Security reports jump the queue. If you've found a vulnerability, write to and give us reasonable time to fix it before disclosing — see [§7 of the terms](/legal/terms). If you need guaranteed response times as a contractual matter, that's a conversation with . ## Things we can't do Stated plainly, so you don't spend a day waiting to find out: - **Recover a lost API key.** We store a hash. Nobody can read it back. Revoke and replace. - **Un-revoke a key.** Revocation is permanent. - **Edit an employer's job posting.** We mirror their board; corrections to the posting itself have to come from them. See [reporting incorrect data](/help/data-corrections). - **Give you a bulk export through the API.** No endpoint returns the whole dataset. For flat files, ask . - **Set up webhooks.** There aren't any. Sync is pull-based via [the feed](/docs/guides/feed-sync). - **Delete an invoice.** Tax law requires we keep it. See [deleting your account](/help/delete-account). ## Status For API availability, [`/v1/health`](/docs/api-reference/health) is unauthenticated and free to poll — it doesn't touch your quota. Your own usage and key activity are on the [dashboard](/dashboard). ## Next The technical FAQ, with the zero-results checklist. Everything else.