Mayan CalendarMayan Calendar API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 231ms|p50: 219ms|p75: 239ms|p90: 264ms|p99: 314ms

Overview

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

GET Endpoint

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

Example

How to call the Mayan Calendar API in different programming languages.

cURL Request
curl -X GET \
  "https://api.apiverve.com/v1/mayancalendar?date=2024-12-21" \
  -H "X-API-Key: your_api_key_here"
JavaScript (Fetch API)
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);
Python (Requests)
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)
Go (net/http)
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))
}
Example 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
  }
}

Authentication

The Mayan Calendar 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 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

ParameterTypeRequiredDescriptionDefaultExample
datestringrequired
The Gregorian date in YYYY-MM-DD format
Format: date (e.g., 2024-12-21)
-2024-12-21

Response

The Mayan Calendar 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 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>
    <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>
YAML Response
200 OK
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
CSV Response
200 OK
keyvalue
gregorian2024-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}
calendarRound6 Akbal 6 Kankin
daysSinceEpoch1876383

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
gregorianstring"2024-12-21"
The input Gregorian date in YYYY-MM-DD format
longCountobject{...}
-
â”” formattedstring"13.0.12.3.3"
Mayan Long Count formatted as baktun.katun.tun.winal.kin
â”” baktunPremiumnumber13
Long Count baktun component (cycle of 400 tuns)
â”” katunPremiumnumber0
Long Count katun component (cycle of 20 tuns)
â”” tunPremiumnumber12
Long Count tun component (cycle of 18 winals)
â”” winalPremiumnumber3
Long Count winal component (cycle of 20 kins)
â”” kinPremiumnumber3
Long Count kin component (day unit in Mayan calendar)
tzolkinobject{...}
-
â”” numberPremiumnumber6
Tzolkin sacred calendar day number (1-13)
â”” dayNamePremiumstring"Akbal"
Tzolkin day name from 20-day Mayan sacred cycle
â”” formattedstring"6 Akbal"
Tzolkin date formatted as number and day name
haabobject{...}
-
â”” dayPremiumnumber6
Haab civil calendar day number (0-19 or 0-4)
â”” monthNamePremiumstring"Kankin"
Haab month name from 18-month Mayan civil calendar
â”” formattedstring"6 Kankin"
Haab date formatted as day and month name
calendarRoundPremiumstring"6 Akbal 6 Kankin"
Calendar Round combining Tzolkin and Haab dates
daysSinceEpochPremiumnumber1876383
Days since Mayan creation date (0.0.0.0.0)

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 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.

Test Mayan Calendar 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 {
  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 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

Mayan Calendar 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 Mayan Calendar 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 Mayan Calendar

Official Mayan Calendar packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

No-Code Integrations

Mayan Calendar 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 Mayan Calendar?
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 Mayan Calendar and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
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?
Yes! The Mayan Calendar 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 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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?