Unified entry
POST /api/entry — one URL, method selects the capability
Request
POST /api/entry
Content-Type: application/jsonThe body is a flat JSON object. Common fields (almost every method):
| Field | Meaning |
|---|---|
app_id | Application id |
method | Capability name, e.g. order.query |
format | Always JSON |
charset | Always UTF-8 |
sign_type | Always RSA2 |
version | e.g. 1.0 |
timestamp | Millisecond timestamp as a string |
sign | App RSA2 signature (Base64) |
Business fields depend on method: admin calls may include scope_id / key_id; payments may include merchant_order_no, order_amount, and so on. Full enums and examples: API Reference.
Response envelope
HTTP status is usually 200. Success is determined by JSON:
{
"code": "0",
"msg": "success",
"data": { },
"psn": "...",
"sign": "..."
}| Field | Meaning |
|---|---|
code | "0" means success; otherwise a business / admission error |
msg | Human-readable message |
data | Object on success; often null on failure |
psn | Platform serial number |
sign | Platform RSA2 reply signature (when present) |
Do not rely on HTTP status alone — use code.
Merchant context
Most payment and Access Key admin requests include:
institution_nomerchant_nostore_no
These must match stores opened to the app (openApp). When an Access Key is bound to a store, morph 2 also checks that binding.