Skip to main content
POST
Refresh an authentication session

Authorizations

Authorization
string
header
required

API token authentication using format <api token id>:<api client secret>

Headers

Grid-Wallet-Signature
string

Full API-key stamp built over the prior payloadToSign with the current session API keypair. Required on the signed retry; ignored on the initial call.

Request-Id
string

The requestId returned in the prior 202 response, echoed back on the signed retry so the server can correlate it with the issued challenge. Required on the signed retry; must be paired with Grid-Wallet-Signature.

Path Parameters

id
string
required

The id of the active session to refresh.

Body

application/json

Request body for refreshing an active authentication session. The clientPublicKey is required on both steps of the signed-retry flow and must match on both. The client keeps the matching private key as the new session signing key. On the initial call, Grid binds the supplied key into the session-creation payload returned as payloadToSign.

clientPublicKey
string
required

Client-generated P-256 public key as a compressed SEC1 point in lowercase hex: 66 characters, a 02 or 03 prefix followed by the 32-byte X coordinate. The client keeps the matching private key as the new session signing key. An uppercase or uncompressed key is rejected with 400 INVALID_INPUT.

Required string length: 66
Pattern: ^0[23][0-9a-f]{64}$
Example:

"02f45f2a22c908b9ce09a7150e514afd24627c401c38a4afc164e1ea783adaaa31"

Response

The session refresh's underlying wallet-provider activity is still in flight — a WalletOperationProcessing body with status: "PROCESSING". The client re-sends the byte-identical signed retry until it gets the 201; the backend also reconciles the activity to terminal on its own.

200 response returned by an Embedded Wallet operation that the wallet provider has accepted but not yet settled — a consensus- or approval-gated activity that is still in flight. It is not an error and needs no client action beyond patience: the backend reconciles the operation to its terminal state on its own. The client MAY re-send the byte-identical request to converge sooner; the request is idempotent and returns the settled success response once the operation completes.

status
enum<string>
required

Always PROCESSING. Marks a still-in-flight operation whose terminal result is not yet available.

Available options:
PROCESSING
Example:

"PROCESSING"

message
string

Human-readable explanation that the operation is still being processed and the same request may be retried.

Example:

"This login is still being processed. Retry the same request in a moment."