TagPipes + any REST API
Pull data from any JSON API into Lens. This is how most platforms without a native source get connected.
Lens: REST API source
Lens calls a JSON API on your schedule, with GET or POST, and stores the rows it returns as a table in your workspace.
How you set it up
- In Lens, open Data Tables, click + New Table and choose API.
- Enter the base URL, the endpoint, any parameters and the date parameters.
- Tell Lens where the rows sit in the response, and whether the API pages by page number or offset.
- Choose the authentication: none, a connection saved in Settings > Security & Access, an API key in a header or the query string, a bearer token, or basic auth.
| What it reads | The rows at the response path you set, on the schedule you set. |
|---|---|
| Limits | The API has to return JSON. For platforms with a ready-made Airbyte connector, the Airbyte route can be less work. |
| Plan | Included with every Lens plan. |
Documentation: API source
Other ways TagPipes works with REST APIs
Airbyte
If Airbyte already has a connector for the platform, point it at Lens instead. TagPipes + Airbyte
How your data is handled
- Credentials you add are stored in Settings > Security & Access, and you can remove them there at any time.
- Each company sees only the data from the accounts and sources it connected.
Read the Privacy Policy and the Terms of Service.
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.
If it speaks JSON, Lens can hold it.
Sign up and add an API table in Lens, or ask us for a walkthrough first.
Already have an account? Log in.