API UPDATED?

[PeteATflochat]

Hey, so it seems the AI 'ASK' side of the API has changed again, and also responses via API have gotten slightly worse since the new co-pilot launch, meaning grammar in some cases is really weird 'in places' and also now getting a lot of timeout errors and no response...

The change/update i'm experiencing is at org ASK endpoint. The response no longer contains the 'Reason' path - but it still displays in your api docs.

We also have issues Site level API AI ASK, as it always 400 error as it doesn't recognise the additional payload 'required' fields ie the Scope.

Attached is my JSON response OK, without the 'Reason' path.. :) Thank you

[taranvohra]

Hey @PeteATflochat, the reason property has always been optional in our API.

As for the grammar issues, do you have any specific examples?

[taranvohra]

We've released a fix, it ensures the markdown messages do not omit links. That should resolve the broken grammar issue.

[PeteATflochat]

We've released a fix, it ensures the markdown messages do not omit links. That should resolve the broken grammar issue.

When you say markdown messages do not omit links. How do you mean exactly sorry... As I just ran a couple of tests and the response payload contains inline links within the message. I did chat with Sam yesterday regarding response times to, which are mostly over 60 seconds, he mentioned that GPT5 was causing the delays..

As you'll see in the image attached, the link is in the chat thread.

[taranvohra]

What I meant to say was previously it was omitting the links in the markdown message which caused the impression that the overal message has grammatical issues. Our fix ensures that the markdown preserves all inline links in the message so it does not appear as grammatically broken

[taranvohra]

As for the delays, we recently made the change to GPT-5 and have been testing heavily with our prompts. Expect more fixes to come this week

[PeteATflochat]

What I meant to say was previously it was omitting the links in the markdown message which caused the impression that the overal message has grammatical issues. Our fix ensures that the markdown preserves all inline links in the message so it does not appear as grammatically broken

Understand thank you... But how the responses used to be, the UX was better. Meaning, NOW - If a user asks a question in a chat widget within a product dashboard, they click the 'hyperlink' it takes them away from the dashboard - into a new browser tab.

Whereas before, we could drop the links in to 'buttons' that opened in the chat thread to the relative support doc page.

So for instance, we create support chat both on facebook and instagram, where people can ask questions in the DM and get a response, also via the post feed, they make a comment, and the AI comments back with context from the docs.

Would it be viable to have a light-weight GitBook Ask endpoint? Just response and nested links in an array - Like Lens was.

For example, i'll leave some images below to how it 'used to work' - basically the product enables omni-channel support chat, plus data driven responses based on a user data via other SaaS product API's that sync with the GitBook AI also...