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

MemberPress Developer Tools REST API

REST API exposed by the MemberPress Developer Tools add-on on the site owner's own WordPress installation, under the WordPress REST namespace mp/v1. Covers members, memberships, transactions, subscriptions, groups, rules, coupons, reminders and the event log, plus webhook subscribe/unsubscribe. Authenticated with a Developer Tools API key sent in the MEMBERPRESS-API-KEY header (the documentation repository and Postman collection send the same key in the Authorization header), or as a logged-in WordPress user holding the remove_users capability. MemberPress is self-hosted, so the base URL is always the customer's own site.

MemberPress Developer Tools REST API is one of 2 APIs that MemberPress publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Members, Memberships, Subscription, Transaction, and Webhook. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 53 operations across 29 paths, organized into 11 resource areas, and defines 1 schema. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://{site}/wp-json/mp/v1.

53 operations 29 paths 1 schemas 9 DELETE22 GET14 POST8 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://{site}/wp-json/mp/v1
Authentication
API Key, API Key
License
Proprietary
Resource Areas
11

Authentication & Security 2

MemberPress Developer Tools REST API declares 2 security schemes for authenticating requests. An API key is passed in the header as MEMBERPRESS-API-KEY (MemberPressApiKey). An API key is passed in the header as Authorization (AuthorizationApiKey). By default, every request must be authenticated.

  • MemberPressApiKey — Developer Tools API key, as documented at https://memberpress.com/docs/overview-of-using-the-developer-tools/
  • AuthorizationApiKey — The same Developer Tools API key sent in the Authorization header, as used by the MemberPress REST API documentation repository and its Postman collection. Not…

Paths & Operations 53

Across 29 paths, the API surfaces 53 operations — 9 DELETE, 22 GET, 14 POST, 8 PUT. They span 11 resource areas, including Authentication, Members, Memberships, Transactions, Subscriptions, Groups, Rules, Coupons, and 3 more. Each is listed below with its method, path, parameters, and response codes.

Authentication 2

Verify the API key and inspect permissions.

GET
/me
Verify authentication
verifyAuthentication → 200401
GET
/me/permissions
Get user permissions
getMyPermissions → 200401
Members 6

Members are the WordPress users MemberPress tracks.

GET
/members
List members
listMembers 8 params → 200401
POST
/members
Create member
createMember body → 200401
GET
/members/{id}
Get member
getMember 1 param → 200401
PUT
/members/{id}
Update member
updateMember 1 param body → 200401
DELETE
/members/{id}
Delete member
deleteMember 1 param → 200401
GET
/member_options
Get member options
getMemberOptions → 200401
Memberships 7

Memberships are the products members buy.

GET
/memberships
List memberships
listMemberships 7 params → 200401
POST
/memberships
Create membership
createMembership body → 200401
GET
/memberships/{id}
Get membership
getMembership 1 param → 200401
PUT
/memberships/{id}
Update membership
updateMembership 1 param body → 200401
DELETE
/memberships/{id}
Delete membership
deleteMembership 1 param → 200401
GET
/membership_options
Get membership options
getMembershipOptions → 200401
GET
/memberships/{id}/member_options
Get membership member options
getMembershipMemberOptions 1 param → 200401
Transactions 7

One-time and recurring payment records.

GET
/transactions
List transactions
listTransactions 10 params → 200401
POST
/transactions
Create transaction
createTransaction body → 200401
GET
/transactions/{id}
Get transaction
getTransaction 1 param → 200401
PUT
/transactions/{id}
Update transaction
updateTransaction 1 param body → 200401
DELETE
/transactions/{id}
Delete transaction
deleteTransaction 1 param → 200401
POST
/transactions/{id}/refund
Refund transaction
refundTransaction 1 param → 200401
POST
/transactions/{id}/refund_and_cancel
Refund transaction and cancel subscription
refundTransactionAndCancelSubscription 1 param → 200401
Subscriptions 8

Recurring billing agreements.

GET
/subscriptions
List subscriptions
listSubscriptions 9 params → 200401
POST
/subscriptions
Create subscription
createSubscription body → 200401
GET
/subscriptions/{id}
Get subscription
getSubscription 1 param → 200401
PUT
/subscriptions/{id}
Update subscription
updateSubscription 1 param body → 200401
DELETE
/subscriptions/{id}
Delete subscription
deleteSubscription 1 param → 200401
POST
/subscriptions/{id}/cancel
Cancel subscription
cancelSubscription 1 param → 200401
POST
/subscriptions/{id}/suspend
Suspend subscription
suspendSubscription 1 param → 200401
POST
/subscriptions/{id}/resume
Resume subscription
resumeSubscription 1 param → 200401
Groups 5

Groups of memberships, used for pricing pages and upgrade paths.

GET
/groups
List groups
listGroups 5 params → 200401
POST
/groups
Create group
createGroup body → 200401
GET
/groups/{id}
Get group
getGroup 1 param → 200401
PUT
/groups/{id}
Update group
updateGroup 1 param body → 200401
DELETE
/groups/{id}
Delete group
deleteGroup 1 param → 200401
Rules 5

Smart Rules that protect content and drip access.

GET
/rules
List rules
listRules 5 params → 200401
POST
/rules
Create rule
createRule body → 200401
GET
/rules/{id}
Get rule
getRule 1 param → 200401
PUT
/rules/{id}
Update rule
updateRule 1 param body → 200401
DELETE
/rules/{id}
Delete rule
deleteRule 1 param → 200401
Coupons 5

Discount codes applied at checkout.

GET
/coupons
List coupons
listCoupons 5 params → 200401
POST
/coupons
Create coupon
createCoupon body → 200401
GET
/coupons/{id}
Get coupon
getCoupon 1 param → 200401
PUT
/coupons/{id}
Update coupon
updateCoupon 1 param body → 200401
DELETE
/coupons/{id}
Delete coupon
deleteCoupon 1 param → 200401
Reminders 5

Scheduled member emails triggered by events.

GET
/reminders
List reminders
listReminders 5 params → 200401
POST
/reminders
Create reminder
createReminder body → 200401
GET
/reminders/{id}
Get reminder
getReminder 1 param → 200401
PUT
/reminders/{id}
Update reminder
updateReminder 1 param body → 200401
DELETE
/reminders/{id}
Delete reminder
deleteReminder 1 param → 200401
Events 1

The MemberPress event log.

GET
/events
List events
listEvents 6 params → 200401
Webhooks 2

Subscribe callback URLs to MemberPress events.

POST
/webhooks/subscribe
Subscribe to events
subscribeWebhook body → 200401
DELETE
/webhooks/unsubscribe/{id}
Unsubscribe from events
unsubscribeWebhook 1 param → 200401

Schemas 1

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

Error
object
MemberPress returns WordPress REST API errors. The documented success envelope is {"success": true, "data": {...}}; WordPress core errors carry code, message a…
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

memberpress-developer-tools-openapi.yml Raw ↑

Other APIs MemberPress publishes across the network.

MemberPress AI Foundation MCP Server
Where this information came from

This is an independent, third-party profile of MemberPress Developer Tools 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.