How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Booqable Settings API

Locations, tax rates, coupons, employees, and notes.

Booqable Settings API is one of 11 APIs that Booqable publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Settings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 8 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 4.

Requests are made against a single base URL, https://{company}.booqable.com/api/4.

8 operations 4 paths 3 schemas 4 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4
Base URL
https://{company}.booqable.com/api/4
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

Booqable Settings API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — An access token created in Booqable account settings, sent as "Authorization: Bearer ". Booqable also supports request signing (single-use signed tokens using…

Paths & Operations 8

Across 4 paths, the API surfaces 8 operations — 4 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Settings 8

Locations, tax rates, coupons, employees, and notes.

GET
/locations
List locations
listLocations → 200
POST
/locations
Create a location
createLocation body → 201
GET
/tax_rates
List tax rates
listTaxRates → 200
POST
/tax_rates
Create a tax rate
createTaxRate body → 201
GET
/coupons
List coupons
listCoupons → 200
POST
/coupons
Create a coupon
createCoupon body → 201
GET
/notes
List notes
listNotes → 200
POST
/notes
Create a note
createNote body → 201

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are ResourceCollection (4 properties), Resource (4 properties), ResourceDocument (3 properties). Each schema is shown below with its type and property counts.

ResourceDocument
object
A JSON:API document containing a single primary resource.
3 properties
Resource
object
A JSON:API resource object.
4 properties
ResourceCollection
object
A JSON:API document containing a collection of resources.
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

booqable-settings-api-openapi.yml Raw ↑

Other APIs Booqable publishes across the network.

Booqable Availability API
Booqable Bundles & Collections API
Booqable Customers API
Booqable Documents API
Booqable Order Fulfillment API
Booqable Orders API
Booqable Product Groups API
Booqable Products API
Booqable Stock Items API
Booqable Webhooks API
Where this information came from

This is an independent, third-party profile of Booqable Settings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.