Skip to main content
GET
/
nonce
Get relayer nonce
curl --request GET \
  --url https://relayer.forka.st/nonce
{
  "nonce": "7"
}
Retrieve the next nonce that the relayer expects for a Safe execution (SAFE) or Safe deployment (SAFE-CREATE). Fetching the nonce before building each payload keeps builders in sync with the server-side queue and prevents duplicate submissions.
Invoke https://relayer.forka.st/nonce with the standard L2 headers (FORKAST_ADDRESS, FORKAST_SIGNATURE, FORKAST_TIMESTAMP, FORKAST_API_KEY, FORKAST_PASSPHRASE). The relayer enforces that the address query matches the authenticated account.

​
Query parameters

NameTypeRequiredDescription
addressstringYesSafe or Safe owner address tied to your API key.
typestringYesEither SAFE for executions or SAFE-CREATE for deployments.

​
Usage notes

  • The relayer keeps separate sequences per type. Always request the nonce for the operation you intend to send next.
  • Responses return decimal strings to avoid precision loss. Submit the same value verbatim inside /submit payloads.
  • If the backend is re-syncing, you may receive a 409 error instructing you to retry once sync completes.

Query Parameters

​
address
string
required

Safe or owner address tied to your credentials.

​
type
enum<string>
required

Nonce namespace to inspect.

Available options:
SAFE,
SAFE-CREATE

Response

Nonce lookup succeeded.

​
nonce
string
required

Next nonce the relayer expects for the provided type.

Example:

"7"