Hey there, I’ve run into a similar issue with Plivo’s SubAccount API before—here are some practical troubleshooting steps and fixes that might help you out:

1. Double-Check the Parameter Name in the SDK #

First, verify if the parameter key is correct for the Plivo Node.js SDK. Sometimes API docs and SDK implementations can have slight mismatches. For example, some versions of the SDK use is_enabled instead of enabled for this field. Try modifying your code to:

plivoclient.subAccounts.create("subaccount name", { is_enabled: true })

Check the official SDK docs (within your installed package or the latest version details) to confirm the exact parameter name.

2. Upgrade Your Plivo SDK to the Latest Version #

Older versions of the Plivo Node.js SDK might have bugs or lack support for the enabled parameter. Run this command to update to the latest stable version:

npm update plivo

After updating, re-test your code to see if the subaccount gets enabled correctly.

3. Verify Your Main Account Permissions #

Some Plivo account tiers or configurations might restrict automatic enabling of subaccounts. Try creating a subaccount directly through the Plivo web console:

• Log into your Plivo dashboard
• Navigate to SubAccounts > Create SubAccount
• Check if you can set the "Enabled" toggle to on during creation

If even the console won’t let you create an enabled subaccount, it’s likely a permission or account-level restriction—reach out to Plivo support to clarify your account’s capabilities.

4. Inspect the API Response #

Add logging to check the actual response returned by the API after creation. This will tell you if the parameter is being ignored or if there’s an underlying issue:

plivoclient.subAccounts.create("subaccount name", { enabled: true })
  .then(function(response) {
    console.log("SubAccount Response:", response);
  })
  .catch(function(error) {
    console.error("Error:", error);
  });

Look for the enabled (or is_enabled) field in the response object. If it’s still false, the API is not processing your parameter correctly.

5. Test with Direct REST API Calls #

To rule out SDK-specific bugs, try creating the subaccount using a raw HTTP request (e.g., with curl):

curl -X POST https://api.plivo.com/v1/Account/{YOUR_AUTH_ID}/SubAccount/ \
  -u '{YOUR_AUTH_ID}:{YOUR_AUTH_TOKEN}' \
  -d 'name=subaccount name' \
  -d 'enabled=true'

If this direct call creates an enabled subaccount, the problem is definitely with the Node.js SDK. You can either use direct HTTP requests as a workaround or report the bug to Plivo’s developer support.

6. Check Parameter Type #

Some APIs expect boolean values as strings instead of native booleans. Try passing "true" instead of true to see if that makes a difference:

plivoclient.subAccounts.create("subaccount name", { enabled: "true" })

If none of these steps work, reaching out to Plivo’s support with your API request logs and account details will help them debug the issue faster.

内容的提问来源于stack exchange，提问作者Hammy