> ## Documentation Index
> Fetch the complete documentation index at: https://www.vobiz.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Why do I get a 'From number not owned by account' error?

> The Vobiz Make Call API rejects a call when the from number is not owned by your account. Learn the two causes - a caller ID that belongs to someone else, or a number bought less than two minutes ago - and how to fix each.

The **From number not owned by account** error occurs when you try to make a call using a number that is not owned by your account. Every outbound call needs a `from` that your account owns, and Vobiz checks that before it places the call.

## Why it happens

There are two common causes:

| Cause | How to tell |
| - | - |
| **The number was bought less than two minutes ago.** A newly purchased number takes about **2 minutes** to register before it can be used as a caller ID. | The number shows in [My Numbers](/docs/platform/numbers/my-numbers) and the purchase succeeded, but calls placed right after buying it fail. |
| **The number belongs to a different account.** The `from` is not on your account at all - a typo, a number on another Vobiz account, or a number that sits in a [sub-account](/docs/account-phone-number/assign-subaccount) when you are calling from the parent, or the other way round. | The number is not in your [List Account Phone Numbers](/docs/account-phone-number/list-account-phone-numbers) response for the `auth_id` you are calling with. |

## How to fix it

**1. Wait a couple of minutes after purchasing**

If you just bought the number, wait about two minutes and retry. Registration finishes on its own - there is nothing to configure. Build the same pause into any script that buys a number and then calls from it straight away.

**2. Confirm the number is on this account**

List the numbers for the exact `auth_id` you are sending in `X-Auth-ID`:

```bash theme={null}
curl "https://api.vobiz.ai/api/v1/Account/MA_XXXXXXXX/numbers" \
  -H "X-Auth-ID: MA_XXXXXXXX" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"
```

The `from` must appear in that list in the same E.164 form you are sending. A number assigned to a sub-account must be called from with that sub-account's credentials.

**3. Use an owned number as the caller ID**

Pick one of the numbers from the list, or [buy a new number](/docs/buy-a-phone-number) and wait two minutes before using it. Trial accounts use the trial number assigned to them.

> [!NOTE]
>
> The same check applies inside call flows. A `<Dial>` without a `callerId` on an inbound call derives the caller ID from the caller's own number, which your account does not own, and the bridge fails with the same message. Always set `callerId` to one of your numbers - see [Dial to a SIP user](/docs/xml/dial/user#caller-id-and-caller-name).

## Related

* [Buy a Phone Number](/docs/buy-a-phone-number) - purchase in the console or over the API, then route the number.
* [Make a Call](/docs/call/make-call) - the `from` and `to` fields and the other errors the endpoint returns.
* [Phone Numbers API](/docs/account-phone-number) - list, assign and release the numbers on your account.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.