Update Store

Update Store

curl --request PUT \
  --url https://api-staging.luladelivery.store/stores/{store_id}

const options = {method: 'PUT'};

fetch('https://api-staging.luladelivery.store/stores/{store_id}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api-staging.luladelivery.store/stores/{store_id}",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "PUT",
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api-staging.luladelivery.store/stores/{store_id}"

	req, _ := http.NewRequest("PUT", url, nil)

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

require 'uri'
require 'net/http'

url = URI("https://api-staging.luladelivery.store/stores/{store_id}")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Put.new(url)

response = http.request(request)
puts response.read_body

{
  "success": true
}

PUT

stores

{store_id}

Update Store

curl --request PUT \
  --url https://api-staging.luladelivery.store/stores/{store_id}

const options = {method: 'PUT'};

fetch('https://api-staging.luladelivery.store/stores/{store_id}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api-staging.luladelivery.store/stores/{store_id}",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "PUT",
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api-staging.luladelivery.store/stores/{store_id}"

	req, _ := http.NewRequest("PUT", url, nil)

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

require 'uri'
require 'net/http'

url = URI("https://api-staging.luladelivery.store/stores/{store_id}")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Put.new(url)

response = http.request(request)
puts response.read_body

{
  "success": true
}

This endpoint allows you to update various aspects of a store’s configuration including name, contact details, point of contact, and addresses. Address updates support both modifying existing addresses and adding new ones.

Path Parameters

string

required

The unique identifier of the store to update

Query Parameters

string

required

The company ID that owns this store for authorization purposes

Request Body Fields

string

Updated store name. Example: “bulk ingest test #1”

string

Updated store contact email address. Example: “[email protected]”

string

Updated store contact phone number. Example: “+12679397993”

number

Updated point of contact user ID. Example: 1000418

array

Updated address information. Can include existing addresses (with IDs) and new addresses (without IDs)

Show Address Object

string

Existing address ID to update. Set to null for new addresses

string

required

Primary address line. Example: “102 W. Mission Ave.”

string

required

City name. Example: “Escondido”

string

required

State or province. Example: “CA”

string

required

ZIP or postal code. Example: “92025”

number

required

Type of address:

0 = Store Address (main operational address)
1 = Welcome Package Address (shipping address)

Request Example

{
    "name": "bulk ingest test #1",
    "email": "[email protected]",
    "phone_number": "+12679397993",
    "point_of_contact": 1000418,
    "addresses": [
        {
            "id": "b6197e9c-8e68-47fe-8dd7-e057d07197ea",
            "line_1": "102 W. Mission Ave.",
            "city": "Escondido",
            "state": "CA",
            "zip": "92025",
            "address_type": 0
        },
        {
            "id": null,
            "line_1": "102 W. Mission Ave.",
            "city": "Escondido",
            "state": "CA",
            "zip": "92025",
            "address_type": 1
        }
    ]
}

Response

boolean

Indicates whether the update operation was successful

Response Example

{
    "success": true
}

Address Update Behavior

Address Update Rules

behavior

When id is provided: Updates the existing address with new information

Only the provided fields will be updated

behavior

When id is null: Creates a new address record and associates it with the store

New addresses will be assigned unique IDs automatically

behavior

To remove an address: Don’t include it in the addresses array

Removing the primary store address may affect operations

Update Impact

What Gets Updated

updated

Basic store details like name, email, and phone number

updated

Point of contact can be reassigned to different users

updated

Existing addresses are modified, new addresses are created

preserved

Delivery service partner configurations remain unchanged

preserved

Store operational status and settings are maintained

Best Practices

Update Recommendations

best-practice

Only include fields you want to change

Omitted fields will retain their current values

best-practice

Always include existing address IDs when updating addresses

Forgetting to include an address ID may create duplicates

best-practice

Verify that the new point_of_contact user exists and has appropriate permissions

Invalid user IDs will result in update failure

best-practice

Perform updates during low-activity periods to minimize operational impact

Store updates don’t affect ongoing orders

Error Scenarios

Common Update Errors

error

The specified store_id doesn’t existStatus Code: 404

error

The store doesn’t belong to the specified company_idStatus Code: 403

error

The point_of_contact user ID doesn’t existStatus Code: 400

error

Address information is incomplete or invalidStatus Code: 400

Operational Continuity: Store updates are designed to maintain operational continuity. Existing orders, inventory, and partner integrations continue functioning normally during and after updates.

Audit Trail: All store updates are logged for compliance and troubleshooting purposes. Update timestamps and user information are automatically recorded.

API Documentation - Legacy

API Documentation - Latest

Path Parameters

Query Parameters

Request Example

Response

Response Example

Address Update Behavior

Update Impact

Best Practices

Error Scenarios

​Path Parameters

​Query Parameters

​Request Example

​Response

​Response Example

​Address Update Behavior

​Update Impact

​Best Practices

​Error Scenarios

Path Parameters

Query Parameters

Request Example

Response

Response Example

Address Update Behavior

Update Impact

Best Practices

Error Scenarios