Mastodon
  • What is Mastodon?
  • Using Mastodon
    • Signing up for an account
    • Setting up your profile
    • Posting to your profile
    • Using the network features
    • Dealing with unwanted content
    • Promoting yourself and others
    • Set your preferences
    • More settings
    • Using Mastodon externally
    • Moving or leaving accounts
    • Running your own server
  • Running Mastodon
    • Preparing your machine
    • Installing from source
    • Configuring your environment
    • Configuring full-text search
    • Installing optional features
      • Object storage
      • Onion services
      • Captcha
      • Single Sign On
    • Setting up your new instance
    • Using the admin CLI
    • Upgrading to a new release
    • Backing up your server
    • Migrating to a new machine
    • Scaling up your server
    • Moderation actions
    • Troubleshooting errors
      • Database index corruption
    • Roles
  • Developing Mastodon apps
    • Getting started with the API
    • Playing with public data
    • Obtaining client app access
    • Logging in with an account
    • Libraries and implementations
  • Contributing to Mastodon
    • Technical overview
    • Setting up a dev environment
    • Code structure
    • Routes
    • Bug bounties and responsible disclosure
  • Spec compliance
    • ActivityPub
    • WebFinger
    • Security
    • Microformats
    • OAuth
    • Bearcaps
  • REST API
    • Datetime formats
    • Guidelines and best practices
    • OAuth Tokens
    • OAuth Scopes
    • Rate limits
  • API Methods
    • apps
      • oauth
      • emails
    • accounts
      • bookmarks
      • favourites
      • mutes
      • blocks
      • domain_blocks
      • filters
      • reports
      • follow_requests
      • endorsements
      • featured_tags
      • preferences
      • followed_tags
      • suggestions
      • tags
    • profile
    • statuses
      • media
      • polls
      • scheduled_statuses
    • timelines
      • conversations
      • lists
      • markers
      • streaming
    • grouped notifications
    • notifications
      • push
    • search
    • instance
      • trends
      • directory
      • custom_emojis
      • announcements
    • admin
      • accounts
      • canonical_email_blocks
      • dimensions
      • domain_allows
      • domain_blocks
      • email_domain_blocks
      • ip_blocks
      • measures
      • reports
      • retention
      • trends
    • proofs
    • oembed
  • API Entities
    • Account
    • AccountWarning
    • Admin::Account
    • Admin::CanonicalEmailBlock
    • Admin::Cohort
    • Admin::Dimension
    • Admin::DomainAllow
    • Admin::DomainBlock
    • Admin::EmailDomainBlock
    • Admin::Ip
    • Admin::IpBlock
    • Admin::Measure
    • Admin::Report
    • Announcement
    • Appeal
    • Application
    • Context
    • Conversation
    • CustomEmoji
    • DomainBlock
    • Error
    • ExtendedDescription
    • FamiliarFollowers
    • FeaturedTag
    • Filter
    • FilterKeyword
    • FilterResult
    • FilterStatus
    • IdentityProof
    • Instance
    • List
    • Marker
    • MediaAttachment
    • Notification
    • NotificationPolicy
    • NotificationRequest
    • Poll
    • Preferences
    • PreviewCard
    • PreviewCardAuthor
    • PrivacyPolicy
    • Quote
    • Reaction
    • Relationship
    • RelationshipSeveranceEvent
    • Report
    • Role
    • Rule
    • ScheduledStatus
    • Search
    • ShallowQuote
    • Status
    • StatusEdit
    • StatusSource
    • Suggestion
    • Tag
    • TermsOfService
    • Token
    • Translation
    • V1::Filter
    • V1::Instance
    • V1::NotificationPolicy
    • WebPushSubscription

Datetime formats

Datetime formats

    • Datetime
      • Interoperability
    • Date
      • Interoperability

Datetime

A “datetime” specifies an instant in time.

The string representation of a datetime uses the “Internet Date/Time Format” defined in RFC3339 section 5.6.

To summarise, that is the following mandatory components:

[YYYY]-[MM]-[DD]T[hh]:[mm]:[ss].[s][TZD]

where:

  • [YYYY] = four-digit year
  • [MM] = two-digit month (01=January, etc.)
  • [DD] = two-digit day of month (01 through 31)
  • [hh] = two digits of hour (00 through 23) (24 NOT allowed)
  • [mm] = two digits of minute (00 through 59)
  • [ss] = two digits of second (00 through 60)
  • [s] = one or more digits representing a decimal fraction of a second
  • [TZD] = time zone designator (either Z for UTC, or +[hh]:[mm] or -[hh]:[mm] to represent an offset from UTC)

For example, 1994-11-05T13:15:30.000Z (equivalent to 1994-11-05T08:15:30-05:00).

See RFC3339 section 5.6 for the complete ABNF grammar.

Interoperability

  • The date and time portions are always separated by an uppercase T (not lowercase, not a space).
  • The timezone designator Z is always uppercase, not lowercase.
  • The fractional ([s]) part of the second is represented with at least one digit and at most three digits.
  • A field may be presented as a datetime while having lower resolution. E.g., the server clamps the value to the midnight on the date in question.

Date

A “date” specifies the calendar date an activity occurred, in UTC.

The string representation of a date uses the complete, extended calendar date representation from ISO 8601, the International Standard for the representation of dates and times (section 5.2.1.1). This is also the “Complete date” format from W3C Date and Time formats.

That is the following mandatory components:

[YYYY]-[MM]-[DD]
  • [YYYY] = four-digit year
  • [MM] = two-digit month (01=January, etc.)
  • [DD] = two-digit day of month (01 through 31)

Interoperability

  • The year, month, and date components are always separated by a -.

Last updated November 27, 2024 · Improve this page

Sponsored by

Dotcom-Monitor LoadView Stephen Tures Swayable SponsorMotion

Join Mastodon · Blog ·

View source · CC BY-SA 4.0 · Imprint