zkMe · Authentication Profile
Zkme Authentication
Authentication
The zkMe Open API authenticates every request with an AppID + API key pair issued from the zkMe dashboard. Unusually, the credentials are passed as request-body fields (mchNo = AppID, apiKey = API key) rather than as an Authorization header, so they are not expressible as a standard OpenAPI securityScheme. The zkKYB endpoint and all SDK-initialized flows instead use a short-lived accessToken (valid 30 minutes) minted server-side via POST https://nest-api.zk.me/api/token/get.
zkMe secures its APIs with apiKey and bearerToken across 2 declared security schemes, as derived from its OpenAPI definitions.
CompanyCrypto Web3IdentityKYCKYBComplianceZero KnowledgeDecentralized IdentityAnti-SybilTransaction Monitoring
Methods: apiKey, bearerToken
Schemes: 2
OAuth flows:
API key in: body
Security Schemes
apiKeyPair apiKey
accessToken bearerToken