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

Lendis case-study API

Customer case studies

Lendis case-study API is one of 10 APIs that Lendis publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include case-study. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version wp/v2.

Requests are made against a single base URL, https://www.lendis.io/wp-json.

2 operations 2 paths 2 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
wp/v2
Base URL
https://www.lendis.io/wp-json
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

Lendis case-study API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (applicationPassword). An API key is passed in the header as X-WP-Nonce (nonce).

  • applicationPassword — WordPress Application Passwords (username plus application password) sent as HTTP Basic over TLS. Required for write operations and privileged routes; anonymou…
  • nonce — Cookie-authenticated first-party browser requests send a WordPress nonce in the X-WP-Nonce header, advertised in Access-Control-Allow-Headers on live responses.

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.

case-study 2

Customer case studies

GET
/wp/v2/case-study
List Customer case studies
listCaseStudy 8 params → 200400
GET
/wp/v2/case-study/{id}
Get one of the Customer case studies
getCaseStudyItem 3 params → 200404

Schemas 2

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

Error
object
The WordPress REST API error envelope. This is NOT RFC 9457 problem+json: it is served as application/json with a WordPress-specific shape.
3 properties
CaseStudy
object
A customer case study (case-study).
17 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lendis-case-study-api-openapi.yml Raw ↑

Other APIs Lendis publishes across the network.

Lendis discovery API
Lendis kataloge API
Lendis media API
Lendis pages API
Lendis posts API
Lendis ratgeber API
Lendis taxonomies API
Lendis testimonial API
Lendis wiki API
Where this information came from

This is an independent, third-party profile of Lendis case-study 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.