API Access

1. Overview

DICE API access allows approved customers, developers, and integration partners to connect software applications to DICE services. This may include querying product information, retrieving regulatory screening results, integrating workflow data, or enabling product identification and certification-related automation within a customer environment.

The API is designed for legitimate business integration and must be used in accordance with this page, the DICE Terms of Service, and applicable law. DICE reserves the right to approve or deny API use based on business, security, technical, or compliance considerations.

2. Eligibility and Approval

API access is available only to organizations or individuals approved by Sanyog. Approval may depend on business purpose, technical design, security posture, legal compliance, and contractual status.

• You must use the API only for the purpose and scope approved by Sanyog.
• You must maintain valid account ownership and control over all API credentials issued to you.
• You must not transfer or resell credentials to unauthorized third parties.
• You must promptly notify us if your access is used by a third party or if there is suspected misuse.

3. Authentication

API access will generally require secure authentication using credentials such as API keys, tokens, OAuth flows, or other industry-standard credentials provided by Sanyog. These credentials must be stored securely and never embedded in client-side code or public repositories unless expressly approved.

• Rotate credentials periodically and immediately after a suspected compromise.
• Restrict access to least-privilege scopes.
• Use HTTPS/TLS for all API traffic.
• Do not share secrets across teams, applications, or external vendors without authorization.

Example request

curl -X POST "https://api.dicebysanyog.com/v1/product/identify" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "product_name": "Plastic Water Bottle",
    "market": "INDIA",
    "label_text": "HDPE, BPA Free, 1L",
    "country_of_origin": "India"
  }'

Example response

{
  "status": "success",
  "request_id": "req_8d1f6bcb",
  "product": {
    "category": "Packaging",
    "likely_material": "HDPE",
    "risk_flags": ["label_conflict"],
    "markets": ["INDIA", "UAE"],
    "confidence": 0.92
  },
  "message": "Product classification and compliance screening completed."
}

4. Usage Limits and Rate Limits

DICE may impose usage limits, quotas, throttling, and rate limits based on service plan, customer tier, resource availability, or business requirements. These limits may apply to request volume, data volume, throughput, or concurrency.

We may alter limits to maintain service stability, security, or fair use. Where feasible, we will provide notice of material rate-limit changes; however, urgent security or reliability issues may require immediate action.

Standard support and service expectations

DICE will use commercially reasonable efforts to maintain a reliable API service for approved customers. Service availability, support response windows, and escalation terms may vary by plan, customer tier, and commercial agreement. In general:

5. Data and Privacy

API use may involve customer data, product information, uploaded files, labels, declarations, ingredient details, compliance records, or related operational content. You agree to use the API in a manner consistent with the DICE Privacy Policy and all applicable privacy and data protection laws.

• Only request or transmit the minimum data necessary for the approved integration.
• Do not misuse customer data or export data beyond the approved scope.
• Ensure your systems protect data in transit and at rest using strong security controls.
• Do not repurpose or resell personal or business data obtained through the API without authorization.

6. Acceptable Use

The DICE API must be used for lawful and approved business purposes only. You may not use the API to:

• harass, impersonate, spam, or mislead users;
• interfere with, disrupt, overload, or attack DICE systems;
• attempt to bypass rate limits, authentication, or access controls;
• access or export data beyond the approved integration scope;
• misrepresent product identity, compliance status, or certification outcome;
• use the API in a way that violates law, regulation, or third-party rights.

7. Security Requirements

Developers and partners integrating with DICE must maintain security controls appropriate to the sensitivity of the data processed and the risk profile of the integration. At a minimum, you must protect API credentials, use TLS, validate inputs, and implement reasonable logging and monitoring.

• Store secrets in a secure secret manager or environment vault.
• Validate all user input and output handling to prevent injection or unsafe processing.
• Monitor your systems for unauthorized use, anomalies, or suspicious activity.
• Use secure error handling and avoid exposing stack traces or confidential information in client responses.

8. Monitoring and Enforcement

We may monitor usage patterns, application behavior, and API health to maintain service integrity, enforce policy, prevent abuse, and improve reliability. We may investigate suspicious activity and may request remediation or evidence of secure implementation.

If we determine that your API use violates these terms or creates risk, we may throttle, restrict, suspend, or revoke access temporarily or permanently, without prior notice where necessary for security or legal compliance.

Operational reliability

DICE may update endpoints, response schemas, or authentication flows from time to time. We will use commercially reasonable efforts to provide notice of material breaking changes in advance where feasible, and to maintain a backward-compatible transition period for supported versions.

9. Termination and Suspension

DICE may suspend or terminate API access at any time, with or without notice, if we believe the access is misused, unauthorized, insecure, non-compliant, or otherwise harmful to the platform or other users.

Upon suspension or termination, your right to use DICE API credentials ends immediately. You must disable any live integrations and remove or revoke access to all valid credentials associated with the terminated account.

10. Contact

For API access requests, developer support, or integration questions, contact us: