Domain automation for reseller.co.tz partners

Quick Start

Use this sample from your backend server. Never call the reseller API directly from public JavaScript or a mobile app bundle.

curl -X POST "https://reseller.co.tz/api/v1/domains/check" \
  -H "X-API-KEY: your_reseller_api_key" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{"domain_name": "example.co.tz"}'

Authentication

Every request must include the reseller API key shown inside the reseller portal API Access page.

Response Format

{
  "success": true,
  "message": "Domain synced successfully.",
  "data": {
    "domain": {
      "id": 123,
      "domain_name": "example.co.tz",
      "status": "active"
    }
  }
}

{
  "success": false,
  "message": "The request could not be validated.",
  "errors": {
    "domain_name": [
      "The domain name field is required."
    ]
  }
}

Billing Safety

Registration, renewal, and transfer are billable when a price is configured. Free actions include sync, fetch nameservers, fetch Whois, fetch EPP, lock status, and privacy status.

• Balance is checked before the provider call.
• The reseller row is locked before funds are deducted.
• Funds are deducted only after the provider returns success.
• The domain update and ledger transaction are saved inside one database transaction.
• A reconciliation audit event is written after successful registration or renewal billing.
• If the provider succeeds but local billing fails, a failed billing audit event is written for admin review.

Endpoints

DNS Management

DNS endpoints are scoped to domains owned by the authenticated reseller. DNS management must be active before records can be listed, created, updated, or deleted. Responses use generic DNS messages and do not expose internal infrastructure details.

Payload Examples

{
  "domain_name": "example.co.tz",
  "period": 1,
  "nameservers": ["ns1.yatosha.com", "ns2.yatosha.com"],
  "registrant": {
    "name": "Domain Owner",
    "organization": "Owner Company",
    "address1": "123 Registry Road",
    "city": "Dar es Salaam",
    "state": "Dar es Salaam",
    "postcode": "11101",
    "country": "TZ",
    "phone": "+255.754123456",
    "email": "owner@example.co.tz"
  },
  "admin": {
    "name": "Domain Admin",
    "organization": "Owner Company",
    "address1": "123 Registry Road",
    "city": "Dar es Salaam",
    "state": "Dar es Salaam",
    "postcode": "11101",
    "country": "TZ",
    "phone": "+255.754123456",
    "email": "admin@example.co.tz"
  }
}

{
  "period": 1
}

{
  "nameservers": ["ns1.yatosha.com", "ns2.yatosha.com"]
}

{
  "registrant": {
    "name": "Domain Owner",
    "organization": "Owner Company",
    "address1": "123 Registry Road",
    "city": "Dar es Salaam",
    "state": "Dar es Salaam",
    "postcode": "11101",
    "country": "TZ",
    "phone": "+255.754123456",
    "email": "owner@example.co.tz"
  },
  "admin": {
    "name": "Domain Admin",
    "organization": "Owner Company",
    "address1": "123 Registry Road",
    "city": "Dar es Salaam",
    "state": "Dar es Salaam",
    "postcode": "11101",
    "country": "TZ",
    "phone": "+255.754123456",
    "email": "admin@example.co.tz"
  }
}

{
  "locked": true
}

{
  "enabled": true
}

{
  "confirm": true
}

{
  "type": "A",
  "name": "www",
  "value": "203.0.113.10",
  "ttl": 14400
}

{
  "type": "MX",
  "name": "@",
  "value": "mail.example.co.tz.",
  "priority": 10,
  "ttl": 14400
}

{
  "type": "TXT",
  "name": "@",
  "value": "v=spf1 include:example.net ~all",
  "ttl": 3600
}

{
  "note": "No request body is required. Replace {record} with the record line or ID returned by the DNS list endpoint."
}

Supported Actions

curl -X POST "https://reseller.co.tz/api/index.php" \
  -H "X-API-KEY: your_reseller_api_key" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "checkDomain",
    "domainName": "example.co.tz"
  }'

curl -X POST "https://reseller.co.tz/api/index.php" \
  -H "X-API-KEY: your_reseller_api_key" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "renewDomain",
    "domainName": "example.co.tz",
    "period": 1
  }'

{
  "action": "registerDomain",
  "domainName": "example.co.tz",
  "period": 1,
  "nameservers": ["ns1.yatosha.com", "ns2.yatosha.com"],
  "registrantInfo": {
    "name": "Domain Owner",
    "organization": "Owner Company",
    "address": "123 Registry Road",
    "city": "Dar es Salaam",
    "state": "Dar es Salaam",
    "postalCode": "11101",
    "country": "TZ",
    "phone": "+255.754123456",
    "email": "owner@example.co.tz"
  },
  "adminInfo": {
    "name": "Domain Admin",
    "organization": "Owner Company",
    "address": "123 Registry Road",
    "city": "Dar es Salaam",
    "state": "Dar es Salaam",
    "postalCode": "11101",
    "country": "TZ",
    "phone": "+255.754123456",
    "email": "admin@example.co.tz"
  }
}

Status Codes

Logging And Reconciliation

Every request is captured in the API Logs page, including invalid keys and failed validation. Sensitive fields such as API keys, EPP codes, auth codes, passwords, tokens, and secrets are removed before logs are saved.