The Ding PHP library provides convenient access to the Ding API from applications written in the PHP language.
composer require "ding/sdk"
Send an OTP code to a user's phone number.
declare(strict_types=1);
require 'vendor/autoload.php';
use Ding\DingSDK;
use Ding\DingSDK\Models\Shared;
$security = 'YOUR_API_KEY';
$sdk = DingSDK\Ding::builder()->setSecurity($security)->build();
$request = new Shared\CreateAuthenticationRequest(
customerUuid: 'cf2edc1c-7fc6-48fb-86da-b7508c6b7b71',
phoneNumber: '+1234567890',
locale: 'fr-FR',
);
$response = $sdk->otp->createAuthentication(
request: $request
);
if ($response->createAuthenticationResponse !== null) {
// handle response
}
Check that a code entered by a user is valid.
declare(strict_types=1);
require 'vendor/autoload.php';
use Ding\DingSDK;
use Ding\DingSDK\Models\Shared;
$security = 'YOUR_API_KEY';
$sdk = DingSDK\Ding::builder()->setSecurity($security)->build();
$request = new Shared\CreateCheckRequest(
authenticationUuid: 'eebe792b-2fcc-44a0-87f1-650e79259e02',
checkCode: '123456',
customerUuid: '64f66a7c-4b2c-4131-a8ff-d5b954cca05f',
);
$response = $sdk->otp->check(
request: $request
);
if ($response->createCheckResponse !== null) {
// handle response
}
Perform a retry if a user has not received the code.
declare(strict_types=1);
require 'vendor/autoload.php';
use Ding\DingSDK;
use Ding\DingSDK\Models\Shared;
$security = 'YOUR_API_KEY';
$sdk = DingSDK\Ding::builder()->setSecurity($security)->build();
$request = new Shared\RetryAuthenticationRequest(
authenticationUuid: 'a4e4548a-1f7b-451a-81cb-a68ed5aff3b0',
customerUuid: '28532118-1b33-420a-b57b-648c9bf85fee',
);
$response = $sdk->otp->retry(
request: $request
);
if ($response->retryAuthenticationResponse !== null) {
// handle response
}
Send feedback about the authentication process.
declare(strict_types=1);
require 'vendor/autoload.php';
use Ding\DingSDK;
use Ding\DingSDK\Models\Shared;
$security = 'YOUR_API_KEY';
$sdk = DingSDK\Ding::builder()->setSecurity($security)->build();
$request = new Shared\FeedbackRequest(
customerUuid: 'cc0f6c04-40de-448f-8301-3cb0e6565dff',
phoneNumber: '+1234567890',
status: Shared\FeedbackRequestStatus::Onboarded,
);
$response = $sdk->otp->feedback(
request: $request
);
if ($response->feedbackResponse !== null) {
// handle response
}
Get the status of an authentication.
declare(strict_types=1);
require 'vendor/autoload.php';
use Ding\DingSDK;
$security = 'YOUR_API_KEY';
$sdk = DingSDK\Ding::builder()->setSecurity($security)->build();
$response = $sdk->otp->getAuthenticationStatus(
authUuid: 'd8446450-f2fa-4dd9-806b-df5b8c661f23'
);
if ($response->authenticationStatusResponse !== null) {
// handle response
}
Perform a phone number lookup.
declare(strict_types=1);
require 'vendor/autoload.php';
use Ding\DingSDK;
$security = 'YOUR_API_KEY';
$sdk = DingSDK\Ding::builder()->setSecurity($security)->build();
$response = $sdk->lookup->lookup(
customerUuid: '69a197d9-356c-45d1-a807-41874e16b555',
phoneNumber: '<value>'
);
if ($response->lookupResponse !== null) {
// handle response
}
Available methods
- lookup - Look up for phone number
- check - Check a code
- createAuthentication - Send a code
- feedback - Send feedback
- getAuthenticationStatus - Get authentication status
- retry - Perform a retry
Ding: The OTP API allows you to send authentication codes to your users using their phone numbers.
- SDK Installation
- SDK Example Usage
- Available Resources and Operations
- Error Handling
- Server Selection
The SDK relies on Composer to manage its dependencies.
To install the SDK and add it as a dependency to an existing composer.json
file:
composer require "ding-live/ding-php"
Handling errors in this SDK should largely match your expectations. All operations return a response object or throw an exception.
By default an API error will raise a Errors\SDKException
exception, which has the following properties:
Property | Type | Description |
---|---|---|
$message |
string | The error message |
$statusCode |
int | The HTTP status code |
$rawResponse |
?\Psr\Http\Message\ResponseInterface | The raw HTTP response |
$body |
string | The response content |
When custom error responses are specified for an operation, the SDK may also throw their associated exception. You can refer to respective Errors tables in SDK docs for more details on possible exception types for each operation. For example, the check
method throws the following exceptions:
Error Type | Status Code | Content Type |
---|---|---|
Errors\SDKException | 4XX, 5XX | */* |
declare(strict_types=1);
require 'vendor/autoload.php';
use Ding\DingSDK;
use Ding\DingSDK\Models\Shared;
$security = 'YOUR_API_KEY';
$sdk = DingSDK\Ding::builder()->setSecurity($security)->build();
try {
$request = new Shared\CreateCheckRequest(
authenticationUuid: 'eebe792b-2fcc-44a0-87f1-650e79259e02',
checkCode: '123456',
customerUuid: '64f66a7c-4b2c-4131-a8ff-d5b954cca05f',
);
$response = $sdk->otp->check(
request: $request
);
if ($response->createCheckResponse !== null) {
// handle response
}
} catch (Errors\SDKException $e) {
// handle default exception
throw $e;
}
You can override the default server globally by passing a server index to the server_idx: int
optional parameter when initializing the SDK client instance. The selected server will then be used as the default on the operations that use it. This table lists the indexes associated with the available servers:
# | Server | Variables |
---|---|---|
0 | https://api.ding.live/v1 |
None |
The default server can also be overridden globally by passing a URL to the server_url: str
optional parameter when initializing the SDK client instance. For example:
This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.
While we value open-source contributions to this SDK, this library is generated programmatically. Feel free to open a PR or a Github issue as a proof of concept and we'll do our best to include it in a future release!