Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Napkin.AI Visuals API

Programmatic visual content generation.

Napkin.AI Visuals API is published by Napkin.AI on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Visuals. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and a changelog.

This API exposes 3 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.0.3, at version 1.1.16.

Requests are made against a single base URL, https://api.napkin.ai/v1.

3 operations 3 paths 5 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.1.16
Base URL
https://api.napkin.ai/v1
Authentication
HTTP Bearer, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

Napkin.AI Visuals API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 2 scopes. By default, every request must be authenticated.

  • bearerAuth — Bearer token authentication required for all endpoints. Use a Napkin AI account API token in the Authorization header.
  • oauth2 — OAuth 2.0 authorization code flow (beta). Your application must be approved by the Napkin AI team to obtain client credentials.

Paths & Operations 3

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

Visuals 3

Programmatic visual content generation.

POST
/visual
Create visual request
createVisualRequest body → 201400401429500
GET
/visual/{request-id}/status
Get visual request status
getVisualRequestStatus 1 param → 200400401403404410500
GET
/visual/{request-id}/file/{file-id}
Download generated file
downloadVisualFile 2 params → 200400401403404410500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are VisualRequest (5 properties), GeneratedFile (3 properties), VisualRequestStatus (3 properties), VisualRequestCreated (2 properties). Each schema is shown below with its type and property counts.

VisualError
object
Present on failed requests; when present, generatedfiles is empty.
2 properties
VisualRequestStatus
object
3 properties
VisualRequestCreated
object
2 properties
VisualRequest
object
Visual generation request. Fields below are the subset documented in the developer-preview docs and changelog; the live API may accept more.
5 properties 1 required
GeneratedFile
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

napkinai-visuals-api-openapi.yml Raw ↑