Mayan Calendar API
Mayan Calendar converts Gregorian dates to the ancient Mayan calendar system. Returns the Long Count, Tzolkin (260-day sacred calendar), and Haab (365-day civil calendar) dates.
The Mayan Calendar API provides reliable and fast access to mayan calendar data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.
To use Mayan Calendar, 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/mayancalendarCode Examples
Here are examples of how to call the Mayan Calendar API in different programming languages:
curl -X GET \
"https://api.apiverve.com/v1/mayancalendar?date=2024-12-21" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/mayancalendar?date=2024-12-21', {
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/mayancalendar?date=2024-12-21', 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/mayancalendar?date=2024-12-21', 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/mayancalendar?date=2024-12-21');
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/mayancalendar?date=2024-12-21", 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/mayancalendar?date=2024-12-21')
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/mayancalendar?date=2024-12-21");
response.EnsureSuccessStatusCode();
var responseBody = await response.Content.ReadAsStringAsync();
Console.WriteLine(responseBody);
}
}Authentication
The Mayan Calendar 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 Mayan Calendar API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Mayan Calendar API:
Convert to Mayan Calendar
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
date | string | required | The Gregorian date in YYYY-MM-DD format Format: date (e.g., 2024-12-21) | - |
Response
The Mayan Calendar API returns responses in JSON, XML, YAML, and CSV formats:
Example Responses
{
"status": "ok",
"error": null,
"data": {
"gregorian": "2024-12-21",
"longCount": {
"formatted": "13.0.12.3.3",
"baktun": 13,
"katun": 0,
"tun": 12,
"winal": 3,
"kin": 3
},
"tzolkin": {
"number": 6,
"dayName": "Akbal",
"formatted": "6 Akbal"
},
"haab": {
"day": 6,
"monthName": "Kankin",
"formatted": "6 Kankin"
},
"calendarRound": "6 Akbal 6 Kankin",
"daysSinceEpoch": 1876383
}
}<?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>
<gregorian>2024-12-21</gregorian>
<longCount>
<formatted>13.0.12.3.3</formatted>
<baktun>13</baktun>
<katun>0</katun>
<tun>12</tun>
<winal>3</winal>
<kin>3</kin>
</longCount>
<tzolkin>
<number>6</number>
<dayName>Akbal</dayName>
<formatted>6 Akbal</formatted>
</tzolkin>
<haab>
<day>6</day>
<monthName>Kankin</monthName>
<formatted>6 Kankin</formatted>
</haab>
<calendarRound>6 Akbal 6 Kankin</calendarRound>
<daysSinceEpoch>1876383</daysSinceEpoch>
</data>
</response>
status: ok
error: null
data:
gregorian: '2024-12-21'
longCount:
formatted: 13.0.12.3.3
baktun: 13
katun: 0
tun: 12
winal: 3
kin: 3
tzolkin:
number: 6
dayName: Akbal
formatted: 6 Akbal
haab:
day: 6
monthName: Kankin
formatted: 6 Kankin
calendarRound: 6 Akbal 6 Kankin
daysSinceEpoch: 1876383
| key | value |
|---|---|
| gregorian | 2024-12-21 |
| longCount | {formatted:13.0.12.3.3,baktun:13,katun:0,tun:12,winal:3,kin:3} |
| tzolkin | {number:6,dayName:Akbal,formatted:6 Akbal} |
| haab | {day:6,monthName:Kankin,formatted:6 Kankin} |
| calendarRound | 6 Akbal 6 Kankin |
| daysSinceEpoch | 1876383 |
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 |
|---|---|---|---|
gregorian | string | The input Gregorian date in YYYY-MM-DD format | |
longCount | object | - | |
â”” formatted | string | Mayan Long Count formatted as baktun.katun.tun.winal.kin | |
â”” baktunPremium | number | Long Count baktun component (cycle of 400 tuns) | |
â”” katunPremium | number | Long Count katun component (cycle of 20 tuns) | |
â”” tunPremium | number | Long Count tun component (cycle of 18 winals) | |
â”” winalPremium | number | Long Count winal component (cycle of 20 kins) | |
â”” kinPremium | number | Long Count kin component (day unit in Mayan calendar) | |
tzolkin | object | - | |
â”” numberPremium | number | Tzolkin sacred calendar day number (1-13) | |
â”” dayNamePremium | string | Tzolkin day name from 20-day Mayan sacred cycle | |
â”” formattedPremium | string | Tzolkin date formatted as number and day name | |
haab | object | - | |
â”” dayPremium | number | Haab civil calendar day number (0-19 or 0-4) | |
â”” monthNamePremium | string | Haab month name from 18-month Mayan civil calendar | |
â”” formattedPremium | string | Haab date formatted as day and month name | |
calendarRoundPremium | string | Calendar Round combining Tzolkin and Haab dates | |
daysSinceEpochPremium | number | Days since Mayan creation date (0.0.0.0.0) |
Headers
Required and optional headers for Mayan Calendar 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 Mayan Calendar through GraphQL to combine it with other API calls in a single request. Query only the mayan calendar 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 {
mayancalendar(
input: {
date: "2024-12-21"
}
) {
gregorian
longCount {
formatted
baktun
katun
tun
winal
kin
}
tzolkin {
number
dayName
formatted
}
haab {
day
monthName
formatted
}
calendarRound
daysSinceEpoch
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Mayan Calendar API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Mayan Calendar 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 Mayan Calendar directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.
Rate Limiting
Mayan Calendar API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Mayan Calendar 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 Mayan Calendar 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, Mayan Calendar 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 Mayan Calendar:
- Monitor the rate limit headers to track your Mayan Calendar usage (Free plan only)
- Cache mayan calendar responses where appropriate to reduce API calls
- Upgrade to Pro or Mega for guaranteed no-throttle Mayan Calendar performance
Note: Mayan Calendar rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Mayan Calendar on Free tier.
Error Codes
The Mayan Calendar 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 Mayan Calendar with SDKs
Get started quickly with official Mayan Calendar 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 Mayan Calendar with No-Code API Tools
Connect the Mayan Calendar API to your favorite automation platform without writing code. Build workflows that leverage mayan calendar data across thousands of apps.





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



