API v3.2 Released - Migration Guide & Breaking Changes Discussion

Hey devs — API v3.2 dropped last Tuesday. I spent the weekend migrating our integration and wanted to share notes in case it helps others.

What’s new (good stuff)

• GraphQL endpoint now available at /graphql
  Huge win—less over-fetching and fewer round trips.
• Improved webhook retry logic
  Retries 5x with exponential backoff (instead of failing immediately).
• New POST /batch endpoint
  Up to 100 operations in a single request.
• More accurate rate limit headers
  X-RateLimit-Remaining and X-RateLimit-Reset finally seem to reflect reality.

Breaking changes (watch out)

• /users response format changed
  created_at is now ISO 8601 (was Unix timestamp before).
• Pagination default changed
  Default page size is now 50 (was 100).
• Auth token changes / deprecation
  Legacy API keys stop working March 1st — OAuth 2.0 required.

Issues I’m seeing (anyone else?)

• Sporadic RATE_LIMIT_EXCEEDED even though we’re well under our 10k/hour quota.
  I opened a support ticket—curious if others are seeing this too.
• GraphQL introspection appears disabled in production
  Is this intentional/expected?

Migration effort

This took about 6 hours for a moderately complex integration (~50k daily syncs). Happy to answer questions—drop your experiences below.

— Ping Z., Staff Engineer @ DataSync Inc