Skip to content
qibdo qibdo
v1
API version
  • v1
Theme
Book a demo

HMAC With Crypto Key

POST
/vault/v1/workspaces/{workspace}/engines/qibdo/cryptoKeys/{id}:hmac
 
curl --request POST \
  --url https://example.com/vault/v1/workspaces/example/engines/qibdo/cryptoKeys/example:hmac \
  --header 'Content-Type: application/json' \
  --data '{ "workspace": "example", "id": "example", "message": "example", "key_version": "example", "mac_algorithm": "example" }'

AIP-136 custom method. Generates a MAC tag under a MAC key. The tag bytes are returned as opaque bytes; clients should compare via constant-time equality on the return path.

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
workspace
required
string

The workspace the crypto key belongs to.

id
required
string

The unique identifier of the MAC crypto key.

Request Body required

Section titled “Request Body required ”
Media type application/json

Request payload for Hmac With Qibdo Crypto Key

Carries the input fields required to hmac with qibdo crypto key.

object
workspace
required

The workspace the crypto key belongs to.

string
id
required

The unique identifier of the MAC crypto key.

string
message
required

The message bytes to authenticate.

string format: bytes
key_version

Optional explicit version number to use. Defaults to the latest ENABLED version.

string
mac_algorithm

Optional MAC algorithm hint (e.g. “sha2-256”, “sha2-384”, “sha2-512”).

string
Example generated
{
  "workspace": "example",
  "id": "example",
  "message": "example",
  "key_version": "example",
  "mac_algorithm": "example"
}

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

Response payload from Hmac With Qibdo Crypto Key

Carries the output produced by hmac with qibdo crypto key.

object
tag

The MAC tag bytes.

string format: bytes
key_version

The version of the MAC key that produced the tag.

string
Example generated
{
  "tag": "example",
  "key_version": "example"
}

default

Section titled “default ”

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}