Pinduoduo PHP SDK

To use the SDK, initialize the PinDuoDuo class with a configuration array. The configuration requires client_id, client_secret, and a member_type defining the user role.

Available member_type values:

• MERCHANT: Merchant authorization
• H5: Mobile end
• JINBAO: Duoduo Jinbao promoter (多多进宝推手)
• KTT: Kuaituantuan leader (快团团团长)
• LOGISTICS: Pinduoduo electronic shipping label user (拼多多电子面单用户)

use \Justmd5\PinDuoDuo\PinDuoDuo;

require __DIR__ . '/vendor/autoload.php';

$config = [
    'client_id'    => 'xxxxxx69e3940c6b93xxxxxx',
    'client_secret' => 'c2eda0c398xxxxxxbd63ff57bf22c05xxxxxx',
    'debug'              => true,
    'member_type'        => 'JINBAO', // e.g., MERCHANT, H5, JINBAO, KTT, LOGISTICS
    'redirect_uri'       => 'https://test.xxx.com/callback',
    'log'                => [
        'name'       => 'pinduoduo',
        'file'       => __DIR__ . '/pinduoduo.log',
        'level'      => 'debug',
        'permission' => 0777,
    ],
];

$pinduoduo = new PinDuoDuo($config);

To access protected endpoints, follow these steps to authorize the user and obtain an access token:

1. Get Authorization URL: Generate the URL to redirect the user to.
2. Redirect User: Redirect the user to the generated URL.
3. Retrieve Token: After redirection, retrieve the access token.
4. Refresh Token (Optional): Use the refresh_token to obtain a new access token.
5. Create Authorized Client: Use the token to create a client instance specifically for authorized API calls.

// 1. Get the authorization URL
$url = $pinduoduo->pre_auth->authorizationUrl();

// 2. Redirect to the authorization page
$pinduoduo->pre_auth->authorizationRedirect();

// 3. Retrieve the token from the redirect callback
$token = $pinduoduo->pre_auth->getAccessToken();

// 4. Refresh the token if needed
// $token = $pinduoduo->pre_auth->refreshToken($token['refresh_token']);

// 5. Create an authorized client instance
$pinduoduo = $pinduoduo->oauth->createAuthorization($token['token']);

To start the OAuth process, use the PreAuth class. You can either generate the authorization URL to build your own redirect logic or use authorizationRedirect to perform an immediate HTTP header redirect to the Pinduoduo authorization page.

Supported member_type values (configured in the main PinDuoDuo instance) determine which authorization endpoint is used:

• MERCHANT: Pinduoduo Shop (Web)
• H5: Pinduoduo Shop (H5 Mobile)
• JINBAO: Jinbao Promoter (Web)
• KTT: KTT Captain (Web)
• LOGISTICS: Pinduoduo Electronic Waybill User (Web)

use Justmd5\PinDuoDuo\PinDuoDuo;
use Justmd5\PinDuoDuo\Oauth\PreAuth;

// Assuming $app is an initialized PinDuoDuo instance
$preAuth = new PreAuth($app);

// Option 1: Get the URL to use in your own redirect logic
$url = $preAuth->authorizationUrl('your_custom_state', 'optional_view');

// Option 2: Perform an immediate redirect
$preAuth->authorizationRedirect('your_custom_state');

The request method is the primary way to interact with the Pinduoduo platform. It handles parameter signing, authentication tokens, and supports both standard JSON responses and file uploads.

Parameters:

• string $type: The API interface name.
• array $params: Request parameters (excluding common parameters which are handled automatically).
• string $data_type: The response format, either 'JSON' or 'XML' (defaults to 'JSON').
• string $version: The API version (defaults to 'V1').

Key Behaviors:

• Authentication: If the Api instance was initialized with $needToken = true or if you call auth(true) before the request, the access_token and client_id are automatically injected into the parameters.
• File Uploads: If the $params array contains a 'file' key, the SDK automatically switches the target URL to UPLOAD_URL and uses the upload HTTP method.
• Data Handling: Boolean values in $params are converted to 'true'/'false' strings, and arrays are automatically json_encoded to ensure compatibility with the Pinduoduo API.

// Example of a standard JSON request
$response = $api->request('api_name', ['param1' => 'value1'], 'JSON');

// Example of a file upload request
$response = $api->request('upload_api_name', ['file' => '/path/to/file.jpg']);

The SDK provides a ServiceProvider implementation for the Pimple dependency injection container. When registered, it sets up the core services required to interact with the Pinduoduo API.

Key services registered to the container:

• access_token: An AccessToken instance used for managing authentication. It requires client_id and client_secret to be configured in the container.
• api: The standard Api instance for making authorized requests.
• auth_api: An Api instance specifically configured for authentication-related requests (initialized with true for auth mode).

use Justmd5\PinDuoDuo\ServiceProvider;
use Pimple\Container;

$container = new Container();
// Ensure client_id and client_secret are configured in your container/config before registering
$container['client_id'] = 'YOUR_CLIENT_ID';
$container['client_secret'] = 'YOUR_CLIENT_SECRET';

$container->register(new ServiceProvider());

// Accessing services
$api = $container['api'];
$accessToken = $container['access_token'];