Skip to main content
Authenticates requests with a value that is first fetched by calling another endpoint. Use this when an API hands you a session token, ticket, or cookie from a login or token call, and you then have to send that value on every following request. Alumio makes the lookup call for you, reads the value out of the response (from a header, a cookie, or the body), and adds it as a header on the requests of the connection. It can also cache the value so the lookup is not repeated on every single request.

​
Fields

​
Sample data

This feature adds authentication to a live HTTP connection rather than transforming data, so there is no before/after to show. A typical configuration that logs in at /auth/login, reads a token from the response body, and sends it back as an Authorization header looks like this: With these settings, Alumio calls /auth/login, reads the token field from the response, and adds Authorization: Bearer <token> to each request the connection sends.