Skip to content
Bottle

Change the name on the account

PATCH
/storefront/sites/{host}/account
curl --request PATCH \
  --url https://example.com/storefront/sites/northgate.shop.getbottle.app/account \
  --header 'Content-Type: application/json' \
  --data '{ "name": "example", "marketingConsent": true }'

Deliberately without a staff session: a shopper on the business’s own shop. The account’s own name only.

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
host
required
string
Example
northgate.shop.getbottle.app

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
name
string
>= 1 characters <= 120 characters
marketingConsent
boolean
Examplegenerated
{
  "name": "example",
  "marketingConsent": true
}

Responses

Section titled “Responses”

200

Section titled “200”

The account

Media typeapplication/json
object
name
required
string
email
required
string
emailVerified
required
boolean
twoFactor
required
boolean
hasPin
required
boolean
marketingConsent
boolean
customers
required
Array<object>
object
id
required

UUID v7

string format: uuid
name
required
string
kind
required
string
Allowed values: domestic commercial
paymentTerms
required
string | null
canPayOnAccount
required
boolean
trade
required
boolean
role
required
string
Allowed values: manager buyer accounts
canOrder
required
boolean
addresses
required
Array<object>
object
id
required

UUID v7

string format: uuid
customerId
required

UUID v7

string format: uuid
label
required
string
line1
required
string
line2
required
string | null
city
required
string | null
postcode
required
string | null
tradeApplication
required
object
status
required
string
Allowed values: none pending approved declined
reason
required
string | null
submittedAt
required
string | null format: date-time
Example
{
  "customers": [
    {
      "id": "019205d1-6e7a-7c3b-9f6e-3a2b1c0d9e8f",
      "kind": "domestic",
      "role": "manager"
    }
  ],
  "addresses": [
    {
      "id": "019205d1-6e7a-7c3b-9f6e-3a2b1c0d9e8f",
      "customerId": "019205d1-6e7a-7c3b-9f6e-3a2b1c0d9e8f"
    }
  ],
  "tradeApplication": {
    "status": "none"
  }
}

400

Section titled “400”

Refused: the message says why

Media typeapplication/json
object
error
required
string
message
required
string
Example
{
  "error": "not_found",
  "message": "Customer not found"
}

401

Section titled “401”

Not signed in

Media typeapplication/json
object
error
required
string
message
required
string
Example
{
  "error": "not_found",
  "message": "Customer not found"
}

403

Section titled “403”

Not from the shop itself, or the email is not confirmed yet

Media typeapplication/json
object
error
required
string
message
required
string
Example
{
  "error": "not_found",
  "message": "Customer not found"
}

404

Section titled “404”

Not a shop. No body.

409

Section titled “409”

A real shop not selling now (shop_closed)

Media typeapplication/json
object
error
required
string
message
required
string
Example
{
  "error": "not_found",
  "message": "Customer not found"
}

422

Section titled “422”

Validation failed

Media typeapplication/json
object
error
required
string
Allowed values: validation
message
required
string
issues
required
Array<object>
object
path
required
string
message
required
string
Example
{
  "error": "validation",
  "issues": [
    {
      "path": "email",
      "message": "Invalid email"
    }
  ]
}

429

Section titled “429”

Too many tries

Media typeapplication/json
object
error
required
string
message
required
string
Example
{
  "error": "not_found",
  "message": "Customer not found"
}