How does authentication work / why am I getting a 401
Auth flow and common causes of authentication errors, answered directly from your documented API reference.
AI chatbot for API and developer support
AI chatbot for API and developer support
Developers ask precise, technical questions — endpoint behaviour, auth, rate limits — and expect exact answers from your actual docs, not a marketing tone. GoBrise answers those from your documentation, and hands account-specific or environment-specific issues to a person.
- Developers want exact, documented answers — not a friendly paraphrase
- The same auth, endpoint, and rate-limit questions repeat across every integrator
- A genuine bug or account-specific technical issue needs an engineer, not a guess
- Developers often work outside your support team's time zone
Last reviewed 20 September 2026
Quick summary
Procedural
Endpoint behaviour, auth flow, rate limits, and error-code meanings — answered directly from your API documentation.
Escalate
Anything that looks like an actual bug, or a problem specific to one account's environment, goes to a person.
$0
Unlimited human live chat on the Free plan while you evaluate AI for developer support.
24/7
Developers integrating outside your staffed hours get accurate, documented answers instantly.
What people actually ask
Real questions this page answers, drawn from the conversations teams like yours handle every day.
What are the rate limits and what happens if I hit them
Exact documented limits and behaviour on exceeding them — a precise, factual question developers expect an exact answer to.
What does this specific error code mean
Documented error codes and their meanings, answered consistently rather than requiring a support ticket for something already written down.
Does the API support X / what's the request format for Y
Endpoint capabilities and exact request/response formats, quoted from your current API reference rather than an outdated example.
My integration isn't working the way the docs describe
If this looks like a genuine bug or environment-specific issue, it's escalated to an engineer rather than met with a generic troubleshooting script.
How it works
Step 1
Feed it your actual API reference, not marketing docs
Developers need the precise, versioned reference documentation — endpoints, parameters, error codes — not a simplified product description.
Step 2
Write the auth and rate-limit boundary explicitly
These generate the highest volume of developer support tickets. Document exact behaviour, including edge cases, precisely.
Step 3
Separate documented behaviour from real bugs
Decide clearly what counts as "answerable from docs" versus "needs an engineer to actually investigate" — and route accordingly.
Step 4
Install the widget in developer docs and the dashboard
Developers ask questions while reading docs or debugging in your dashboard — not typically on the marketing homepage.
Step 5
Test with real developer wording, including terse ones
Developers often ask short, technical, sometimes curt questions. Confirm the assistant answers precisely and escalates genuine bugs without a generic reply.
Step 6
Review after every API version change
Outdated endpoint or parameter documentation produces confidently wrong technical answers — update immediately after any API change.
Who this is — and isn't — for
An honest read on where GoBrise fits, so you can rule it out quickly if it doesn't.
A good fit if
- Your API documentation is precise, current, and versioned
- Most developer questions are genuinely answerable from documented behaviour: auth, endpoints, limits, error codes
- You want anything resembling a real bug to reach an engineer immediately
- Developers integrate across time zones outside your staffed support hours
- You value exact, documented answers over a friendlier but less precise tone
Not the right tool if
- Your API documentation is incomplete, outdated, or inconsistent with actual behaviour
- Most developer tickets are already genuine bugs needing engineering investigation
- Your API changes frequently enough that docs can't realistically stay current
- You need the assistant to debug a specific integration's actual code or environment
- You have no engineering escalation path for genuine technical issues
Frequently asked questions
Can it debug my specific integration?
No — it answers from your documented API behaviour. Anything that looks like an actual bug or environment-specific issue is escalated to an engineer.
Will it give exact, documented answers rather than a vague paraphrase?
It answers strictly from the API reference content you provide, so precision depends on how precisely your docs are written — vague docs produce vague answers.
Can it explain a specific error code we return?
Yes, if your error codes and their meanings are documented — this is exactly the kind of repetitive, precise question it handles well.
How do we keep it accurate across API versions?
Update the ingested documentation immediately after any API or endpoint change — stale docs are the main source of confidently wrong technical answers.
Does it replace our engineering support team?
No — it absorbs the repeatable documented questions; genuine bugs and account-specific technical issues still need an engineer.
Can it be embedded directly in our developer docs site?
Yes, the widget can be installed on your docs site and dashboard, not just the marketing homepage.
Is it white-labelled for our developer portal?
Yes, on Growth and Business plans the widget carries your own branding, no GoBrise mark.
How much documentation do we need before launch?
Start with your core authentication, rate-limit, and most-used endpoint documentation, then expand based on what still escalates.
How should we test it before rolling out to developers?
Load your real API reference and run actual past developer support tickets through it, confirming documented questions answer precisely and real bugs escalate cleanly.
Try it on your own content
Start free with unlimited human live chat, add your content, and judge the answers for yourself.