Tom Bartoň
11/02/2026, 3:22 PMkapa.ai
11/02/2026, 3:22 PM201 Created response confirms the write was accepted, but full propagation across nodes takes additional time. The same pattern applies to API token creation: the token exists in the system after the POST, but it may not yet be recognized by all nodes when an immediate request is made with it, resulting in a transient 403.
Your workaround (adding a short sleep after token creation) is the right approach for now. The recommended general pattern for this type of workflow is to poll with a GET until the entity returns 200 before using it downstream — a 1–2 second retry interval with a ~30 second timeout is typically more than sufficient. [User Tokens]
Regarding the docs — that's a fair point. The eventual consistency caveat for token creation isn't currently called out explicitly in the API token documentation. [User Tokens]
To help the Support team investigate and consider a docs update, please add the following details to this thread:
• The approximate time(s) the 403 was observed
• The delay (sleep duration) that resolved the issue for you
• Whether this happens consistently on first use of a new token, or intermittently on existing tokens as well
• Any trace or request IDs from the failed 403 responses
The Support team monitors this thread and will pick it up from here.
Community support (Startup & Professional): You're already in the right place — the GoodData Support team monitors this Slack and a team member will join the conversation when human review is needed. You can also visit the Community Forums for additional discussion.
24/7 Support (Enterprise plans): If your account includes 24/7 Support or this is a Severity 1 (L1) critical issue, you can also submit a ticket, email support@gooddata.com, or call +1 (415) 200-0194. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups.
👀 Our Support team monitors all messages and will jump in if needed.Tom Bartoň
11/02/2026, 3:26 PMShamil Akhmadyshev
11/02/2026, 3:36 PM