Three steps to compliance integration
Connect your users' compliance accounts, call a standardized API, and let SeedLink handle the rest.
Connect
Secure credential linking via Connect SDK
Your users authenticate their compliance accounts through the Connect SDK iframe — a drop-in UI component that handles credential collection and validation. You never touch or store state system credentials directly.
- Drop-in iframe works in any web app
- Credentials encrypted with AES-256-GCM
- Supports Metrc, BioTrack, and more
- Users link accounts in under 60 seconds
// Create a link token for the Connect SDK
POST /v1/link/token/create
{
"organization_id": "org_abc123",
"user_id": "user_456"
}
→ 200 OK
{
"link_token": "link_tok_live_...",
"expiration": "2024-01-15T12:00:00Z"
}Standardized API
One interface for every state system
Use consistent endpoints for packages, plants, transfers, harvests, and reports — regardless of which state system your users are connected to. Our Common Data Model normalizes every response into a predictable shape.
- Unified schema across Metrc and BioTrack
- Consistent pagination, filtering, and sorting
- Predictable error codes and response shapes
- Comprehensive API reference documentation
// Pull packages from any state system
GET /v1/packages?connection_id=conn_456
→ 200 OK
{
"data": [
{
"id": "pkg_789",
"tag": "ABCDEF012345670000010042",
"product_name": "Blue Dream 3.5g",
"quantity": 100,
"unit": "grams",
"status": "active"
}
],
"pagination": {
"total": 248,
"page": 1,
"per_page": 25
}
}Compliance handled
State-specific rules managed behind the scenes
Every state has different field requirements, validation rules, and reporting formats. SeedLink manages these differences behind the scenes — when a state system changes its API or rules, we handle the update so you don't have to.
- State-specific field mapping and validation
- Automatic format conversions
- System change monitoring and updates
- No code changes when regulations shift
What we handle