Frequently Asked Questions
Everything you need to know about our API
We combine public regulatory and reference sources (for example FDA, EU CosIng, Health Canada where applicable), peer-reviewed literature, and established cosmetic-ingredient references, then normalize fields for use in software. The API is built for developers integrating ingredient data into apps—not for clinical diagnosis. Methodology evolves as sources update; see our docs for the current response schema.
Scores and labels in API responses come from a documented, weighted model (irritation, comedogenicity, and related signals). They are informational fields for your product logic—not a medical or dermatological assessment, and not a guarantee about how any individual will react to a product. Always validate critical use cases in your own UX and legal review.
Yes. The API is intended for commercial products: mobile apps, e-commerce, internal tools, and SaaS. Plans, rate limits, and pricing are described on our pricing page (subscriptions plus usage-style options). Enterprise customers can discuss custom terms, SLAs, and integrations on our contact page.
We target high availability for production use and document SLA-style expectations with paid tiers where applicable. Infrastructure is monitored around the clock; status and incidents are communicated through our status page when available. Exact numbers depend on your plan—ask sales for Enterprise guarantees.
Yes. You can start with a limited free allocation for development and testing (see the pricing page for current call limits and rate limits). Paid tiers add higher limits and support. Details change over time—always check /pricing for the live numbers.
Our API is optimized for speed with typical response times under 300ms for ingredient lookups and under 500ms for complete product analysis. We use global CDN distribution and intelligent caching to ensure low latency regardless of your location.
Any language that can send HTTPS requests with a Bearer token works. We also publish official alpha SDKs: JavaScript/TypeScript on npm (https://www.npmjs.com/package/dermalytics) and Python on PyPI (https://pypi.org/project/dermalytics/). For interactive API tests, use the hosted Swagger UI at https://api.dermalytics.dev/docs. The REST contract is defined in OpenAPI 3 at https://api.dermalytics.dev/openapi.json. Guides and examples are on our /docs page.
We refresh data on a rolling basis as new regulatory listings and reference updates appear. Breaking or safety-critical public notices are prioritized. API consumers receive updated fields through the same endpoints without schema surprises—check release notes or contact us for Enterprise change notifications.
Still have questions? We're here to help.
Contact Support