Support & getting help

Stuck, found a bug, or have a question? Here's how to reach us and what to expect.

Email-first support

Support runs through one async front door: support@noms.sh. Email fits a developer audience and lets us give every request a considered answer. Anyone can email us, free Taster users included.

When you write in, include the endpoint and parameters you called, the response you got (status + doc_url), and what you expected. That gets you a useful answer on the first reply. Never send us a key. We can find your account from the address you write from.

Response times

Our commitment is time to first human response (not time to resolution). "Business day" means Monday–Friday, measured in UTC.

Tier	First response
Taster (free)	Best-effort
Sous Chef	Within 2 business days
Head Chef	Within 1 business day
Executive Chef	Per contract

The self-serve targets are best-effort goals, not contractual guarantees; only Executive Chef carries a negotiated commitment. These are launch values and may be revised at general availability.

Outages and security jump the queue

Severity beats tier: a suspected outage or security issue is handled as fast as possible for everyone, free tier included. Report security issues privately to support@noms.sh, never in a public channel.

Status & incidents

Check status.noms.sh for live API and website health and incident history. During a confirmed outage we post updates there, so it's the single source of truth rather than emailing in.

Before you write in

A quick self-check resolves most questions:

401? Re-read Authentication and check the header name, and that the key has not been revoked or rotated out from under you.
429? You're over quota. See Rate limits & quotas and back off until Retry-After.
Unexpected shape? Confirm your include= / fields[...] against the API explorer, which documents every field.
Every error carries a doc_url linking straight to the explanation of that problem type. Follow it first.

SDKs & integrations

There are no official SDKs yet. The API is plain REST over HTTPS with JSON, so any HTTP client works, and the copy-paste snippets throughout this guide cover cURL, JavaScript and Python. The API explorer can also generate request snippets in more languages.