Get the device context
Non-custodial accounts are available in sandbox only. Production non-custodial accounts are on the roadmap.
Confirms that the authorization key that signed X-Device-Authorization is registered and active, and returns its device context. The Digital Asset Accounts SDK calls this to check a stored registration, for example when the app starts.
The SDK signs this request over an empty body. Your backend relay must forward the header unchanged. This call doesn’t issue a token or create a session.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Compact ES256 JWS that the Digital Asset Accounts SDK creates on the end user's device. It signs this request's method, path, and exact body bytes (an empty body for GET requests) with the authorization key the end user registered. The SDK creates a new value for every new request.
A missing value returns 400 (error code 420031). A value that isn't a well-formed compact JWS returns 401 (error code 420031).
The SDK gives each value an expiry at most 5 minutes after it signs it. Unless the operation says otherwise, Circle rejects a value whose expiry has passed or whose signing time is in the future, allowing 60 seconds of clock difference either way, with 400 (error code 420031). A device clock that's off by more than 60 seconds causes the same error. Retry within the value's lifetime, or let the SDK sign the request again.
Your backend relay must forward this header, and the request body, exactly as the SDK sent them. Don't parse, reformat, or re-serialize the body. If the bytes change, Circle rejects the request.
Compact ES256 JWS created by the Digital Asset Accounts SDK on the end user's device.
64 - 8192"eyJhbGciOiJFUzI1NiJ9.e30.AAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1Njc4OTo7PD0-Pw"
Response
Successfully retrieved the device context.
The active device registration for an end customer.