How to Extend As Customer a Business Account via Rest API

I am fairly familiar with REST APIs and the 422 Unprocessable Entity error typically indicates that the request format or data is incorrect.
this error might be due to one of the following:

•  Check the Endpoint URL – Ensure the endpoint and version (24.200.001) are correct.

• Missing Required Fields: Some fields might be required but not obvious.

• Validate the Business Account ID (000053) – Confirm it exists and is accessible.
  with GET /entity/Default/24.200.001/BusinessAccount/000053

• Check the Request Body/Params – For GET, ensure you're not sending an unnecessary or malformed body.
   

Hope it helps!

Hi ​@jpeterson ,

To convert a Business Account to a Customer, only the BusinessAccountID field is required. Please find below a sample JSON request for the conversion.

Url:entity/Default/24.200.001/BusinessAccount/ConvertBusinessAccountToCustomer

Method:POST

Request:
{

    "entity": {

        "BusinessAccountID": {

            "value": "ALPINEAIR"

        }

    },

    "parameters": {}

}

I have cleaned up the POST so the request looks like the below but I still get the 422

Same URL: https://((Customer)).acumatica.com/entity/Default/24.200.001/BusinessAccount/ConvertBusinessAccountToCustomer

{

"entity": {

"BusinessAccountID": { "value": "000053" }

}

}

Have also confirmed that I can access the account by doing the simple Get

https://((Customer)).acumatica.com/entity/Default/24.200.001/BusinessAccount/000053

Any other ideas? 

​@jpeterson Hello, after hours of trying I’m able to Create Customer via ConvertBusinessAccountToCustomer action.

I have attached my testing example to show it works :

I used this Request :
 

{
  "entity": {

    "BusinessAccountID": {
      "value": "TEST1"
    },


     "MainContact": {

        "Email": {

            "value": "test@gmail.com"

        }

    }
  }
}

and you just need BusinessAccountID & Email. (Both are Mandatory)
Note : You can add field such as Type, CustomerClass, CustomerName, SalesAccount, etc.

URL’s  you can use one of them (both works):
1.  /entity/Default/24.200.001/BusinessAccount/ConvertBusinessAccountToCustomer/
2.  /entity/Default/24.200.001/BusinessAccount/ExtendToCustomer/
 

You Got 204 - No Content as a Response & it actually means: The request was successfully processed, but there's no data returned in the response body.

I hope it helps! Thanks for sharing this. I learned something new from it.

Argh I am glad you got it to work but unfortunately i still get the 422. See below: 

Body: 

{

"entity": {

"Type":{

"Value":"BAccount"

},

"BusinessAccountID": {

"value": "000054"

},

"MainContact": {

"Email": {

"value": "billing@example.com"

}

}

}

}

I tried it with both url’s you suggested.

​@jpeterson from above I suggest you check BusinessAccountID value in Database (my case DAC - BAccount - > AcctCD → Test1).

Select AcctCD from BAccount 

if query give you result & AccCD value is diff. then replace it OR
Inspect your Business Account ID field & check value in Database.

I have confirmed that AccountId does match. You are doing a POST correct?

​@jpeterson Yes, its a POST request. I suggest you that try BusinessAccountID as “54” in request instead of “000054”. rest is as it is.
so your req become : 

{

"entity": {"Type":{"Value":"BAccount"},

"BusinessAccountID": {"value": "54"},

"MainContact": {"Email": {"value": "billing@example.com"}}}

}

Give it try.

Might be getting somewhere. Now I get the error saying the Extend as Customer button is disabled? I have confirmed I can use it in the UI. 

It is an action under the business account endpoint: 

Though there are no parameters? Not sure if that matters. 

​@jpeterson okay you are on right track & I also face this issue. This error came when you try to send req with Unknown fields name like instead of BusinessAccountID you trying BusinessAccount or other naming issue regarding fields.
you can try this req also & if possible send database snap of BAccount & Customer Table.

{"entity": {
    "Type":{"Value":"BAccount"},
    "BusinessAccountID": {"value": "--"},
    "CustomerName": {"value": "---"},
    "CustomerClass": {"value": "LOCAL"},
     "MainContact": { "Email": { "value": "test@mail.com" }}}}

Hmm same error with your request but atleast we are getting somewhere. 

Here is the Business Account Schema: 

Customer Schema

If I go through this manually in the UI when I click the “extend as customer” button it jumps me to the customer’s page and before I save the record I have to update the customer class. When I do that it gives me this warning below. Not sure if it matters.

​@jpeterson I think its not required & if you not provide it take default Customer class. & if had doubt then provide this value in req.
I’m pretty sure that your providing wrong value in req. Just double check your values that are matches with database records like in AcctCD value in table BAccount, EMail format in Contact table, etc.
All fields values you providing in  request double check it.
and provide Whole log of 422 error if possible.

I found something interesting. A business account I extended to a customer manually through the UI. if I do a Get customer in the response it shows me the BAccountID and the customerID. But I am not sure where that BAccountID of 6587 is coming from? 000056 is what shows as the Business Account in the UI. Where would I find that 6587 number?

You can find 6587 in the BAccount table as the BAccountID


Try this:

• SELECT 
      b.BAccountID, 
      b.AcctCD AS BusinessAccountCD, 
      c.BAccountID AS CustomerCD, 
      c.bAccountID AS CustomerBAccountID
  FROM 
      BAccount b
  JOIN 
      Customer c ON b.BAccountID = c.bAccountID
  WHERE 
      b.AcctCD = '000056';

   

Would it make sense that it needs to be the internal numeric id in the request vs the visible one?