# How to Ingest data into Elasticsearch with URL Callback?

**URL:** <https://discuss.elastic.co/t/how-to-ingest-data-into-elasticsearch-with-url-callback/284003>\
**Category:** Logstash\
**Created:** [September 13, 2021, 5:58am UTC](https://discuss.elastic.co/t/how-to-ingest-data-into-elasticsearch-with-url-callback/284003 "2021-09-13T05:58:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![e-fo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/e-fo/32/87474_2.png) [@e-fo](https://discuss.elastic.co/u/e-fo)\
**Post date:** [September 13, 2021, 5:58am UTC](https://discuss.elastic.co/t/how-to-ingest-data-into-elasticsearch-with-url-callback/284003/1 "2021-09-13T05:58:52Z")

</div>

Hello, thanks for your great community

I want to logging some data from some mobile app attribution service (such as [Adjust](https://www.adjust.com/) or [Appsflyer](https://www.appsflyer.com/)) into Elasticsearch  
the admin panel of attribution service allow me to set an url callback in panel to notify me for each event (such as install, uninstall, purchase, ...)

My question is what's the best method to logging this events with url callback into elasticsearch?  
I searched for a logstash plugin that supports url callback but I not found anything.

Thanks for any help. 🙂

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 13, 2021, 5:59am UTC](https://discuss.elastic.co/t/how-to-ingest-data-into-elasticsearch-with-url-callback/284003/2 "2021-09-13T05:59:47Z")

</div>

> [@e-fo](#):
>
> url callback

Do you mean something like [Http\_poller input plugin | Logstash Reference [8.11] | Elastic](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-http_poller.html)?

---

<div class="post-metadata">

**Author:** ![e-fo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/e-fo/32/87474_2.png) [@e-fo](https://discuss.elastic.co/u/e-fo)\
**Post date:** [September 13, 2021, 6:35am UTC](https://discuss.elastic.co/t/how-to-ingest-data-into-elasticsearch-with-url-callback/284003/3 "2021-09-13T06:35:19Z")

</div>

No @warkolm , in [Http\_poller input plugin](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-http_poller.html) we are the caller of API through url that specifing in logstash pipeline config file.  
in the "URL Callback" method we are specified the url in attribution service panel and the service calling our url and informs me. in other word, we are the callee and attribution service is caller.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 13, 2021, 6:37am UTC](https://discuss.elastic.co/t/how-to-ingest-data-into-elasticsearch-with-url-callback/284003/4 "2021-09-13T06:37:22Z")

</div>

Ok then, [Http input plugin | Logstash Reference [7.14] | Elastic](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-http.html) looks relevant.

---

<div class="post-metadata">

**Author:** ![e-fo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/e-fo/32/87474_2.png) [@e-fo](https://discuss.elastic.co/u/e-fo)\
**Post date:** [September 25, 2021, 12:10pm UTC](https://discuss.elastic.co/t/how-to-ingest-data-into-elasticsearch-with-url-callback/284003/5 "2021-09-25T12:10:33Z")

</div>

Thanks @warkolm , this plugin is fit with my requirements.

---

<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:** [October 23, 2021, 12:10pm UTC](https://discuss.elastic.co/t/how-to-ingest-data-into-elasticsearch-with-url-callback/284003/6 "2021-10-23T12:10:45Z")

</div>

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