Due Date Calculator API
Due Date Calculator estimates pregnancy due dates using either last menstrual period or conception date, providing comprehensive pregnancy timeline information.
The Due Date Calculator API provides reliable and fast access to due date calculator data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use Due Date Calculator, 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/duedatecalculatorCode Examples
Here are examples of how to call the Due Date Calculator API in different programming languages:
curl -X GET \
"https://api.apiverve.com/v1/duedatecalculator?last_period=2025-06-01" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/duedatecalculator?last_period=2025-06-01', {
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/duedatecalculator?last_period=2025-06-01', headers=headers)
data = response.json()
print(data)const https = require('https');
const url = require('url');
const options = {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
};
const req = https.request('https://api.apiverve.com/v1/duedatecalculator?last_period=2025-06-01', options, (res) => {
let data = '';
res.on('data', (chunk) => data += chunk);
res.on('end', () => console.log(JSON.parse(data)));
});
req.end();<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/duedatecalculator?last_period=2025-06-01');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
'X-API-Key: your_api_key_here',
'Content-Type: application/json'
]);
$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
?>package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/duedatecalculator?last_period=2025-06-01", 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))
}require 'net/http'
require 'json'
uri = URI('https://api.apiverve.com/v1/duedatecalculator?last_period=2025-06-01')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'
response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))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 response = await client.GetAsync("https://api.apiverve.com/v1/duedatecalculator?last_period=2025-06-01");
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The Due Date Calculator 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 Due Date Calculator API directly in your browser with live requests and responses.
Parameters
The Due Date Calculator API supports multiple query options. Use one of the following:
Option 1: Calculate from Last Period
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
last_period | string | required | First day of last menstrual period (YYYY-MM-DD) Format: date (e.g., 2025-06-01) | - |
Option 2: Calculate from Conception Date
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
conception_date | string | required | Conception date (YYYY-MM-DD) | - |
Response
The Due Date Calculator API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"status": "ok",
"error": null,
"data": {
"calculation_method": "last_period",
"last_period_date": "2024-01-01",
"estimated_conception_date": "2024-01-15",
"due_date": "2024-10-07",
"current_progress": {
"days_pregnant": 715,
"weeks_pregnant": 102,
"days_into_week": 1,
"formatted": "102 weeks, 1 days",
"trimester": 3,
"percentage_complete": 255.36
},
"time_until_due": {
"days": 0,
"weeks": 0,
"days_extra": 0,
"formatted": "Past due date",
"is_overdue": true
},
"upcoming_milestones": [],
"important_dates": {
"end_first_trimester": "2024-04-01",
"end_second_trimester": "2024-07-08",
"full_term_begins": "2024-09-16"
},
"disclaimer": "This is an estimate only. Due dates can vary. Consult your healthcare provider for medical advice."
}
}<?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>
<calculation_method>last_period</calculation_method>
<last_period_date>2024-01-01</last_period_date>
<estimated_conception_date>2024-01-15</estimated_conception_date>
<due_date>2024-10-07</due_date>
<current_progress>
<days_pregnant>715</days_pregnant>
<weeks_pregnant>102</weeks_pregnant>
<days_into_week>1</days_into_week>
<formatted>102 weeks, 1 days</formatted>
<trimester>3</trimester>
<percentage_complete>255.36</percentage_complete>
</current_progress>
<time_until_due>
<days>0</days>
<weeks>0</weeks>
<days_extra>0</days_extra>
<formatted>Past due date</formatted>
<is_overdue>true</is_overdue>
</time_until_due>
<upcoming_milestones>
</upcoming_milestones>
<important_dates>
<end_first_trimester>2024-04-01</end_first_trimester>
<end_second_trimester>2024-07-08</end_second_trimester>
<full_term_begins>2024-09-16</full_term_begins>
</important_dates>
<disclaimer>This is an estimate only. Due dates can vary. Consult your healthcare provider for medical advice.</disclaimer>
</data>
</response>
status: ok
error: null
data:
calculation_method: last_period
last_period_date: '2024-01-01'
estimated_conception_date: '2024-01-15'
due_date: '2024-10-07'
current_progress:
days_pregnant: 715
weeks_pregnant: 102
days_into_week: 1
formatted: 102 weeks, 1 days
trimester: 3
percentage_complete: 255.36
time_until_due:
days: 0
weeks: 0
days_extra: 0
formatted: Past due date
is_overdue: true
upcoming_milestones: []
important_dates:
end_first_trimester: '2024-04-01'
end_second_trimester: '2024-07-08'
full_term_begins: '2024-09-16'
disclaimer: >-
This is an estimate only. Due dates can vary. Consult your healthcare
provider for medical advice.
| key | value |
|---|---|
| calculation_method | last_period |
| last_period_date | 2024-01-01 |
| estimated_conception_date | 2024-01-15 |
| due_date | 2024-10-07 |
| current_progress | {days_pregnant:715,weeks_pregnant:102,days_into_week:1,formatted:102 weeks, 1 days,trimester:3,percentage_complete:255.36} |
| time_until_due | {days:0,weeks:0,days_extra:0,formatted:Past due date,is_overdue:true} |
| upcoming_milestones | [] |
| important_dates | {end_first_trimester:2024-04-01,end_second_trimester:2024-07-08,full_term_begins:2024-09-16} |
| disclaimer | This is an estimate only. Due dates can vary. Consult your healthcare provider for medical advice. |
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 |
|---|---|---|---|
calculation_method | string | - | |
last_period_date | string | - | |
estimated_conception_date | string | - | |
due_date | string | - | |
current_progress | object | - | |
â”” days_pregnant | number | - | |
â”” weeks_pregnant | number | - | |
â”” days_into_week | number | - | |
â”” formatted | string | - | |
â”” trimester | number | - | |
â”” percentage_complete | number | - | |
time_until_due | object | - | |
â”” days | number | - | |
â”” weeks | number | - | |
â”” days_extra | number | - | |
â”” formatted | string | - | |
â”” is_overdue | boolean | - | |
upcoming_milestones | array | - | |
important_dates | object | - | |
â”” end_first_trimester | string | - |
Headers
Required and optional headers for Due Date Calculator API requests:
| Header Name | Required | Example Value | Description |
|---|---|---|---|
X-API-Key | required | your_api_key_here | Your APIVerve API key. Found in your dashboard under API Keys. |
Accept | optional | application/json | Specify response format: application/json (default), application/xml, or application/yaml |
User-Agent | optional | MyApp/1.0 | Identifies your application for analytics and debugging purposes |
X-Request-ID | optional | req_123456789 | Custom request identifier for tracking and debugging requests |
Cache-Control | optional | no-cache | Control caching behavior for the request and response |
GraphQL AccessALPHA
Access Due Date Calculator through GraphQL to combine it with other API calls in a single request. Query only the due date calculator 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 {
duedatecalculator(
input: {
last_period: "2025-06-01"
}
) {
calculation_method
last_period_date
estimated_conception_date
due_date
current_progress {
days_pregnant
weeks_pregnant
days_into_week
formatted
trimester
percentage_complete
}
time_until_due {
days
weeks
days_extra
formatted
is_overdue
}
upcoming_milestones
important_dates {
end_first_trimester
end_second_trimester
full_term_begins
}
disclaimer
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Due Date Calculator API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Due Date Calculator directly from browser-based applications without proxy servers.
| CORS Header | Value | Description |
|---|---|---|
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 Due Date Calculator directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
Due Date Calculator API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Due Date Calculator users.
| Plan | Rate Limit | Description |
|---|---|---|
| Free | 5 requests/min | Hard rate limit enforced - exceeding will return 429 errors |
| Starter | No Limit | Production ready - standard traffic priority |
| Pro | No Limit | Production ready - preferred traffic priority |
| Mega | No Limit | Production ready - highest traffic priority |
Learn more about rate limiting →
Rate Limit Headers
When rate limits apply, each Due Date Calculator response includes headers to help you track your usage:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed per time window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets |
Handling Rate Limits
Free Plan: When you exceed your rate limit, Due Date Calculator 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 Due Date Calculator:
- Monitor the rate limit headers to track your Due Date Calculator usage (Free plan only)
- Cache due date calculator responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle Due Date Calculator performance
Note: Due Date Calculator rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Due Date Calculator on Free tier.
Error Codes
The Due Date Calculator API uses standard HTTP status codes to indicate success or failure:
| Code | Message | Description | Solution |
|---|---|---|---|
200 | OK | Request successful, data returned | No action needed - request was successful |
400 | Bad Request | Invalid request parameters or malformed request | Check required parameters and ensure values match expected formats |
401 | Unauthorized | Missing or invalid API key | Include x-api-key header with valid API key from dashboard |
403 | Forbidden | API key lacks permission or insufficient credits | Check credit balance in dashboard or upgrade plan |
429 | Too Many Requests | Rate limit exceeded (Free: 5 req/min) | Implement request throttling or upgrade to paid plan |
500 | Internal Server Error | Server error occurred | Retry request after a few seconds, contact support if persists |
503 | Service Unavailable | API temporarily unavailable | Wait 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 Due Date Calculator with SDKs
Get started quickly with official Due Date Calculator 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 Due Date Calculator with No-Code API Tools
Connect the Due Date Calculator API to your favorite automation platform without writing code. Build workflows that leverage due date calculator data across thousands of apps.





All platforms use your same API key to access Due Date Calculator. Visit our integrations hub for step-by-step setup guides.
Frequently Asked Questions
How do I get an API key for Due Date Calculator?
How many credits does Due Date Calculator cost?
Each successful Due Date Calculator 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 due date calculator lookups.
Can I use Due Date Calculator in production?
The free plan is for testing and development only. For production use of Due Date Calculator, 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 Due Date Calculator from a browser?
What happens if I exceed my Due Date Calculator credit limit?
When you reach your monthly credit limit, Due Date Calculator 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.



