SRV Record ParserSRV Record Parser API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 241ms|p50: 228ms|p75: 250ms|p90: 276ms|p99: 328ms

SRV Record Parser analyzes DNS SRV records and extracts service location information including priority, weight, port, and target server details.

The SRV Record Parser API provides reliable and fast access to srv record parser data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.

To use SRV Record Parser, you need an API key. You can get one by creating a free account and visiting your dashboard.

POST Endpoint

URL
https://api.apiverve.com/v1/srvparser

Code Examples

Here are examples of how to call the SRV Record Parser API in different programming languages:

cURL Request
curl -X POST \
  "https://api.apiverve.com/v1/srvparser" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."
}'
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/srvparser', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."
})
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

payload = {
    "record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."
}

response = requests.post('https://api.apiverve.com/v1/srvparser', headers=headers, json=payload)

data = response.json()
print(data)
Node.js (Native HTTPS)
const https = require('https');
const url = require('url');

const options = {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
};

const postData = JSON.stringify({
  "record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."
});

const req = https.request('https://api.apiverve.com/v1/srvparser', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.write(postData);
req.end();
PHP (cURL)
<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/srvparser');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here',
    'Content-Type: application/json'
]);

curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode({
    'record': '_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com.'
}));

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($data);

?>
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    payload := map[string]interface{}{
        "record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/srvparser", bytes.NewBuffer(jsonPayload))

    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))
}
Ruby (Net::HTTP)
require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/srvparser')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

payload = {
  "record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."
}

request = Net::HTTP::Post.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'

request.body = payload.to_json

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))
C# (HttpClient)
using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;

class Program
{
    static async Task Main(string[] args)
    {
        using var client = new HttpClient();
        client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");

        var jsonContent = @"{
        ""record"": ""_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com.""
}";
        var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");

        var response = await client.PostAsync("https://api.apiverve.com/v1/srvparser", content);
        response.EnsureSuccessStatusCode();

        var responseBody = await response.Content.ReadAsStringAsync();
        Console.WriteLine(responseBody);
    }
}

Authentication

The SRV Record Parser API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the SRV Record Parser API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the SRV Record Parser API:

Parse SRV Record

ParameterTypeRequiredDescriptionDefaultExample
recordstringrequired
The SRV record string to parse
-_http._tcp.example.com. 3600 IN SRV 10 60 80 server.example.com.

Response

The SRV Record Parser API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

JSON Response
200 OK
{
  "status": "ok",
  "error": null,
  "data": {
    "raw_record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com.",
    "parsed": {
      "name": "_http._tcp.example.com.",
      "service": "_http",
      "protocol": "tcp",
      "domain": "example.com.",
      "ttl": 86400,
      "class": "IN",
      "priority": 10,
      "weight": 60,
      "port": 80,
      "target": "server.example.com"
    },
    "service_info": {
      "name": "HTTP",
      "description": "Web service",
      "default_port": 80
    },
    "interpretation": {
      "priority_explanation": "Priority level 10 (lower is better)",
      "weight_explanation": "Weight 60 for load balancing",
      "target_explanation": "Connect to server.example.com:80"
    },
    "is_valid": true
  }
}
XML Response
200 OK
<?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>
    <raw_record>_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com.</raw_record>
    <parsed>
      <name>_http._tcp.example.com.</name>
      <service>_http</service>
      <protocol>tcp</protocol>
      <domain>example.com.</domain>
      <ttl>86400</ttl>
      <class>IN</class>
      <priority>10</priority>
      <weight>60</weight>
      <port>80</port>
      <target>server.example.com</target>
    </parsed>
    <service_info>
      <name>HTTP</name>
      <description>Web service</description>
      <default_port>80</default_port>
    </service_info>
    <interpretation>
      <priority_explanation>Priority level 10 (lower is better)</priority_explanation>
      <weight_explanation>Weight 60 for load balancing</weight_explanation>
      <target_explanation>Connect to server.example.com:80</target_explanation>
    </interpretation>
    <is_valid>true</is_valid>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  raw_record: _http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com.
  parsed:
    name: _http._tcp.example.com.
    service: _http
    protocol: tcp
    domain: example.com.
    ttl: 86400
    class: IN
    priority: 10
    weight: 60
    port: 80
    target: server.example.com
  service_info:
    name: HTTP
    description: Web service
    default_port: 80
  interpretation:
    priority_explanation: Priority level 10 (lower is better)
    weight_explanation: Weight 60 for load balancing
    target_explanation: Connect to server.example.com:80
  is_valid: true
CSV Response
200 OK
keyvalue
raw_record_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com.
parsed{name:_http._tcp.example.com.,service:_http,protocol:tcp,domain:example.com.,ttl:86400,class:IN,priority:10,weight:60,port:80,target:server.example.com}
service_info{name:HTTP,description:Web service,default_port:80}
interpretation{priority_explanation:Priority level 10 (lower is better),weight_explanation:Weight 60 for load balancing,target_explanation:Connect to server.example.com:80}
is_validtrue

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains 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:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
raw_recordstring"_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."Original SRV record string provided for parsing
parsedobject{...}-
â”” namestring"_http._tcp.example.com."Full SRV record name with trailing dot
â”” servicestring"_http"Service identifier (e.g., _http, _xmpp, _sip)
â”” protocolstring"tcp"Protocol type (e.g., tcp, udp, tls)
â”” domainstring"example.com."Domain name with trailing dot
â”” ttlnumber86400Time-to-live value in seconds
â”” classstring"IN"DNS class (typically IN for Internet)
â”” priorityPremiumnumber10Priority value (lower values preferred)
â”” weightPremiumnumber60Weight for load balancing among same priority
â”” portPremiumnumber80Port number for service connection
â”” targetPremiumstring"server.example.com"Target hostname without trailing dot
service_infoPremiumobject{...}Information about the recognized service type
â”” namestring"HTTP"Human-readable service name (e.g., HTTP, XMPP)
â”” descriptionstring"Web service"Service description and use case
â”” default_portnumber80Default port for identified service
interpretationPremiumobject{...}Human-readable interpretation of SRV record values
â”” priority_explanationstring"Priority level 10 (lower is better)"Human-readable explanation of priority level
â”” weight_explanationstring"Weight 60 for load balancing"Human-readable explanation of weight value
â”” target_explanationstring"Connect to server.example.com:80"How to connect to target with port

Headers

Required and optional headers for SRV Record Parser API requests:

Header NameRequiredExample ValueDescription
X-API-Keyrequiredyour_api_key_hereYour APIVerve API key. Found in your dashboard under API Keys.
Acceptoptionalapplication/jsonSpecify response format: application/json (default), application/xml, or application/yaml
User-AgentoptionalMyApp/1.0Identifies your application for analytics and debugging purposes
X-Request-IDoptionalreq_123456789Custom request identifier for tracking and debugging requests
Cache-Controloptionalno-cacheControl caching behavior for the request and response

Learn more about request headers →

GraphQL AccessALPHA

Access SRV Record Parser through GraphQL to combine it with other API calls in a single request. Query only the srv record parser data you need with precise field selection, and orchestrate complex data fetching workflows.

Test SRV Record Parser in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  srvparser(
    input: {
      record: "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."
    }
  ) {
    raw_record
    parsed {
      name
      service
      protocol
      domain
      ttl
      class
      priority
      weight
      port
      target
    }
    service_info {
      name
      description
      default_port
    }
    interpretation {
      priority_explanation
      weight_explanation
      target_explanation
    }
    is_valid
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The SRV Record Parser API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call SRV Record Parser directly from browser-based applications without proxy servers.

CORS HeaderValueDescription
Access-Control-Allow-Origin*Accepts requests from any origin
Access-Control-Allow-Methods*Accepts any HTTP method
Access-Control-Allow-Headers*Accepts any request headers

Browser Usage: You can call SRV Record Parser directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.

Learn more about CORS support →

Rate Limiting

SRV Record Parser API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all SRV Record Parser users.

PlanRate LimitDescription
Free5 requests/minHard rate limit enforced - exceeding will return 429 errors
StarterNo LimitProduction ready - standard traffic priority
ProNo LimitProduction ready - preferred traffic priority
MegaNo LimitProduction ready - highest traffic priority

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each SRV Record Parser response includes headers to help you track your usage:

HeaderDescription
X-RateLimit-LimitMaximum number of requests allowed per time window
X-RateLimit-RemainingNumber of requests remaining in the current window
X-RateLimit-ResetUnix timestamp when the rate limit window resets

Handling Rate Limits

Free Plan: When you exceed your rate limit, SRV Record Parser returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.

Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.

Best Practices for SRV Record Parser:

  • Monitor the rate limit headers to track your SRV Record Parser usage (Free plan only)
  • Cache srv record parser responses where appropriate to reduce API calls
  • Upgrade to Pro or Mega for guaranteed no-throttle SRV Record Parser performance

Note: SRV Record Parser rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using SRV Record Parser on Free tier.

Error Codes

The SRV Record Parser API uses standard HTTP status codes to indicate success or failure:

CodeMessageDescriptionSolution
200OKRequest successful, data returnedNo action needed - request was successful
400Bad RequestInvalid request parameters or malformed requestCheck required parameters and ensure values match expected formats
401UnauthorizedMissing or invalid API keyInclude x-api-key header with valid API key from dashboard
403ForbiddenAPI key lacks permission or insufficient creditsCheck credit balance in dashboard or upgrade plan
429Too Many RequestsRate limit exceeded (Free: 5 req/min)Implement request throttling or upgrade to paid plan
500Internal Server ErrorServer error occurredRetry request after a few seconds, contact support if persists
503Service UnavailableAPI temporarily unavailableWait and retry, check status page for maintenance updates

Learn more about error handling →

Need help? Contact support with your X-Request-ID for assistance.

Integrate SRV Record Parser with SDKs

Get started quickly with official SRV Record Parser SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.

Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.

Integrate SRV Record Parser with No-Code API Tools

Connect the SRV Record Parser API to your favorite automation platform without writing code. Build workflows that leverage srv record parser data across thousands of apps.

All platforms use your same API key to access SRV Record Parser. Visit our integrations hub for step-by-step setup guides.

Frequently Asked Questions

How do I get an API key for SRV Record Parser?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for SRV Record Parser and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does SRV Record Parser cost?

Each successful SRV Record Parser 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 srv record parser lookups.

Can I use SRV Record Parser in production?

The free plan is for testing and development only. For production use of SRV Record Parser, 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 SRV Record Parser from a browser?
Yes! The SRV Record Parser API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my SRV Record Parser credit limit?

When you reach your monthly credit limit, SRV Record Parser 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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?