✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for WPGetAPI

SleekView Kanban reads the WPGetAPI configuration of APIs and endpoints and renders one card per endpoint, grouped into columns by health state. Dragging a card pauses, resumes, or retires an endpoint by writing back to the WPGetAPI options store with one AJAX call.

♾️ Lifetime License available

SleekView Kanban board for WPGetAPI

Why WPGetAPI integrations need a board

WPGetAPI stores every API and every endpoint inside the wpgetapi_apis option, with each endpoint carrying its method, path, headers, body template, and an active flag. The plugin admin renders APIs as tabs and endpoints as forms inside each tab, with no overview that crosses API boundaries to show which endpoints are healthy, paused, failing, or retired.

SleekView Kanban reads the WPGetAPI option directly. The grouping axis is the endpoint health state, derived from the active flag plus the most recent response status the plugin captured on its last call. Cards land in Active, Paused, Failing, or Disabled columns based on that signal. Each card shows the endpoint ID, parent API name, HTTP method, target path, and last response code, with optional badges for authentication scheme.

Dragging a card between Active and Paused updates the endpoint's active flag and fires the wpgetapi_endpoint_state_changed action so logging integrations record the change. Moving a Failing endpoint back to Active resets its failure counter, so the next call attempts a real request instead of skipping due to a backoff window. Disabling an endpoint prevents calls entirely without losing the configuration.

Workflow

From WPGetAPI config to live board in four steps

1

Connect to the WPGetAPI registry

Pick the WPGetAPI APIs option as the data source. The plugin reads every API and its child endpoints through the WPGetAPI helper functions so target URLs, authentication, and headers appear on the board without duplicating any config.
2

Pick the status column to group by

Endpoint health is the natural axis. The board derives Active, Paused, Failing, and Disabled columns from the active flag plus the most recent response code. Failing covers any endpoint that returned a 4xx or 5xx in the last 24 hours.
3

Choose what shows on each card

Drag up to six fields onto the card layout. Endpoint ID, parent API, HTTP method, path, last response code, and last call timestamp all render natively. Authentication scheme and per endpoint tag chips are available as optional card components.
4

Enable drag and drop writes

Turn writes on and dragging a card updates the active flag through the WPGetAPI option API and fires the wpgetapi_endpoint_state_changed action. Logging plugins capture the change, and the dispatcher honors the new state on the next call request.

Sample board

Sample WPGetAPI integration board

The WPGetAPI APIs and endpoints registry grouped by health state, rendered as four columns of cards pulled from a live multi service integration setup.
Active
38
stripe / list_customers
GET, last 200, 2 min ago
hubspot / create_contact
POST, last 201, 7 min ago
shopify / list_orders
GET, last 200, 4 min ago
Paused
7
github / list_repos
Paused by Asha, 2026-05-29
slack / list_channels
Paused by Tomas, 2026-05-21
intercom / list_admins
Paused by Asha, 2026-05-18
Failing
3
zendesk / list_tickets
GET, last 502, 22 min ago
notion / query_database
POST, last 401, 4 hours ago
airtable / list_records
GET, last 429, 11 hours ago
Disabled
14
old_crm / sync_contacts
Retired 2026-04-19
legacy_billing / export
Retired 2026-03-28
sandbox / debug_echo
Retired 2026-03-12

Comparison

Default WPGetAPI admin versus SleekView Kanban

Default WPGetAPI endpoint forms

  • Endpoints live inside per API tabs with no cross-API overview
  • Operators must open each form to check last response and last call time
  • Pausing an endpoint requires drilling into a settings form per record
  • No grouping by health, so a Failing endpoint can sit hidden for days
  • Bulk re-activating a batch of endpoints is not supported in the admin

SleekView Kanban

  • Reads the WPGetAPI wpgetapi_apis option through helper functions
  • Derives Active, Paused, Failing, and Disabled columns from real signals
  • Drag fires wpgetapi_endpoint_state_changed for log capture
  • Resetting a Failing endpoint clears its retry counter automatically
  • Filter cards by parent API, HTTP method, or last response code class

Features

What SleekView Kanban gives you for WPGetAPI

Cross-API health view

WPGetAPI organizes endpoints under their parent API tab, which makes single API maintenance simple but hides fleet wide signals. The board ignores the tab structure and shows every endpoint in one view, grouped by health, so operators see issues across services in a single glance.

Real WPGetAPI writes

Card moves update the active flag through the WPGetAPI option API and fire the official endpoint state changed action. Logging plugins capture the change like a manual edit, and any subsequent call to wpgetapi_endpoint() honors the new state on the next request.

Filters that match operations

Filter cards by parent API, HTTP method, last response code class, and authentication scheme. Filtering on 5xx response codes scopes the board to endpoints that need attention right now. Filtering by API scopes the view to one service during incident triage.

Audience

Three integration teams that need a board

Integration operations

Teams running dozens of API integrations across services use the Failing column as their triage queue. Cards landing there get dragged to Paused while engineers investigate upstream, then back to Active once the upstream is healthy, all without per endpoint settings drilling.

Upstream incidents

When a vendor publishes an incident on their status page, the on call engineer filters the board by that API and drags every affected endpoint to Paused. Failures stop polluting logs immediately, and re-activation is a single sweep once the vendor reports green.

Legacy endpoint retirement

Old endpoints from retired services accumulate inside the WPGetAPI registry over years. The board surfaces them in the Failing or Disabled columns, and dragging them to Disabled stops further calls while keeping the configuration available for an eventual audit.

The bigger picture

Why WPGetAPI deserves a fleet view

WPGetAPI is one of the best WordPress plugins for treating arbitrary REST APIs as first class data sources. The form based configuration UI works well when you have one or two APIs, because each endpoint gets a clean settings tab with every option exposed. The form based UI stops scaling once the install holds twenty endpoints across half a dozen services, because no operator can keep a fleet wide picture in their head when each endpoint lives in its own tab.

A kanban board solves that without changing the configuration model. Endpoints stay in WPGetAPI, the writes stay in WPGetAPI, and the board reads the same option the rest of the plugin uses. Operations teams gain a cross-API view that helps them spot failures fast, take batch actions during incidents, and retire legacy endpoints intentionally instead of forgetting they exist.

Questions

Common questions about SleekView Kanban for WPGetAPI

Both. The integration reads the wpgetapi_apis option that both versions write to and writes back through the same option API. Pro features around authentication, scheduling, and templating render on cards as additional metadata but are not required for the board to function.

 

An endpoint lands in Failing when its most recent response code captured by WPGetAPI is a 4xx or 5xx within the configured window, which defaults to 24 hours. Older failures roll out of the column automatically as the window slides forward over time.

 

WPGetAPI tracks consecutive failures internally for backoff calculations. Moving a card from Failing back to Active resets that counter, so the next call to wpgetapi_endpoint attempts a real request immediately instead of waiting for the backoff window to expire.

 

Yes. Each drag fires the wpgetapi_endpoint_state_changed action with the API ID, endpoint ID, old state, new state, and acting user. Any logging or audit plugin that listens for that action records the move with the same metadata as a manual configuration edit.

 

Yes. The filter bar exposes parent API, HTTP method, last response code class, and authentication scheme. Filters apply on the server through array filters on the option, so even installs with hundreds of endpoints render the board without noticeable lag.

 

Yes. The plugin enforces the same capability check WPGetAPI applies on its own admin pages. Users with the configured management capability see drag handles and can move cards. Other users see the same layout in read only mode with drag handles hidden.

 

No. Disabled stops the endpoint from being called by wpgetapi_endpoint or scheduled events but keeps the full configuration in the option. The endpoint, headers, body template, and authentication settings remain ready to re-activate by dragging the card back to Active.

 

The board streams cards lazily per column, and WPGetAPI stores endpoints inside a single option, so the practical limit is whatever the WordPress options table can hold. Boards stay responsive into the low thousands of endpoints without any server side pagination tweaks.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView