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 Intentions API

The v1 Intentions API is Paymob's modern entry point for payment acceptance. The merchant backend creates an intention with the secret key and an array of payment_methods (integration IDs or named methods like apple_pay, tabby, tamara, stc_pay, easypaisa, jazzcash). Paymob returns a client_secret used to launch the Unified Checkout, render the Pixel component, or confirm the payment headlessly.

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

This API exposes 1 JSON Schema definition.

Tagged areas include Payments, Intentions, Checkout, and MENA. The published artifact set on APIs.io includes API documentation, an API reference, an OpenAPI specification, and 1 JSON Schema.

This API exposes 4 operations across 4 paths, and defines 7 schemas. 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.

4 operations 4 paths 7 schemas 1 GET2 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 Intentions 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 4

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

Intentions 4
POST
/v1/intention/
Create Intention
createIntention body → 201400401
PUT
/v1/intention/{client_secret}
Update Intention
updateIntention 1 param body → 200
GET
/v1/intention/element/{public_key}/{client_secret}/
Retrieve Intention
retrieveIntention 2 params → 200
POST
/v1/intentions/confirm/
Confirm Payment Intention
confirmIntention body → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are BillingData (12 properties), Transaction (12 properties), Intention (11 properties), IntentionRequest (11 properties). Each schema is shown below with its type and property counts.

Transaction
object
12 properties
IntentionRequest
object
11 properties 5 required
IntentionItem
object
5 properties 2 required
Error
object
2 properties
BillingData
object
12 properties
Intention
object
11 properties
Customer
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paymob-intentions-api-openapi.yml Raw ↑

Other APIs Paymob publishes across the network.

Paymob Subscriptions 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 Intentions 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.