Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.brandsapi.com/llms.txt

Use this file to discover all available pages before exploring further.

Security is at the heart of hello@devshineteam.com. We implement industry-standard security measures to protect our infrastructure and your API usage.

​
API Authentication

All requests to the Brand API must be authenticated using a Secret API Key.
  • Header Name: Authorization
  • Format: Bearer <YOUR_API_KEY>
curl --request GET \
  --url https://api.brandapi.com/v2/brands/github.com \
  --header 'Authorization: Bearer YOUR_API_KEY'
Never share your Secret API Key or commit it to version control. If your key is compromised, rotate it immediately in the Developer Portal.

​
Data Security

​
Encryption

  • At Rest: All data stored in our databases is encrypted using AES-256.
  • In Transit: All API traffic is served over HTTPS using TLS 1.2 or higher to ensure data is encrypted as it travels across the web.

​
Isolation

We ensure strict multi-tenant isolation. Your API usage data and configurations are logically separated from other customers.

​
Infrastructure Security

Our platform is hosted on AWS (Amazon Web Services), benefiting from their world-class security physical and network infrastructure.
  • DDoS Protection: We use AWS Shield and Cloudflare to protect against large-scale distributed denial-of-service attacks.
  • Vulnerability Scanning: We perform regular automated vulnerability scans of our infrastructure and application code.

​
Compliance

We are committed to maintaining a secure environment for your data. We are currently working towards SOC2 Type II compliance, with an expected completion in 2026.

​
Reporting Vulnerabilities

If you believe you have found a security vulnerability in hello@devshineteam.com, please report it to our security team at hello@devshineteam.com. We appreciate your help in keeping BrandApi secure for everyone.