SDKs & Client Libraries
Use ResolveDB from standard DNS and HTTP clients while official SDKs are prepared for release.
No SDK Required
ResolveDB uses DNS, DoH, DoT, and a JSON DNS endpoint. Any language with a DNS or HTTP client can query it directly.
dig TXT get.quebec.weather.public.v1.resolvedb.net +shortconst name = 'get.quebec.weather.public.v1.resolvedb.net';
const response = await fetch(
`https://doh.resolvedb.io/resolve?name=${encodeURIComponent(name)}&type=TXT`,
);
const dns = await response.json();See the DoH JSON guide for correct TXT character-string joining and UQRP payload decoding.
Official SDK Status
Current official clients are not yet published. Do not install packages that
claim to be the current ResolveDB SDK unless a release is linked from this page.
The older public Go v0.1.0 client predates the production protocol and is not
compatible with the current service.
Planned SDKs will provide typed public-service queries, private query-token support, transport selection, redaction, and response parsing. Publication is a separate release gate.
ResolveDB does not currently provide hosted blob fallback, DNS write operations, or automatic large-record chunk reassembly. Hosted record writes use the REST API, and each decoded record payload is limited to 2,586 bytes.
Write Hosted Records
Use the customer REST API or dashboard. The REST data field is strict Base64;
the 2,586-byte limit applies after decoding.
curl -X POST https://api.resolvedb.com/api/v1/records \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"record": {
"key": "config.your-namespace.v1",
"data": "eyJoZWxsbyI6IndvcmxkIn0="
}
}'Private DNS reads require a namespace query token as described in the Quickstart.
Stay Updated
Create an account or return to this page for release links.