Skip to content

OpenAPI gaps (in code, not in public Postman)

These ptrader-api-gateway /openapi routes exist in code but are outside the locked Postman scope (or only partially covered). Do not document as supported until product adds them to the collection or explicitly approves.

Method Path Controller Notes
POST /openapi/fiat[/v1]/generate_qr_code FiatOpenApiController QR write
POST /openapi/fiat[/v1]/generate/static/qr_code same
POST /openapi/fiat[/v1]/update/qr_code same
POST /openapi/fiat[/v1]/decode/kyb_qr_code same
GET /openapi/v1/sub-account/apikey/ip-restriction SubAccountController
POST /openapi/v1/sub-account/apikey/add-ip-restriction same
POST /openapi/v1/sub-account/apikey/delete-ip-restriction same
GET /openapi/migration/v4/payout-outlets/{id} FiatMigrationApiController list path is in Postman; by-id variant not
GET /openapi/migration/v4/payout-outlet-categories/{id} same

Legacy aliases such as /openapi/order-new/... exist on some controllers — treat as non-public unless added to Postman.

Still incomplete inside scoped OpenAPI

  • Full response/request JSON Schemas from Java DTOs
  • Per-endpoint error code lists
  • Per-endpoint rate-limit weights