[#719] Can't book using new SimplyBook account 'Client phone value is wrong'

API General
,
1

Migrated from Redmine #719 | Author: Brendan Jefferis
Status: Closed | Priority: High, I’m very impatient | Created: 2021-06-16

We use multiple SimplyBook accounts for our business, with no issue.

We have a new instance, still on Free plan that we cannot book with via the API – fails with error

-32063 Client phone value is wrong

We are not providing a phone value for these requests with any account but only one account fails with this error.

Request for existing working account:

POST / HTTP/1.1
Host: user-api.simplybook.me
X-Company-Login: vicinitytest
X-Token: 1a9077fcad3af5ea1f2449331584bdef7ee88557320492ff552b8cb4349d403e
Content-Type: application/json
Content-Length: 225

{
  "jsonrpc": "2.0",
  "method": "book",
  "params": [
    "56",
    36,
    "2021-06-17",
    "10:00:00",
    {
      "name": "Guest",
      "email": "a@b.co"
    },
    { "terms": true, "handle_invoice": true },
    1
  ],
  "id": 1
}

Request for non-working account

POST / HTTP/1.1
Host: user-api.simplybook.me
X-Company-Login: trainingsite
X-Token: 5ec9361c85e4b3241ab29350d98b70d8f8a53e8c78db76e7a0b8efdd2b5b7f9d
Content-Type: application/json
Content-Length: 233

{
  "jsonrpc": "2.0",
  "method": "book",
  "params": [
    "9",
    6,
    "2021-07-01",
    "11:00:00",
    {
      "name": "Guest",
      "email": "a@b.co"
    },
    { "terms": true, "handle_invoice": true },
    1
  ],
  "id": 1
}

Notice that the only things that differ are the credentials and service ids.

Is there a reason that the phone field is required for some accounts and not others?

2

Brendan Jefferis wrote:

Solved: In the accounts that were failing I had missed the following configuration setting:

Settings > Email and SMS > Settings for Email and SMS Notifications > Mandatory registration fields

That was set to “Email and Phone”

You can close this issue now.