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

Quenza Clients API

The Clients API from Quenza — 4 operation(s) for clients.

Quenza Clients API is one of 16 APIs that Quenza publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://developers.quenza.com/v1.

6 operations 4 paths 5 schemas 2 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://developers.quenza.com/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

  • http — Authenticate using a Bearer token in the Authorization header: Authorization: Bearer {your-token} You can generate or regenerate your API token in your Quenza…

Paths & Operations 6

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

Clients 6
GET
/clients
List clients
developers.v1.clients.list 2 params → 200401
POST
/clients
Create a client
developers.v1.clients.create body → 201401422
GET
/clients/{client}
Get a client
developers.v1.clients.show 1 param → 200404401
PATCH
/clients/{client}
Update a client
developers.v1.clients.update 1 param body → 200404401422
POST
/clients/{client}/archive
Archive a client
developers.v1.clients.archive 1 param → 200404401
POST
/clients/{client}/unarchive
Unarchive a client
developers.v1.clients.unarchive 1 param → 200404401

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ClientResource (16 properties), CreateClientRequest (9 properties), UpdateClientRequest (8 properties). Each schema is shown below with its type and property counts.

ClientResource
object
16 properties 16 required
ClientStatus
string
Gender
string
UpdateClientRequest
object
8 properties
CreateClientRequest
object
9 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

quenza-clients-api-openapi.yml Raw ↑

Other APIs Quenza publishes across the network.

Quenza ArchiveClient API
Quenza AttachGroupMembers API
Quenza CreateClient API
Quenza CreateGroup API
Quenza CreateMember API
Quenza Groups API
Quenza ListClient API
Quenza ListMember API
Quenza ListTask API
Quenza Members API
Quenza ShowClient API
Quenza Tasks API