Skip to main content
GET
/
v2
/
notifications
/
publicKey
/
{id}
Get a notification signature public key
curl --request GET \
  --url https://api.circle.com/v2/notifications/publicKey/{id} \
  --header 'Authorization: Bearer <token>'
{
  "data": {
    "id": "09379bc1-4871-45ad-8b8b-8027795df70d",
    "algorithm": "ECDSA_SHA_256",
    "publicKey": "QFkwewylAoZIzj0CBQYIKoZIzj0DAQcDQgAEEext6d7AimvYFDAKBwsUsGXrhqmRHNPYum7V/BwfvJLmJeSMe2V0b9eWKPuFxAEH8HCY/MSZdBI+q/E6IdPnSg==",
    "createDate": "2023-06-01T18:18:06.931526Z"
  }
}

Authorizations

​
Authorization
string
header
required

Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are requred to make a successful request.

Headers

​
X-Request-Id
string<uuid>

Developer-provided identifier for this request, used for tracing requests in Wallets API logs and the Developer Console, and when communicating with Circle Support. Must be a UUID to appear in logs. Non-UUID values are accepted by the API but are ignored by logging and tracing systems.

A unique identifier, which can be helpful for identifying a request when communicating with Circle support.

Example:

"2adba88e-9d63-44bc-b975-9b6ae3440dde"

Path Parameters

​
id
string<uuid>
required

The universally unique identifier of the resource.

Example:

"b3d9d2d5-4c12-4946-a09d-953e82fae2b0"

Response

Successfully retrieved a digital notification signature.

​
data
object