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

Paymob Subscriptions API

The Subscriptions Module manages subscription plans (create, list, update, suspend, resume) and per-customer subscriptions billed against tokenised cards. Lifecycle operations cover suspend, resume, cancel, secondary card attachment, and transaction inspection. Initial subscription creation flows through /v1/intention/ for card capture.

Paymob Subscriptions API is one of 18 APIs that Paymob publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments, Subscription, and Recurring Billing. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 8 operations across 7 paths, and defines 1 schema. It is described by OpenAPI 3.0.3, at version 2.0.

Requests are made against 5 base URLs: https://accept.paymob.com, https://ksa.paymob.com, https://uae.paymob.com, https://oman.paymob.com, https://pakistan.paymob.com.

8 operations 7 paths 1 schemas 4 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0
Servers
https://accept.paymob.com
https://ksa.paymob.com
https://uae.paymob.com
https://oman.paymob.com
https://pakistan.paymob.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

  • BearerAuth — Bearer authtoken from /api/auth/tokens (60-minute TTL).

Paths & Operations 8

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

Subscriptions 8
GET
/api/acceptance/subscriptions/{subscription_id}
Retrieve Subscription
retrieveSubscription 1 param → 200
PUT
/api/acceptance/subscriptions/{subscription_id}
Update Subscription
updateSubscription 1 param body → 200
POST
/api/acceptance/subscriptions/{subscription_id}/suspend
Suspend Subscription
suspendSubscription 1 param → 200
POST
/api/acceptance/subscriptions/{subscription_id}/resume
Resume Subscription
resumeSubscription 1 param → 200
POST
/api/acceptance/subscriptions/{subscription_id}/cancel
Cancel Subscription
cancelSubscription 1 param → 200
GET
/api/acceptance/subscriptions/{subscription_id}/last-transaction
Get Last Subscription Transaction
getLastSubscriptionTransaction 1 param → 200
GET
/api/acceptance/subscriptions/{subscription_id}/transactions
List Subscription Transactions
listSubscriptionTransactions 1 param → 200
GET
/api/acceptance/subscriptions/{subscription_id}/card-tokens
List Subscription Card Tokens
listSubscriptionCardTokens 1 param → 200

Schemas 1

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

Subscription
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paymob-subscriptions-api-openapi.yml Raw ↑

Other APIs Paymob publishes across the network.

Paymob Intentions API
Paymob Card Tokens API
Paymob Accounts API
Paymob Authentication API
Paymob Capture API
Paymob Checkout API
Paymob Disbursement API
Paymob Orders API
Paymob Payment Keys API
Paymob Payment Links API
Paymob Payments API
Paymob Refund API
Where this information came from

This is an independent, third-party profile of Paymob Subscriptions 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.