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

Zapier Inputs API

Refers to resources interacting with 'Inputs' associated resources

Zapier Inputs API is one of 13 APIs that Zapier publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Inputs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.

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

Requests are made against a single base URL, https://api.zapier.com.

2 operations 2 paths 20 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2024.11.0
Base URL
https://api.zapier.com
Authentication
API Key, OAuth 2.0
Contact
Resource Areas
1

Authentication & Security 2

Zapier Inputs API declares 2 security schemes for authenticating requests. An API key is passed in the query as client_id (ClientIDAuthentication). It supports OAuth 2.0 (OAuth) using the authorizationCode and implicit flows, exposing 8 scopes.

  • ClientIDAuthentication — See our authentication documentation for how to find your Client ID
  • OAuth — See our OAuth2 authentication documentation here: https://docs.zapier.com/powered-by-zapier/api-reference/authentication

Paths & Operations 2

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

Inputs 2

Refers to resources interacting with 'Inputs' associated resources

POST
/v2/actions/{action_id}/inputs
Zapier Get Input Fields
get-fields-inputs 1 param body → 200403401409429503504400
POST
/v2/actions/{action_id}/inputs/{input_id}/choices
Zapier Get Choices
get-choices 3 params body → 200403401409429503504400

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are InputField (12 properties), Error (6 properties), Fieldset (4 properties), Choice (4 properties). Each schema is shown below with its type and property counts.

BaseMeta
object
The meta object returned in paginated response bodies.
3 properties 2 required
Links
object
The links object returned in paginated response bodies.
2 properties
ListInputFieldsRequest
object
Common inputs with inputs and an authentication id.
1 property 1 required
Meta
object
Metadata about a certain response
1 property 1 required
ErrorResponse
object
1 property 1 required
RootFieldset
array
The base concept of a Fieldset, from which others extend
Error
object
Base Error definition
6 properties
FieldsetFieldsField
Somewhat confusingly named, a field that is a list of either input fields or info fields.
Choice
object
A single element from a set of Choices, variants in an enumeration.
4 properties 3 required
ChoiceParams
object
A Choice as to be provided to the /choices endpoint
2 properties 2 required
ChoiceRequest
object
1 property 1 required
ErrorSource
object
Populates the source object inside our error responses.
3 properties
InfoField
object
Represents an Info-type Fieldset
3 properties 3 required
Fieldset
object
Represents a Fieldset
4 properties 4 required
FormatEnum
string
DATETIME - DATETIME MULTILINE - MULTILINE PASSWORD - PASSWORD CODE - CODE READONLY - READONLY FILE - FILE SELECT - SELECT
InputFieldsResponse
object
A successful response for getting the input fields for a particular Action.
3 properties 3 required
InputField
object
Represents Input Field data as accepted by the API
12 properties 12 required
ChoiceResponse
object
A successful response for getting the requested Input Fields.
3 properties 2 required
_ListInputFieldsRequest
object
The common data object that includes inputs and an authentication id.
2 properties 2 required
ValueTypeEnum
string
STRING - STRING NUMBER - NUMBER INTEGER - INTEGER BOOLEAN - BOOLEAN ARRAY - ARRAY OBJECT - OBJECT

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zapier-inputs-api-openapi.yml Raw ↑

Other APIs Zapier publishes across the network.

Zapier AI Actions API
Zapier MCP
Zapier Accounts API
Zapier Actions API
Zapier Apps API
Zapier Authentications API
Zapier Categories API
Zapier Experimental API
Zapier Outputs API
Zapier Zap Templates API
Zapier Zaps API
Where this information came from

This is an independent, third-party profile of Zapier Inputs 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.