API Key Security
- Keep API keys confidential and never expose them in public repos or client-side code.
- Use separate keys per environment and rotate credentials regularly.
SAHMK Legal
Developer Usage Terms
Practical API usage rules to help teams integrate SAHMK endpoints safely and responsibly.
Rate Limits and Fair Use
- Stay within your plan limits and expected traffic profile.
- Usage limits may be enforced at different levels, including API key, account and IP address, depending on the applicable service and plan. Refer to the technical documentation for the current limits.
- Handle throttling responses (such as 429) using backoff and retry logic.
- When abuse signals or quota-circumvention patterns are detected, we may apply temporary restrictions, including active key revocation and disabling new key issuance pending review.
Prohibited Behavior
- No abuse, automated attacks, or disruption attempts.
- No sharing, selling, or transferring API keys to third parties.
- No attempts to bypass throttling, authentication, or security controls.
- No creating or using multiple accounts to circumvent plan limits, usage quotas, or access controls.
Responsible Endpoint Automation
- Use automation in ways that do not create unnecessary infrastructure load.
- Monitor unusual usage patterns and stop harmful traffic promptly.
Enforcement and Appeal
- If we confirm a violation of these terms, we may apply proportionate enforcement actions, including temporary restriction, suspension, and key revocation while review is ongoing.
- To request reinstatement, contact support with an incident explanation, root-cause analysis, corrective actions already implemented, and a prevention plan with a designated technical point of contact.