Skip to main content
Settings hold the configuration of an Exsited instance: currencies, taxes, time zones, warehouses, item groups, variations, discount, shipping and payment setup, custom objects, field settings and the general settings groups. You can read every area and create, change or delete most of its records. This area has 86 endpoints, and all seven SDKs call every one.
Updating the general group of general settings sets eight other instance settings, such as accountingPeriod and fiscalYear, to null, and no API call can set them back.

At a glance

Before you call

Register your API credentials once when your app starts, as shown in Authentication. Every SDK sample on these pages then gets its client in one line. With cURL, send the access token in an Authorization header: Authorization: Bearer $ACCESS_TOKEN.

Things to know

  • Each record sits under its own key. A currency is under currency, a warehouse under warehouse and general settings under general_settings, and writes use the same key.
  • General settings are read and written one group at a time. group is one of account, item, date_and_time, order, purchase, labour, transaction, security, dashboard, portal, display or general; the item and order groups also carry product. The dashboard and security groups store flags as "1" and "0".
  • Currencies and taxes cannot be deleted. There is no delete call for either, so a currency or tax you create stays on the instance.
  • Some writes return a different shape from the read. A payment term create returns a flat period and duration, and a payment processor write returns gateway_name and credentials where a read has provider.
  • Listings page by cursor. Records sit under data; pass pagination.next_cursor as cursor to read the next page, and stop when pagination.has_more is false.
  • Custom objects have two paths. /custom_objects and /settings/custom_objects serve the same records; the settings listing shows enabled ones only.