Skip to content

Contact support

View as Markdown

Aerandil is in early access with design partners, and the people who answer are the people who built it.

Write to hello@aerandil.com. For a question about a request that did not do what you expected, send:

  • the route and the action, for example POST /v1/actions/hospitality.action.check_in/apply;
  • the instance_id from the error envelope, or the request-id response header, which is the same value;
  • the correlation_id from an apply that succeeded but produced the wrong effect;
  • what you sent, with secrets removed, and what you expected.

With an instance_id we can find the exact request in the cell’s log. Without one we can usually still find it from the time and the principal, but it takes longer.

A vulnerability goes to security@aerandil.com, not to the general address. Send what you found and how to reproduce it; we will acknowledge it and tell you what happens next.

What changed and when is on the changelog. A deprecation is announced there before it takes effect, with the date and what to use instead.

A private demo runs live over a video call on a hotel seeded to look like yours. Book one on aerandil.com.