Rafael Felipe
05/21/2026, 8:38 PMkapa.ai
05/21/2026, 8:38 PMSession Token Path field is designed to navigate a JSON response body using an array of keys. For example:
• Response {"id": "my-token"} → Session Token Path: id
• Response {"result": {"token": "my-token"}} → Session Token Path: result, token
[Session Token Config]
If your API returns the token as a plain text body (e.g., just abc123 with no JSON wrapping), this is a case the knowledge sources don't cover directly. The SessionTokenAuthenticator documentation states:
> "The response body is expected to be a JSON object with a session token property."
[YAML Reference]
Suggestions:
1. Check if the response is actually JSON — sometimes APIs return a plain string that is still valid JSON (e.g., "abc123" with quotes). In that case, you may be able to leave the Session Token Path empty or try a single empty path entry.
2. Reach out to the Airbyte community — if the response is truly a raw plain-text body with no key, this may be a current limitation. You can report it on GitHub or ask in the Airbyte Slack for guidance on workarounds.
I'd recommend verifying the exact raw response format (e.g., using a tool like Postman) to confirm whether it's truly keyless plain text or a JSON string. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.Rafael Felipe
05/21/2026, 8:41 PMkapa.ai
05/21/2026, 8:42 PM"abc123") with no key.
However, based on how the Session Token Path works — it forms a path into a JSON object to locate the token value — if your response is just a quoted string like:
"abc123"
There is no key to navigate to. The SessionTokenAuthenticator expects a JSON object with a property, like:
{
"token": "abc123"
}
[YAML Reference]
Since the Session Token Path field is required and your response has no key, I'd suggest:
1. Double-check the raw API response — make sure it's truly just a quoted string and not a JSON object. Sometimes responses look like plain text but are actually {"token": "abc123"} or similar.
2. Contact the Airbyte community — this edge case (plain JSON string response) may not be supported today. You can ask in the Airbyte Slack or open an issue on GitHub for guidance or a potential workaround.
I'm sorry I can't provide a more definitive answer — the knowledge sources don't contain enough information to confirm a working solution for this specific scenario. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.