Libraries tagged by gremo

PHP library to convert Gregorian date to Hijri date and vice versa

Go to Download

a php script to convert date between persian jalili date and gregorian date time

Go to Download

Converts Gregorian date to Bikram Samvat date and vice versa.

Go to Download

GeezDate is a lightweight and efficient Laravel package that seamlessly converts standard Gregorian dates into the traditional Ethiopian (Geez) calendar format.

Go to Download

jalali date for all purpose and codeigniter library to convert gregorian date to jalali date and reverse (jalali date to gregorian date)

Go to Download

Tempus handles Gregorian calendar

Go to Download

A library to convert between Middle Eastern calendars including Hijri, Gregorian, Persian, Hebrew

Go to Download

Laravel package to convert Gregorian dates to Hijri dates

Go to Download

Convert Jalali Date to Gregorian and vice versa

Go to Download

A full dates that support all dates such gregorian, iranian, kurdish, hebrew, ... .

Go to Download

The Gregorian calendar to Lunar calendar

Go to Download

Library to convert between Gregorian and Badi calendars.

Go to Download

Converts from Gregorian date to Chinese lunisolar date and vice versa.

Go to Download

Craft plugin convert Gregorian date to Hijri date and vice versa.

Go to Download

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download