Privicore
  1. Verified authenticator
Privicore
  • Privicore API
  • Utility
    • Utility
    • Check server health
      GET
    • Request command id status
      GET
  • Profile
    • Profile Model and Authentication Workflow
    • Register new profile
      POST
    • Authenticate
      POST
    • Retrieve profile id
      GET
    • Change password
      POST
    • Generate qr token for authorization
      POST
    • Reauthorize authorization token
      POST
    • Revoke authorization token
      POST
    • Retrieve token expiry
      POST
  • OAuth Application
    • OAuth Application Management
    • Register OAuth Application
      POST
    • Retrieve OAuth app configuration
      POST
    • Request OAuth app authorization code
      GET
    • Retrieve OAuth app authorization code
      POST
    • Obtain OAuth app access token
      POST
    • OAuth application list
      GET
    • Retrieve OAuth application scope
      GET
    • Refresh OAuth app access token
      POST
  • Public key
    • Public and Private Key Management
    • Generate your private and public keys
    • Register public key
    • Retrieve public key
    • Retrieve CAB public key
  • Data Token
    • Data Token Management
    • Reserve token space
    • Retrieve temporary data token
    • Exchange data for token
    • Upstream file via stream auth
    • Request data via token
    • Download data
    • Configure information security risk meta
    • Configure file meta
    • List data tokens
    • Update data token
    • Delete data
  • Device
    • Device Management
    • Request unique identifier (i.e. Register new device)
    • Retrieve unique identifier
    • Retrieve profile devices
    • Configure device meta
    • Approve device
    • Reject device
    • Retrieve device configuration
    • Remove device
  • Storage
    • Storage Device Management
    • Register storage device
    • List storage devices
    • Synchronize device
    • Remove storage
  • Verified authenticator
    • Authenticator and Voting Management
    • Register authenticator
      POST
    • List verified authenticators
      GET
    • Retrieve voting strategy
      GET
    • Set quorum size
      POST
    • Set quorum strategy
      POST
    • Set voting time limit
      POST
    • Set maximum voting attempts
      POST
    • Remove authenticator
      POST
    • Register voting configuration
      POST
    • Update voting configuration
      POST
    • List voting configurations
      GET
    • Retrieve voting configuration
      GET
  • Policy
    • Policy Management
    • List policy templates
    • Register policy
    • List active policies
    • List inactive policies
    • Activate policy
    • Deactivate policy
    • Delete policy
    • List registered policies
    • Retrieve registered policy
  • Voting
    • Voting Operations
    • Create voting
    • Check pool status
  • Schemas
    • Response
      • CommandAccepted
      • Unauthorized
      • ValidationErrors
    • Schemas
    • profileId
    • deviceIdentifier
    • directoryId
    • directoryName
    • directoryShortName
    • givenName
    • familyName
    • createdAt
    • meta
  1. Verified authenticator

Register authenticator

POST
/verified-authenticator/register

Overview#

Register an existing approved device as an Authenticator, enabling it to receive and respond to voting ballots for policy-driven authorization workflows.

Register Authenticator#

Endpoint: POST /verified-authenticator/register
Authentication: Required (Authorization token obtained from the step)
Content-Type: application/x-www-form-urlencoded

Request Parameters#

ParameterTypeRequiredDescription
deviceIdentifierstringYesThe unique identifier of the approved device to register as Authenticator
typeintegerNoAuthenticator type. Currently only 1 (Phone) is supported. Default: 1
Authenticator Types:
1 - Phone (default)

Use Case#

After a device has been registered, approved, and has a public key configured, use this endpoint to designate it as an Authenticator. Once registered as an Authenticator:
The device begins receiving encrypted ballots when policies trigger voting workflows
Ballots are delivered via RabbitMQ to the device
User or automated software can respond to ballots with approval or rejection
The device participates in poll resolution according to configured voting strategies
A device must be approved and have a registered public key before it can be registered as an Authenticator.
Device must be approved before Authenticator registration
Device must have a registered public key for encrypted ballot delivery
After registration, device immediately begins receiving ballots for new voting polls
Use the RabbitMQ configuration from device configuration to listen for incoming ballots
A single device can be registered as both Storage and Authenticator
Additional Authenticator types will be available in future releases

Request

Authorization
API Key
Add parameter in header
X-DPT-AUTHORIZATION
Example:
X-DPT-AUTHORIZATION: ********************
or
Header Params

Body Params application/x-www-form-urlencoded

Request Code Samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://sandbox.privicore.com:9009/verified-authenticator/register' \
--header 'X-DPT-AUTHORIZATION: <api-key>' \
--data-urlencode 'deviceIdentifier=' \
--data-urlencode 'type='

Responses

🟢202Success
This response does not have a body.
🟠401401
🟠422422
Modified at 2025-12-25 11:11:04
Previous
Authenticator and Voting Management
Next
List verified authenticators
Built with