Wrike Custom Fields API
Custom field definitions and management
Wrike Custom Fields API is one of 17 APIs that Wrike publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Custom Fields. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, a getting-started guide, and a changelog.
This API exposes 2 operations across 1 path, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 4.0.
Requests are made against a single base URL, https://www.wrike.com/api/v4.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Wrike Custom Fields API declares
2 security schemes
for authenticating requests.
It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 6 scopes.
It accepts HTTP bearer tokens (bearerToken).
By default, every request must be authenticated.
oauth2— OAuth 2.0 authorization code flowbearerToken— Permanent access token (legacy authentication)
Paths & Operations 2
Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Custom field definitions and management
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are CustomField (7 properties), Error (2 properties), CustomFieldListResponse (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Wrike 12
Other APIs Wrike publishes across the network.