Support

A human reads
every email.

One channel, no ticket maze: petreldata.io@gmail.com. We aim to reply within 48 hours — usually much faster. Picking the matching subject below routes you to the right answer sooner.

Can’t access your data

Scores returning errors, downloads failing, a key that stopped working, or a product you paid for that you can’t reach. Run the 60-second checks below first — they resolve most cases instantly.

Email us — “Petrel support — data access”

API bug or unexpected result

An endpoint erroring, a score that looks wrong for a location you know, or behavior that contradicts the documentation. Include the details listed below and we can usually reproduce it same-day.

Email us — “Petrel support — API bug”

Billing & account

Plan changes, invoices, usage questions, cancellations, or anything Stripe-related. Include the email address on the account.

Email us — “Petrel support — billing”

Commercial licensing

Licensing terms for the free layers beyond non-commercial use, bulk data agreements, or redistribution questions.

Email us — “Petrel licensing”

Can’t reach the data? The 60-second checks.

Three checks separate “the platform is down” from “my key or quota” — run them top to bottom and you’ll know which email to send (or that none is needed).

1 · Is the platform up? (no key needed)

curl "https://api.petreldata.io/v1/demo/score?lon=-80.19&lat=25.76"

Scores back = the platform is healthy, and the issue is specific to your key or quota — keep going. An error here = it’s on our side; email “API bug” with the timestamp.

2 · Is your key valid?

curl -H "X-API-Key: tlk.YOUR_KEY" "https://api.petreldata.io/v1/catalog"

200 = key is fine. 401 = the key is wrong, revoked, or truncated — check it in your account (keys are shown once at creation; generate a new one if in doubt).

3 · Are you over quota?

A quota_exceeded response means the month’s included calls are used up (free tier: 1,000/mo; the live demo allows 25 scores/day per IP). Check usage in your account, or upgrade for more.

Reporting a bug? Include these.

  • The full request URL (endpoint + parameters).
  • Timestamp (with timezone) of the failing call.
  • The complete response body and HTTP status.
  • The first 12 characters of your API key only (e.g. tlk.1a2b3c4d) — never send the full key.