---
title: "Submit token permit"
method: POST
path: "/api/v1/token-permit"
tags: ["External Wallet Access Mode"]
---

# Submit token permit

`POST /api/v1/token-permit`

Submits an EIP-2612 permit signature so UR contracts can spend tokens from the user's wallet without an on-chain approve transaction. Used for card spending against the user's UR fiat balance.

## Headers

- `tokenId` string, required
- `network` string, required
- `sign` string, required
- `hash` string, required
- `deadline` string, required

## Request body

- object
  - `address` string, required — Contract address of the token being approved.
  - `amount` string, required — Amount to approve (decimal string).
  - `permitAmount` string, required — Permit amount signed in the EIP-2612 permit (decimal string).
  - `permitDeadline` integer, required — Unix seconds until which the permit is valid.
  - `permitV` integer, required — EIP-2612 signature component v.
  - `permitR` string, required — EIP-2612 signature component r (32-byte hex).
  - `permitS` string, required — EIP-2612 signature component s (32-byte hex).

## Response `200`

Response envelope. For the user API, retCode 0 means success; for the partner API, code 0 means success. Business rejections return HTTP 200 with a non-zero code.

- EwaEnvelope — Standard response envelope for the user API (api.ur.app).
  - `retCode` integer, required — 0 on success; non-zero indicates failure.
  - `retMsg` string, required — Human-readable message; error details when retCode is non-zero.
  - `result` unknown
  - `timeNow` integer — Server timestamp in milliseconds.

---

[API](https://skmtc.net/ur/apis/ur-api.md) · [All operations](https://skmtc.net/ur/apis/ur-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ur/ur-api/revisions/087dcf516ce2/schema)