Support

Routes

Need	Where
A question, a bug, anything not urgent	support@stylumia.com — response within 2 business days
A security vulnerability	security@stylumia.com — see Security at Stylumia
An incident or outage	the status page

What to include

• The request_id from the response you're asking about — it's in meta.request_id on a success, request_id on an error, and the X-Request-Id header on both.
• The name of the key that made the call, from the console — never the key itself.
• Roughly when the call happened, in a timezone you name.

That's usually enough for us to find your exact request server-side without back-and-forth.

Asking for more

The published rate limits and the retailers and categories in coverage are what a key reaches today. If you need more than that — higher limits, retailers we don't list, or delivery somewhere other than this API — email support@stylumia.com and say what you're building. There is no form and no approval queue; it is a conversation.

If the docs made you ask

If you needed to email support because a doc page didn't answer the question, that's a bug in the docs — tell us that too, separately from whatever you actually asked about. The standard we hold these docs to is that you shouldn't need to email us at all; every time you do, we want to know why the page in front of you didn't already cover it.