For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
LoginSandbox
Platform GuidesAPI DocsSDKMCP ServerChangelog
Platform GuidesAPI DocsSDKMCP ServerChangelog
  • Getting started
    • Introduction
    • Concepts
    • Onboarding guide
  • Use cases
    • Monetizing an AI agent
    • Pricing models for AI products
    • Configuring entitlements for AI products
  • Usage metering & events
    • Meters
    • Usage events
    • Unmatched events
    • Event reprocessing
  • Products & plans
    • Product Catalog
    • Pricing Plans
    • Features & Entitlements
  • Wallets & credits
    • Credit types & wallets
    • Credits in pricing plans
  • Customers & subscriptions
    • Customers
    • Subscriptions
    • Quotes
  • Invoicing
    • Invoices
    • Invoice corrections
    • Payment Collections
    • Tax
    • Currencies & Exchange rates
    • E-invoicing
  • Analytics & reporting
    • Insights
    • Report downloads
    • Revenue Recognition & Deferred Revenue
  • Integrations
    • CRM
    • ERP
    • Email Providers
    • Data Imports: Event File Uploads
    • Data Exports
    • Payment Service Providers
  • Settings & admin
    • Billing entities
    • Payment Options
    • User management
    • Customising invoices
    • Custom fields
    • Default platform settings
    • API key creation
    • Alert Rules
    • Workflows
  • Workflows
    • Workflow Triggers
    • Workflow Actions
    • Monitoring and Audit
    • Common Use Cases
  • For developers
    • Introduction
    • Authentication
    • Local development setup
    • API
    • Errors
    • Troubleshooting
    • Query Parameters
    • Expanding Responses
    • Idempotency
    • Timestamp formatting
    • Webhooks
    • Locale
    • MCP Server
LoginSandbox
On this page
  • Overview
  • What is ISO 8601?
  • ISO 8601 Date-Time Format
  • Usage in Our API
  • Why Use ISO 8601?
  • Handling Time Zones
  • Conclusion
For developers

Timestamp formatting

Was this page helpful?
Previous

Webhooks

Next
Built with

Overview

When ingesting events into our system, it is crucial to ensure that timestamps are formatted correctly to maintain consistency and facilitate accurate processing. Our system requires all timestamps to be in the ISO 8601 date-time format.

What is ISO 8601?

ISO 8601 is an international standard for date and time representations issued by the International Organization for Standardization (ISO). This standard aims to eliminate the risk of misinterpretation of numeric dates and times due to different conventions worldwide.

ISO 8601 Date-Time Format

Our system supports the following ISO 8601 date-time formats:

  • Date and Time with Time Zone: YYYY-MM-DDThh:mm:ss±hh:mm
    • Example: 2024-05-17T11:27:00+02:00 (Local time with offset)
  • Date and Time in UTC: YYYY-MM-DDThh:mm:ssZ
    • Example: 2024-05-15T08:56:00Z (UTC time)

Usage in Our API

When sending events to our API, ensure that the timestamp field is in one of the above formats. For example when ingesting an event:

1{
2  "meter_reference": "some_meter",
3  "customer_reference": "some_customer",
4  "timestamp": "2024-05-09T17:06:00+02:00"
5}

Why Use ISO 8601?

Using ISO 8601 ensures that timestamps are unambiguous and easily parseable by systems worldwide. It prevents confusion that may arise from different date and time conventions and improves interoperability between different systems and services.

Handling Time Zones

It is essential to include time zone information to accurately represent the time of the event. Using Z denotes UTC time, while offsets like +02:00 specify the time zone relative to UTC.

Conclusion

Adhering to the ISO 8601 format for timestamps helps maintain data integrity and ensures that events are processed accurately. If you have any questions or need further assistance, please contact our support team.