BIMI Record Validator API
Overview
To use BIMI Record Validator, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/bimivalidatorExample
How to call the BIMI Record Validator API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/bimivalidator?domain=ebay.com" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/bimivalidator?domain=ebay.com', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/bimivalidator?domain=ebay.com', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/bimivalidator?domain=ebay.com", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"host": "ebay.com",
"bimi_host": "default._bimi.ebay.com",
"has_bimi_record": true,
"bimi_record": "v=BIMI1;l=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg;a=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem",
"bimi_records_count": 1,
"version": "BIMI1",
"svg_logo": {
"url": "https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg",
"status_code": 200,
"valid": true,
"file_size_bytes": 1518
},
"vmc_certificate": {
"url": "https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem",
"status_code": 200,
"valid": true
},
"issues_found": [],
"valid": true
}
}Authentication
The BIMI Record Validator API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the BIMI Record Validator API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the BIMI Record Validator API:
Validate BIMI Record
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
domain | string | required | The domain to validate the BIMI record for Format: domain (e.g., ebay.com) | - |
Response
The BIMI Record Validator API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<host>ebay.com</host>
<bimi_host>default._bimi.ebay.com</bimi_host>
<has_bimi_record>true</has_bimi_record>
<bimi_record>v=BIMI1;l=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg;a=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem</bimi_record>
<bimi_records_count>1</bimi_records_count>
<version>BIMI1</version>
<svg_logo>
<url>https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg</url>
<status_code>200</status_code>
<valid>true</valid>
<file_size_bytes>1518</file_size_bytes>
</svg_logo>
<vmc_certificate>
<url>https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem</url>
<status_code>200</status_code>
<valid>true</valid>
</vmc_certificate>
<issues_found>
</issues_found>
<valid>true</valid>
</data>
</response>
status: ok
error: null
data:
host: ebay.com
bimi_host: default._bimi.ebay.com
has_bimi_record: true
bimi_record: >-
v=BIMI1;l=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg;a=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem
bimi_records_count: 1
version: BIMI1
svg_logo:
url: https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg
status_code: 200
valid: true
file_size_bytes: 1518
vmc_certificate:
url: https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem
status_code: 200
valid: true
issues_found: []
valid: true
| key | value |
|---|---|
| host | ebay.com |
| bimi_host | default._bimi.ebay.com |
| has_bimi_record | true |
| bimi_record | v=BIMI1;l=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg;a=https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem |
| bimi_records_count | 1 |
| version | BIMI1 |
| svg_logo | {url:https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.svg,status_code:200,valid:true,file_size_bytes:1518} |
| vmc_certificate | {url:https://vmc.digicert.com/2b7216dc-27d2-4fbd-8472-f68790117238.pem,status_code:200,valid:true} |
| issues_found | [] |
| valid | true |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
host | string | The domain name that was validated | |
bimi_host | string | The BIMI DNS record host location | |
has_bimi_record | boolean | Whether a BIMI record exists for domain | |
bimi_recordPremium | string | The complete BIMI DNS record content | |
bimi_records_count | number | Number of BIMI records found in DNS | |
version | string | BIMI protocol version identifier | |
svg_logoPremium | object | SVG logo validation details | |
â”” url | string | URL where the SVG logo is hosted | |
â”” status_code | number | HTTP status code when fetching SVG logo | |
â”” valid | boolean | Whether the SVG logo file is valid | |
â”” file_size_bytes | number | Size of SVG logo file in bytes | |
vmc_certificatePremium | object | VMC certificate validation details | |
â”” url | string | URL where the VMC certificate is hosted | |
â”” status_code | number | HTTP status code when fetching certificate | |
â”” valid | boolean | Whether the VMC certificate is valid | |
issues_found | array | List of validation issues discovered during check | |
valid | boolean | Overall validity status of BIMI record |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access BIMI Record Validator through GraphQL to combine it with other API calls in a single request. Query only the bimi record validator data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
bimivalidator(
input: {
domain: "ebay.com"
}
) {
host
bimi_host
has_bimi_record
bimi_record
bimi_records_count
version
svg_logo {
url
status_code
valid
file_size_bytes
}
vmc_certificate {
url
status_code
valid
}
issues_found
valid
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The BIMI Record Validator API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
BIMI Record Validator requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The BIMI Record Validator API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for BIMI Record Validator
Official BIMI Record Validator packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
BIMI Record Validator works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for BIMI Record Validator?
How many credits does BIMI Record Validator cost?
Each successful BIMI Record Validator API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful bimi record validator lookups.
Can I use BIMI Record Validator in production?
The free plan is for testing and development only. For production use of BIMI Record Validator, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use BIMI Record Validator from a browser?
What happens if I exceed my BIMI Record Validator credit limit?
When you reach your monthly credit limit, BIMI Record Validator API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








