Lead Claims Test Suite #
The Claims Test Suite is an interactive tool for testing certificate claiming functionality before going live.
Features #
The Claims Test Suite provides:
- Certificate Claiming — Claim certificates by key or URL
- Access Checking — Verify if you have access to a certificate
- Real-time Status — Monitor API connections and authentication
- Available Certificates — Browse unclaimed certificates (generators only)
- Claimed Certificates — View certificates you’ve claimed
- Activity Log — Detailed log of all operations
User Types #
The claims system has two user types:
| Type | Role | Capabilities |
|---|---|---|
| Lead Generator | Creates certificates | View all certificates they create, cannot claim |
| Lead Buyer | Claims certificates | Claim certificates, view only claimed certificates |
When signing in, select the appropriate user type for testing.
Getting Started #
1. Sign In as Lead Buyer #
Click Sign In and authenticate with Google or GitHub. Make sure to sign in as a Lead Buyer to test claiming functionality.
2. Check Connection Status #
Verify both services are connected:
| Status | Meaning |
|---|---|
| Auth Service: Connected | Successfully authenticated |
| Billing API: Connected | Can perform claim operations |
| User Type: Buyer | Correct role for claiming |
3. Claim a Certificate #
Enter a certificate key or full URL in the Claim a Certificate panel:
- Certificate key:
abc123def456... - Full URL:
https://cert.veriform.co/view/abc123def456...
Click Claim to attempt the claim operation.
4. View Claimed Certificates #
Switch to the My Claimed tab to see all certificates you’ve successfully claimed.
Certificate Operations #
Claiming a Certificate #
- Obtain a certificate key from a lead generator
- Enter the key in the claim input field
- Click Claim
- View the result in the response panel
Successful Claim Response:
{
"success": true,
"message": "Certificate claimed successfully",
"certificate_id": 123,
"cert_key": "abc123def456...",
"claimed_date": "2025-11-28T12:00:00"
}
Failed Claim Response:
{
"success": false,
"message": "Certificate already claimed"
}
Checking Access #
Use the Check Certificate Access panel to verify if you can view a certificate:
| Response | Meaning |
|---|---|
hasAccess: true |
You can view this certificate |
hasAccess: false |
No access to this certificate |
Access reasons:
owner— You created this certificate (generator)claimed— You claimed this certificate (buyer)not_claimed— Certificate not claimed by younot_found— Certificate doesn’t exist
Status Indicators #
Connection Status Cards #
| Card | Success | Failure |
|---|---|---|
| Auth Service | Connected to auth | Auth unavailable |
| Billing API | API responding | API error |
| User Type | Buyer/Generator | Not logged in |
| User ID | Database user ID | No user |
Activity Log #
The log shows all operations in real-time:
[12:00:00] Logged in as buyer@example.com
[12:00:01] Token: eyJhbGciOiJIUzI1NiIs...
[12:00:02] Billing API connected
[12:00:03] Loaded 5 claimed certificates
[12:00:10] Attempting to claim certificate: abc123...
[12:00:11] Certificate claimed successfully: abc123...
Certificate Tables #
Available to Claim (Generators Only) #
If logged in as a generator, you can see unclaimed certificates:
| Column | Description |
|---|---|
| Cert Key | Truncated certificate identifier |
| Domain | Source domain where certificate was created |
| Created | Certificate creation date |
| Action | Quick claim button |
My Claimed (Buyers Only) #
Certificates you have successfully claimed:
| Column | Description |
|---|---|
| Cert Key | Truncated certificate identifier |
| Domain | Source domain |
| Claimed | Date you claimed it |
| View | Link to view certificate details |
Troubleshooting #
“Only lead buyers can claim certificates” #
You’re signed in as a lead generator. Sign out and sign back in with the Lead Buyer option.
“Certificate already claimed” #
This certificate has already been claimed by another user or yourself.
“Certificate not found” #
The certificate key doesn’t exist. Verify you have the correct key.
“No auth token available” #
Sign out and sign back in to refresh your authentication.
“Billing API error” #
The billing service may be unavailable. Check the status panel and try again later.
Access Denied When Viewing Certificate #
You can only view certificates you’ve claimed. Use Check Access to verify your permissions.
API Endpoints Used #
The Claims Test Suite interacts with these API endpoints:
| Endpoint | Method | Description |
|---|---|---|
/api/certificates/claim |
POST | Claim a certificate |
/api/certificates/claimed |
GET | List your claimed certificates |
/api/certificates/{key}/access |
GET | Check access to a certificate |
/api/certificates/{key}/details |
GET | Get certificate details |
/api/certificates |
GET | List all certificates (generators) |
Testing Workflow #
Complete Test Flow #
- Generate a certificate using the SDK Test Suite
- Copy the certificate key from the result
- Open the Claims Test Suite
- Sign in as a Lead Buyer
- Paste the certificate key and click Claim
- Verify the claim succeeded
- View the certificate in My Claimed tab
Testing Access Control #
- Sign in as Lead Generator and create a certificate
- Note the certificate key
- Sign out and sign in as Lead Buyer
- Use Check Access — should show
hasAccess: false - Claim the certificate
- Use Check Access again — should show
hasAccess: true
Next Steps #
- SDK Test Suite Guide — Generate certificates for testing
- Quickstart Guide — Integrate the SDK into your site
- Billing — Manage your subscription and usage