# Fetching, ingesting and merging data from REST API in 2023

**URL:** https://discuss.elastic.co/t/fetching-ingesting-and-merging-data-from-rest-api-in-2023/325143
**Category:** Logstash
**Tags:** ingest-pipeline
**Created:** [February 9, 2023, 1:07pm UTC](https://discuss.elastic.co/t/fetching-ingesting-and-merging-data-from-rest-api-in-2023/325143 "2023-02-09T13:07:17Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![NiklasHBB](https://avatars.discourse-cdn.com/v4/letter/n/b9e5f3/32.png) [@NiklasHBB](https://discuss.elastic.co/u/NiklasHBB)
#### Post date: [February 9, 2023, 1:07pm UTC](https://discuss.elastic.co/t/fetching-ingesting-and-merging-data-from-rest-api-in-2023/325143/1 "2023-02-09T13:07:18Z")

</div>

I want to fetch and ingest data from several REST APIs. In previous discussions in [2019](https://discuss.elastic.co/t/ingesting-data-from-api/167192) and [2020](https://discuss.elastic.co/t/data-ingestion-from-api/254267) it was recommended to use logstash [http\_poller](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-http_poller.html) input plugin. Is that still the best way to go with fleet and elastic agents around?

Can I control the way data is ingested such that data from different API endpoints will be combined/merged/joined in a single index (think of creating a big denormalised table from several normalised relations)? Or is it better to keep data from different endpoints in their respective index and work with several indices (for creating dashboards and analytics)?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 9, 2023, 1:07pm UTC](https://discuss.elastic.co/t/fetching-ingesting-and-merging-data-from-rest-api-in-2023/325143/2 "2023-03-09T13:07:33Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
