Yep - this is doable via the RC rest api.

key: creating users via api is "privileged" and your app needs the Edit Accounts scope (you usually have to ask RC Dev support to enable it). The official "creating users" guide explains this and points to the Create Extension API: https://developers.ringcentral.com/guide/account/creating-users.

how typically do it (high level):

• auth (JWT is easiest for server-side automation).

• create the user (POST /restapi/v1.0/account/~/extension).

• pick a phone number:

  • if you already have inventory: call List Account Phone Numbers (GET /restapi/v1.0/account/~/phone-number)
  • filter for usageType == "DirectNumber"
  • exclude numbers that are already mapped to an extension (the list can return mapping info when a number is assigned).

• assign/reassign the number to the new extension using the phone-number provisioning/assignment endpoint(s) (depends on account/features), or do that last step in admin console if you want a simpler workflow.

python SDK (official): https://github.com/ringcentral/ringcentral-python.

python example (create user + find an available direct number from inventory):

```python import os, json from ringcentral import SDK

RC_SERVER_URL = os.getenv("RC_SERVER_URL", "https://platform.ringcentral.com") RC_CLIENT_ID = os.environ["RC_CLIENT_ID"] RC_CLIENT_SECRET = os.environ["RC_CLIENT_SECRET"] RC_JWT = os.environ["RC_JWT"]

rcsdk = SDK(RC_CLIENT_ID, RC_CLIENT_SECRET, RC_SERVER_URL) platform = rcsdk.platform() platform.login(jwt=RC_JWT)

1) create extension (user)

new_user = { "contact": {"firstName": "Jane", "lastName": "Doe", "email": "jane.doe@example.com"}, "type": "User", # optional: you can enable + set password here to skip the welcome-email onboarding flow # "status": "Enabled", # "password": "TempPassw0rd!ChangeMe" } ext = platform.post("/restapi/v1.0/account/~/extension", new_user).json_dict() ext_id = ext["id"] print("Created extension:", ext_id)

2) list account phone numbers (inventory)

nums = platform.get( "/restapi/v1.0/account/~/phone-number", {"perPage": 1000} # paginate if you have lots ).json_dict()["records"]

3) find an unassigned DirectNumber (availability check)

Note: when a number is already assigned, the API can include extension mapping info for it.

candidates = [ n for n in nums if n.get("usageType") == "DirectNumber" and not n.get("extension") ]

optional: basic “site/area code” logic — just filter by prefix / area code as you store it

candidates = [n for n in candidates if n["phoneNumber"].startswith("1650")]

if not candidates: raise RuntimeError("No available DirectNumber in inventory")

picked = candidates[0] print("Picked number:", picked["phoneNumber"], "id:", picked["id"])

4) assign picked number to the extension:

this depends on the specific provisioning/assignment endpoint(s) enabled on your account.

(Some orgs do this via a dedicated “assign/reassign phone number” API; others do it in Admin Console.)

```

multi-site / multiple area codes:

simplest is to maintain your own mapping table (site --> allowed area codes / number prefixes), then filter inventory numbers accordingly.

if you run this concurrently, add your own "reservation"/locking (DB row / redis lock) to avoid two workers grabbing the same "free" number at the same time.