- How do I install centralnic-reseller/php-sdk with Composer?
- Install the package with Composer using composer require centralnic-reseller/php-sdk. Make sure your PHP version and Composer dependencies match what the package requires. After installation, include Composer's autoloader and instantiate the SDK client in your application bootstrap or service provider.
- Can I use centralnic-reseller/php-sdk in a Laravel application?
- Yes, the SDK is a PHP package and can be used inside Laravel even though it is not described as Laravel-specific. A common approach is to bind the client as a singleton in a service provider and inject it into services or jobs. Keep configuration in config/services.php and environment variables rather than hardcoding credentials.
- How do I configure CentralNic Reseller API credentials in Laravel?
- Store the API username, password, and any endpoint or account settings in your .env file. Reference them from config/services.php and pass them into the SDK client from a service provider. Avoid committing credentials and consider separate configuration sets for staging and production.
- Which domain operations does this PHP SDK support?
- The package is described as covering domain registration, renewal, transfer, DNS, and related reseller operations. It provides a structured client for communicating with CentralNic Reseller services. Check the SDK methods for the exact commands and response objects your workflow needs.
- Does centralnic-reseller/php-sdk support Internet.bs and Moniker APIs too?
- The overview says it is an API connector for Team Internet backend APIs covering CentralNic Reseller, Internet.bs, and Moniker. That suggests the SDK may target multiple brands through the same backend family. Verify the available client classes and endpoints before assuming every operation is exposed for each brand.
- Is there a sandbox or test environment for the CentralNic Reseller API?
- The provided package context does not document a sandbox environment. Check CentralNic Reseller or Team Internet provider documentation for test credentials or an OTE-style environment. In your Laravel tests, mock the SDK client behind an interface so domain operations do not hit the live API.
- How should I handle API errors and exceptions with this SDK?
- Wrap SDK calls in try/catch blocks and log the request context without exposing credentials. Inspect the SDK source or documentation for the exception types and error response structure it exposes. For reseller operations, also record the domain name and command so failed registrations or transfers can be retried safely.
- Does this package support Laravel 10 and Laravel 11?
- The package is not presented as a Laravel package, so Laravel version support mainly depends on its PHP version requirements. Check the package composer.json for PHP constraints and confirm they are compatible with your Laravel 10 or Laravel 11 runtime. Because it is framework-agnostic, it should work in both if the PHP versions align.
- Can I manage DNS records and nameservers through the SDK?
- The package overview explicitly mentions DNS and related reseller operations. That indicates you can likely manage DNS-related tasks, but confirm the exact methods for records, nameservers, and zone updates in the SDK. Test DNS changes in a controlled environment before applying them to production domains.
- What are alternatives to centralnic-reseller/php-sdk for domain reseller automation?
- Alternatives include calling the CentralNic Reseller or Team Internet APIs directly with Guzzle or Laravel's HTTP client, using another registrar SDK, or building a small internal wrapper around the endpoints you need. The best choice depends on how much of the reseller workflow you want managed for you. If you only need a few commands, a thin HTTP client may be simpler to maintain.