formId filter for "GET /user/forms" endpoint

[wzup]

formId filter for "GET /user/forms" endpoint

[hasansoydabas]

Isn't is possible to filter desired form ids after getting user/forms?

We don't have a functionality that support advanced queries right now. Like, should we apply AND or OR for these form ids? They have both valid cases and currently we are building filter queries with AND.

It is not possible for us to change this behaviour.

About the performance issues we will monitor your concerns. However you can also implement a cache mechanism.

Thanks.

[selengenc]

Hi,

we implemented this issue. You can use this property of JotForm Api.

Sample Request Example::
&filter={"id:eq":["formID1","formID2","formID3","formID4"],"status":["disabled","enabled"]}&limit=50

[hasansoydabas]

@wzup Due to some performance impact we had to revert recent changes.
We can't give an estimated time, however we are looking for a better solution.

[wzup]

@hasansoydabas

Due to some performance impact we had to revert recent changes.

Haha, that's really funny to read after this:

Isn't is possible to filter desired form ids after getting user/forms?

So you experience a performance impact, revert changes because of that and then you say:

Hey, you better have performance impact on your side than we have it on ours.

Thanks for the service, yeah. Very good service 👍

[wzup]

@hasansoydabas
hey because of your whining "oooh, we have performance impact we had to revert" we cannot query your API to solve our needs - we constantly get error from your servers.

{
    Error: connect ETIMEDOUT 104.23.128.7:443
        at Object.exports._errnoException (util.js:1012:11)
        at exports._exceptionWithHostPort (util.js:1035:20)
        at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)

    code: 'ETIMEDOUT',
    errno: 'ETIMEDOUT',
    syscall: 'connect',
    address: '104.23.128.7',
    port: 443
}

Can you implement that feature? We needs it for our work. Other solutions are not possible with weak API

[eeertekin]

@wzup IP address is not related with our stack. It belongs to CloudFlare.com.

I'm not sure if CloudFlare is failing or API endpoint.

Send your query, I will check this out.

[wzup]

@eeertekin

IP address is not related with our stack

What's that? My imagination?

Regarding the issue, let me prepare it for you. Will send it to you later.

Yes, the IP is not yours. But you use the service. And it is not possible to use your current version of API with that service. Because of ETIMEDOUT the service has for requests. I don't know if it is you who sets the time out or the service itself. But the result is - it breaks requests.

Implementing formId filter for

1. GET /form/{id}/questions
2. GET /form/{id}

would solve the issue.

[eeertekin]

I have just tested your code with a test account,
and everything is working without a problem.

What is your username? Lets see it with your test env.

[eeertekin]

In addition to your first problem;

You can use /user/forms for more than 29 items. I don't know how you get this number, but we're basically limiting it to 100 as default, and still you can get more than 100 with limit query.

So you don't need to loop over GET /form/{id} endpoint or formIDs filter on /user/forms endpoint.

[eeertekin]

I would like to inform you that id filter is fixed for /user/forms endpoint.

http://api.jotform.com/user/forms?filter={"id":["***64608154459"]}

http://api.jotform.com/user/forms?filter={"id:ne":["****4608154459"]}