| Discussion Forum: Thread 215739 |
|
 |
| | | Author: | terryer_sandbox  | | Posted: | Jan 23, 2017 18:59 | | Subject: | API - GET /orders more parameters needed | | Viewed: | 85 times | | Topic: | Suggestions | | Status: | Open | | Vote: | [Yes|No] | |
|
| Hi there,
i'm writing for a customer of mine a few tools which are using your API.
What bothers me currently the most is that there are to few parameters for the
Get /orders call. What we do is that we are asking all orders with the status
shipped to send a feedback and the drive_thru over the API. But since there are
not enough parameters i can provide to the API, the result will be a huge list
of orders, because the least customers are marking their orders as received.
There are several things (filters) you can include to safe server power and bandwidth,
but the easiest one is a date-filter. Let the people give the API an "From-Date"
and a "To-Date". The results are than only these in between. If you only transmit
one of them than every order up or from than will be send. If none is given,
than you do as you do now and give just everything back.
This would be pretty helpful not only for me, but also for your servers.
Other users can write other parameters they wish, like and "feedback given" parameter.
Another solution for our problem would be, if there would be more push-notification-options.
If i could receive a push-notification when the status of an order is changed
(and not only by the buyer).
So i would be really pleased if you could implement a few more parameters to
the GET /orders call as soon as possible.
Best regards
|
|
|
| | | | | |
| | | | | Author: | ignacioxd | | Posted: | Jul 24, 2017 15:39 | | Subject: | Re: API - GET /orders more parameters needed | | Viewed: | 30 times | | Topic: | Suggestions | |
|
| In Suggestions, terryer_sandbox writes:
| | Hi there,
i'm writing for a customer of mine a few tools which are using your API.
What bothers me currently the most is that there are to few parameters for the
Get /orders call. What we do is that we are asking all orders with the status
shipped to send a feedback and the drive_thru over the API. But since there are
not enough parameters i can provide to the API, the result will be a huge list
of orders, because the least customers are marking their orders as received.
There are several things (filters) you can include to safe server power and bandwidth,
but the easiest one is a date-filter. Let the people give the API an "From-Date"
and a "To-Date". The results are than only these in between. If you only transmit
one of them than every order up or from than will be send. If none is given,
than you do as you do now and give just everything back.
This would be pretty helpful not only for me, but also for your servers.
Other users can write other parameters they wish, like and "feedback given" parameter.
|
Wishful thinking: GraphQL. This will probably never happen though.
| | Another solution for our problem would be, if there would be more push-notification-options.
If i could receive a push-notification when the status of an order is changed
(and not only by the buyer).
So i would be really pleased if you could implement a few more parameters to
the GET /orders call as soon as possible.
Best regards
|
According to the API documentation at http://apidev.bricklink.com/redmine/projects/bricklink-api/wiki/PushNotificationMethod,
push notifications are supposed to be sent when buyers update the status of an
order and when the order is updated (items added/removed). In my experience,
I only get push notifications when a new order is placed.
|
|
|
|
|
|
|
Germany, Hamburg
USA, North Carolina