Operations

This set of API calls allows you to fetch operations on various Keyless entities.

Last updated 4 months ago

Was this helpful?

Get a user's pending operations

get

Get a user's pending operations

Authorizations

Path parameters

userIdstring · Uppercase HEX stringrequired

The user id

Responses

application/json

get

curl -L \
  --url '/v2/users/{userId}/operations/pending' \
  --header 'X-Api-Key: YOUR_API_KEY'

200

400

401

404

406

500

[
  {
    "operationId": "123456abcdef",
    "operationPayload": "payload",
    "externalUserId": "abcdef123456",
    "authType": "biom"
  },
  {
    "operationId": "654321fedcba"
  }
]

An user's pending operations

Get a customer operation

get

Get a customer operation

Authorizations

Path parameters

operationIdstringrequired

Unique operation identifier set and managed by the client

Responses

application/json

get

curl -L \
  --url '/v2/operations/{operationId}' \
  --header 'X-Api-Key: YOUR_API_KEY'

200

400

401

404

406

500

{
  "id": 1,
  "timestamp": "2020-01-02T03:04:05.68",
  "nodeId": "text",
  "userId": "0123456789ABCDEF",
  "apiKey": "text",
  "externalUserId": "text",
  "operationId": "text",
  "operationPayload": "text",
  "result": true,
  "authType": "biom",
  "state": "approved"
}

A customer operation

Get the customer public key

get

Get the customer public key in PEM format

Authorizations

Responses

application/json

get

curl -L \
  --url '/v2/verify-jwt/public-key' \
  --header 'X-Api-Key: YOUR_API_KEY'

200

400

401

406

{
  "content": "-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwJ1\n-----END PUBLIC KEY-----"
}

The public key in PEM format

Create a pending operation

post

Create a pending operation

Authorizations

Path parameters

userIdstring · Uppercase HEX stringrequired

The user id

Body

externalUserIdstringoptional

User id set and managed by the client

operationIdstringrequired

Unique operation identifier set and managed by the client

operationPayloadstringoptional

Operation payload set and managed by the client

Responses

application/json

post

curl -L \
  --request POST \
  --url '/v2/users/{userId}/operations' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "externalUserId": "text",
    "operationId": "text",
    "operationPayload": "text"
  }'

200

400

401

404

406

409

415

500

{
  "success": true
}

Operation created successfully

Verify a signed JWT message

post

Verify a signed JWT message. The only format accepted for now is a JWT generated by a PIN signature

Authorizations

Body

messagestring · JWTrequired

The signed JWT message

Responses

application/json

post

curl -L \
  --request POST \
  --url '/v2/verify-jwt' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "message": "text"
  }'

200

400

401

406

415

{
  "result": true
}

The verification completed successfully. Check the result to see if the signature is valid or not