Support

Stuck? Work down this list, then contact us.

1. Is the API up?

   GET /health needs no key and returns {"message": "API is running"} when the service is healthy.

2. Is it your key?

   GET /v1/perils with your key. A 401 means the key is missing, mistyped or expired; a 403 on another endpoint means the key is valid but not licensed for it.

3. Is it the payload?

   The daily and batch endpoints return detailed validation messages: malformed JSON, duplicate CSV indices, invalid peril names, non-ISO dates. Read the 422 body; it names the failing field.

4. Is it a modelling question?

   For questions about how a peril is modelled, what a threshold means or how to interpret a curve (rather than API mechanics), see the CERA® Hazard Guide: per-peril methodology, reliability & transparency, and a full glossary.

5. Contact us

   Email admin@birdseyeview.ai with the request you sent (minus your key), the full response body and a timestamp.