Skip to main content

useConsentSignature

Requests a consent-signature response for one consent record.

When to use it​

Call mutate with the consent ID; this is a signature workflow, not consent acceptance.

Setup​

Call it from a client-side React component below OvokProvider so it uses the client configured at that provider boundary.

Hook arguments​

The hook takes no configuration arguments. Call mutate(payload) when the user or workflow is ready to run the operation; the payload and result types are shown below.

TypeScript signature​

(): OvokMutationState<{ consentId: string; }, OvokConsentSignatureResponse>

Mutation state​

The operation runs only when you call mutate(payload). The payload type is { consentId: string; }; the returned promise and data carry OvokConsentSignatureResponse.

FieldMeaning
dataLatest successful result, or undefined before success.
loadingWhether the mutation is running.
errorNormalized Error from the latest failure.
mutateStarts the operation, resolves with its result, and rejects on failure.
resetClears mutation data and error state.

Request behavior​

The mutation is explicit: collect and validate the input in your UI, disable repeated submission while loading is true, handle the rejected promise, and render error near the action.

Example​

Call the mutation from an event handler and show its error beside the action.

import { useConsentSignature } from '@ovok/core';

type Input = Parameters<ReturnType<typeof useConsentSignature>['mutate']>[0];

export function ConsentSignatureExample({ input }: { input: Input }) {
  const { mutate, loading, error } = useConsentSignature();
  async function submit() {
    try { await mutate(input); } catch { /* The hook exposes the error below. */ }
  }
  return <section>
    <button disabled={loading} onClick={() => void submit()}>Submit</button>
    {error && <p role="alert">{error.message}</p>}
  </section>;
}