Last updated · May 2026
- Production-ready APIs
- SOC 2 Type I - In Progress
INVALID_OAUTH_STATE
HTTP 400 with next_step=retry. Your OAuth callback came back with a state token that doesn't match what we issued.
What it means
DataVibe's OAuth start endpoint stores a single-use state token in Redis with a 10-minute TTL and binds it to your workspace. If the callback's state expired, was reused, or came from a different workspace, we reject the exchange to prevent CSRF.
How to fix
- Restart the connector flow from the dashboard. Don't reuse a bookmarked callback URL.
- Complete the OAuth consent within 10 minutes of clicking Connect.
- If you switched workspaces mid-flow, sign back into the original workspace and try again.