Build with the ChipRegister API
Connect veterinary software, shelters, municipalities and pet platforms to a secure global pet-registration ecosystem.
# Verify a registered microchip GET /api/v1/microchips/985141000123456 Authorization: Bearer YOUR_API_KEY { "registered": true, "lost_alert": false, "certificate_valid": true, "owner_verified": true }
Designed for connected pet services
The planned API will allow authorized systems to verify registrations and coordinate recovery workflows without exposing unnecessary personal data.
Microchip Verification
Check whether a microchip is registered and retrieve an authorized public status response.
Lost Pet Status
Identify whether a registered pet has an active Lost Pet Alert.
Certificate Validation
Verify the authenticity and current status of a ChipRegister certificate.
Event Webhooks
Receive authorized notifications when important registration or Lost Pet events occur.
QR Verification
Integrate digital QR verification into partner applications and websites.
Organization Access
Support clinics, shelters, associations and approved institutional systems.
Planned endpoints
The following examples represent the intended API structure. They are not active public endpoints yet.
/api/v1/microchips/{number}
Verify microchip registration status.
/api/v1/lost-pets/{number}
Check for an active Lost Pet Alert.
/api/v1/certificates/{id}
Validate a registration certificate.
/api/v1/qr/{token}
Verify an authorized QR identifier.
/api/v1/found-reports
Report a found pet through a partner.
{
"data": {
"registered": true,
"microchip": "985141******456",
"species": "dog",
"country": "ES",
"lost_alert": false,
"certificate_valid": true
},
"meta": {
"request_id": "req_01H...",
"api_version": "v1"
}
}
Built for trusted partners
Controlled and auditable access
API access will be granted according to partner identity, purpose and permissions.
Every integration receives restricted credentials appropriate to its role.
Automated controls protect availability and prevent abusive usage.
Sensitive operations are recorded for monitoring and accountability.
Authentication
Production requests will use secure credentials sent over HTTPS. Never include an API key in public JavaScript or public repositories.
OAuth 2.0 and more granular organization roles can be introduced for advanced integrations.
Proposed API plans
Final quotas and pricing will be defined before the API is launched publicly.
Professional
For veterinary clinics, shelters and production software integrations.
Managed quota Contact API TeamEnterprise
For municipalities, networks and high-volume institutional partners.
Custom capacity Discuss IntegrationBecome an early API partner
Tell us about your organization, software and expected integration. Early partners can help define the first production API workflows.
Request API Access