FlxpointAPI Help CenterBeta

Date Formatting

The Flxpoint API uses ISO 8601The international standard for date/time stringsA widely-supported format that puts year-month-day-T-hour-minute-second together with an explicit timezone — like 2026-04-20T15:30:00Z. Every modern language has a parser for it; using anything else (e.g. 04/20/2026) leads to ambiguity between US and European date order. for every datetime field, in both requests and responses.

Tool

Date format converter

Paste any date, get the ISO 8601 string the API expects. No server call — runs in your browser.

Enter a date or timestamp to convert.

What to send

2026-04-20T15:30:00Z        // UTC (preferred)
2026-04-20T08:30:00-07:00   // with explicit offset

Date-only fields (like effectiveDate) take YYYY-MM-DD.

What to expect in responses

Every datetime response is in UTC with a trailing Z. Parse it, don't string-compare — dates that look different can be equal. For example, 2026-04-20T15:30:00Z and 2026-04-20T08:30:00-07:00 are the same instant, but they will never be string-equal.

Common mistakes

  • Missing timezone. 2026-04-20T08:30:00with no offset is rejected. There's no "default": explicit beats clever every time.
  • Local-time assumptions.If you build a filter "orders from yesterday", yesterday in US/Eastern is not yesterday in UTC. Convert first, then send.
  • Millisecond precision.Flxpoint stores to the second. Milliseconds in requests are tolerated but dropped — your response won't echo them back.
  • Naive equality after a round-trip. Send ...-07:00, get back ...Z. Same moment, different string. Always parse and compare as instants, not text.

Filter examples

A typical date-range query for orders:

GET /orders?createdSince=2026-04-01T00:00:00Z&createdUntil=2026-04-30T23:59:59Z

For a rolling cursorA timestamp you store to remember 'last sync'Instead of re-pulling everything every run, you store the latest updatedAt from the last response and pass it as the start of your next query. The first call may pull a lot; every later call only pulls the delta. This is the standard pattern for inventory / order syncs. sync (only fetch what changed since last poll):

# Store this between runs:
LAST_SEEN="2026-04-30T15:00:00Z"

# Each poll, fetch only what changed after LAST_SEEN:
curl -G "https://api.flxpoint.com/orders" \
  -H "X-API-TOKEN: YOUR_TOKEN" \
  --data-urlencode "updatedSince=$LAST_SEEN"

# Then advance LAST_SEEN to the latest updatedAt in the response.