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

The Picklr WordPress REST API

The public read surface of thepicklr.com, served by WordPress core and the site's plugins. Anonymous GET returns the franchise's own published content — 157 club location records, 53 pages, 23 blog posts, 5 press items and 4 events — with page-number pagination, X-WP-Total headers and sparse-fieldset support. Writes require a WordPress Application Password and are not offered to third parties. No OpenAPI is published by the provider; the description in openapi/ is a mechanical transform of the route index the site serves at /wp-json/, restricted to routes whose anonymous access was individually verified.

This API exposes 21 operations across 21 paths, organized into 12 resource areas, and defines 1 schema. It is described by OpenAPI 3.1.0, at version wp/v2.

Requests are made against a single base URL, https://thepicklr.com/wp-json.

21 operations 21 paths 1 schemas 21 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
wp/v2
Base URL
https://thepicklr.com/wp-json
Authentication
HTTP Basic, OAuth 2.0
Contact
Terms of Service
Resource Areas
12

Authentication & Security 2

The Picklr WordPress REST API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (applicationPassword). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope.

  • applicationPassword — WordPress Application Passwords. Authorization endpoint advertised by the live API root: https://thepicklr.com/wp-admin/authorize-application.php. Required for…
  • oauth2 — OAuth 2.1 authorization code + PKCE (S256) with RFC 7591 dynamic client registration, advertised at https://thepicklr.com/.well-known/oauth-authorization-serve…

Paths & Operations 21

Across 21 paths, the API surfaces 21 operations — 21 GET. They span 12 resource areas, including posts, pages, media, location, press, event, club_clinics, categories, and 4 more. Each is listed below with its method, path, parameters, and response codes.

posts 2
GET
/wp/v2/posts
List posts
get_wp_v2_posts 27 params → 200400401404
GET
/wp/v2/posts/{id}
Retrieve posts
get_wp_v2_posts_id 4 params → 200400401404
pages 2
GET
/wp/v2/pages
List pages
get_wp_v2_pages 22 params → 200400401404
GET
/wp/v2/pages/{id}
Retrieve pages
get_wp_v2_pages_id 4 params → 200400401404
media 2
GET
/wp/v2/media
List media
get_wp_v2_media 23 params → 200400401404
GET
/wp/v2/media/{id}
Retrieve media
get_wp_v2_media_id 2 params → 200400401404
location 2
GET
/wp/v2/location
List location
get_wp_v2_location 27 params → 200400401404
GET
/wp/v2/location/{id}
Retrieve location
get_wp_v2_location_id 3 params → 200400401404
press 2
GET
/wp/v2/press
List press
get_wp_v2_press 23 params → 200400401404
GET
/wp/v2/press/{id}
Retrieve press
get_wp_v2_press_id 3 params → 200400401404
event 2
GET
/wp/v2/event
List event
get_wp_v2_event 23 params → 200400401404
GET
/wp/v2/event/{id}
Retrieve event
get_wp_v2_event_id 4 params → 200400401404
club_clinics 2
GET
/wp/v2/club_clinics
List club clinics
get_wp_v2_club_clinics 23 params → 200400401404
GET
/wp/v2/club_clinics/{id}
Retrieve club clinics
get_wp_v2_club_clinics_id 3 params → 200400401404
categories 2
GET
/wp/v2/categories
List categories
get_wp_v2_categories 12 params → 200400401404
GET
/wp/v2/categories/{id}
Retrieve categories
get_wp_v2_categories_id 2 params → 200400401404
tags 2
GET
/wp/v2/tags
List tags
get_wp_v2_tags 12 params → 200400401404
GET
/wp/v2/tags/{id}
Retrieve tags
get_wp_v2_tags_id 2 params → 200400401404
types 1
GET
/wp/v2/types
List types
get_wp_v2_types 1 param → 200400401404
taxonomies 1
GET
/wp/v2/taxonomies
List taxonomies
get_wp_v2_taxonomies 2 params → 200400401404
search 1
GET
/wp/v2/search
List search
get_wp_v2_search 8 params → 200400401404

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is WPError (3 properties). Each schema is shown below with its type and property counts.

WPError
object
WordPress REST API error envelope, observed verbatim on live 401/404 responses.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

the-picklr-wordpress-rest-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of The Picklr WordPress REST 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.