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

Smokeball Layout Designs API

The Layout Designs API from Smokeball — 2 operation(s) for layout designs.

Smokeball Layout Designs API is one of 34 APIs that Smokeball publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Layout Designs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, rate-limit docs, a GitHub repository, and 1 JSON Schema.

This API exposes 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 6 base URLs: https://api.smokeball.com, https://api.smokeball.com.au, https://api.smokeball.co.uk, https://stagingapi.smokeball.com, https://stagingapi.smokeball.com.au, https://stagingapi.smokeball.co.uk.

2 operations 2 paths 6 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.smokeball.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Smokeball Layout Designs API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (api-key). An API key is passed in the header as Authorization (token). By default, every request must be authenticated.

Paths & Operations 2

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

Layout Designs 2
GET
/layouts
Get layout designs
GetLayoutDesigns 2 params → 200
GET
/layouts/{id}
Get a layout design
GetLayoutDesignById 3 params → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are LayoutDesignInfoPagedCollection (13 properties), LayoutDesign (10 properties), LayoutDesignInfo (8 properties), ProblemDetails (5 properties). Each schema is shown below with its type and property counts.

LayoutDesign
object
10 properties
LayoutDesignInfoPagedCollection
object
13 properties
LayoutDesignInfo
object
8 properties
Link
object
4 properties
ProblemDetails
object
5 properties
LayoutDesignField
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

smokeball-layout-designs-api-openapi.yml Raw ↑

Other APIs Smokeball publishes across the network.

Smokeball Activity Codes API
Smokeball Authorization API
Smokeball Bank Accounts API
Smokeball Contacts API
Smokeball Events API
Smokeball Expenses API
Smokeball Fees API
Smokeball Files API
Smokeball Firm API
Smokeball Folders API
Smokeball Intake API
Smokeball Integrated Search API
Where this information came from

This is an independent, third-party profile of Smokeball Layout Designs 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.