NetHood Creative
  • Welcome
  • Shop
  • My Account
  • Imprint
  • Privacy Policy
  • Documentations
  • Support

Select your language

  • Deutsch (Deutschland)

Setting Up Didit Verification for Joomla

Didit Verification connects your Joomla website with Didit so logged-in users can complete an identity verification. After a successful verification, the user can automatically be assigned to a Joomla user group.

Requirements

You need:

  • A Joomla website
  • The installed Didit Verification extension
  • Access to the Didit Console
  • A Didit API Key
  • A Didit Workflow ID
  • The Didit Webhook Secret Key

1. Install the Extension

In the Joomla administrator area, open:

System -> Install -> Extensions

Upload and install the package.

After installation, you will find Didit Verification in the Joomla administrator area.

2. Enable the Plugin

Open:

System -> Manage -> Plugins

Search for:

Didit Webhook

Enable the plugin.

Without this plugin, webhooks, callback requests, and automatic license checks cannot be processed.

3. Find the Didit API Key and Webhook Secret

Open the Didit Console.

Go to:

Settings -> API & Webhooks

Copy:

  • API Key
  • Webhook Secret Key

The API Key is used to create new verification sessions with Didit. The Webhook Secret Key is used to securely verify incoming webhook requests.

4. Create or Copy the Workflow ID

In the Didit Console, open:

Workflows

Create a new workflow or open an existing one. Copy the Workflow ID.

The workflow defines which verification steps the user must complete, such as ID document verification, liveness check, or age verification.

5. Configure Didit Verification in Joomla

In the Joomla administrator area, open:

Components -> Didit Verification -> Settings

Enter:

  • API Key
  • Workflow ID
  • Webhook Secret
  • Approved Usergroup

The Approved Usergroup is the Joomla user group that a user is added to after a successful verification.

6. Add the Webhook URL in Didit

In the Didit Verification settings, you will see a Webhook URL.

Copy this URL and add it in the Didit Console under:

Settings -> API & Webhooks

as the webhook endpoint.

Didit sends verification results to this URL.

7. Callback URL

The callback URL is used to send users back to your website after completing the verification.

The extension automatically sends this URL to Didit when a new verification session is created. It is mainly shown for reference and checking.

8. Publish the Module

If you want to use the status module, open:

Content -> Site Modules

Search for:

Didit Verification Status

Publish the module in the desired position.

9. Enter the Pro License Key

If you use Pro features, enter your license key in the Didit Verification settings.

The license is automatically activated for the current domain and checked regularly.

Pro features may include:

  • Age verification
  • Storing document expiry dates
  • Revalidation when a document has expired
  • Showing the expiry date in the frontend

10. Run a Test

Log in as a user on the frontend and start the verification.

After completion, Didit sends the result to your Joomla website by webhook. If the verification is successful, the user is added to the selected Joomla user group.

Troubleshooting

The user is not approved

Check:

  • Is the Didit Webhook plugin enabled?
  • Is the webhook URL correctly entered in Didit?
  • Is the Webhook Secret Key correct?
  • Is an Approved Usergroup selected?

The webhook does not arrive

Check:

  • Is the website publicly reachable?
  • Is a firewall blocking the webhook?
  • If you use Cloudflare, check your firewall rules.

The API Key does not work

Check:

  • Was the API Key copied completely?
  • Does the API Key belong to the correct Didit organization?
  • Is the Workflow ID correct?

Sources

This guide is based partly on the official Didit documentation for API keys, workflows, hosted sessions, and webhooks:

  • Didit API Full Flow
  • Didit Webhooks
  • Didit API Reference
Copyright © 2026 NetHood Creative. All Rights Reserved.
Joomla! is Free Software released under the GNU General Public License.
  • Terms & Condition
  • EULA
  • Withdrawal Policy