i am receive only 18 orders and also if i set the limit property I get only 18 orders back.
admin/orders.json?limit=50
And if i use the page property
admin/orders.json?limit=50&page=2
it returns empty orders.
{"orders":[]}
After some more searching i found out that this works
admin/orders/search.json?query=&limit=122
but is not mentioned in the API, and is not implemented in the Python SDK
In case anyone cares, you can find this API reference here : http://docs.shopify.com/api/order
Related
This quite frankly is driving me up the wall. (connecting to a node.js server that needs the order id)
The post id is whats actually used when using the /wp-json/wc/v3/orders/
So something like = /wp-json/wc/v3/orders/259992?customer_key ... Works but using the "number" item which is connected to this (the order number) it errors. For example's sake we will say the order number linked with the order post id I used above (259992) = 99794
I've been trying to get the result by order number.
If I run /wp-json/wc/v3/orders?customer_key ... it lists all the orders no problems. However if I attempt to run /wp-json/wc/v3/orders?select?q=number:99794?consumer_key= ... I get the following error (i have also tried this with ?search?q=number:99794?) no no avail
Which is daft because i know you can list resources. I just did it with /wp-json/wc/v3/orders?customer_key ...
I just need it to return the json for the order id not the post id. Is this at all possible?
Have also tried: /wp-json/wc/v3/orders?filter[number]=99798?customer_key ... Same error
(First, I want to note that this didn't answer my question: How to get the latest/new messages from Telegram API)
I am building a history object to poll the 20 latest messages from a channel/chat:
get_history = GetHistoryRequest(
peer=input_peer,
offset_id=0,
offset_date=None,
add_offset=0,
limit=20,
max_id=0,
min_id=0,
hash=0
)
The API here:
https://core.telegram.org/api/offsets
mentions max_date and min_date.
I imagine to get the latest messages, I should use limit=[number], offset_date=[same_number] and max_date be the date at the moment. However, I can't get from the API documentation how "max_date" should be represented. Any ideas how, and whether I am correct in my assumptions in getting the latest 20 messages?
This is also useful to have around: https://core.telegram.org/method/messages.getHistory
I'm using google places api, but it returns the value with different place_id.
I have considered this blog : https://developers.google.com/places/documentation/search
I have requested with place id like this :
https://maps.googleapis.com/maps/api/place/details/json?key=AAIS...
In this url, you can see that the place_id is "EiJ..."
But in the returning json, i have received different place_id.
"place_id" : "AASS...",
"reference" : "df..."
When I have tried with reference, it was the same.
What did I wrong?
Is this the same location with different place_id?
Thanks for your help...
1) Never post your API key on a public forum. Go get yourself a new one.
2) reference has been deprecated, so you don't need to include it
3) EiJG... doesn't look like a Placeid. My guess is that you are trying to look up a value that doesn't exist and you're getting strange behavior.
Run a Place Search and get the Placeid and try again. You haven't posted what you searched for initially so it's impossible to verify that EiJ... really is a valid Placeid.
You can also have more than one place ID associated with a particular place.
In that case, if you request details using one place ID, you can get another ID back (you used the alternate ID, it returns what it considers the primary).
I found your question how to deal with this because I'll be storing information using their primary key and if it changes it will cause issues since the ID initially comes from their search (I'll get the new ID and not realize it is associated with the information I stored).
The Google Custom Search API requires the use of an API key, I have get from the Google APIs console. The API provides 100 search queries per day for free. I want to more,so I have signed up for billing in the console and succeed.I can set the requests/day,defalut 1000 requests/day.But the total results are still 100,I show 10 in one page,so I can get 10 pages.
Billing solve the querys per day,but not the total results.The document does not explain clearly.What should i do to solve the results problem.Does XML API have the same problem? Must I Replace the JSON API by XML API?
another year passed... Limits are the same =((
Google forces us to use multiple accounts to get complete search results.
Use a query per day/week/month.
Or you can sort huge result array by publish date. And when '100-items' limit is reached you should execute new request with excluding first items by applying "the lowest(or the highest) possible value" condition on publish date.
btw, using webbrowser you could set 100 results per page. So total count of result items is 1000 per query. Web crawling would be helpful=))))
be happy!
Using the Box 1.0 REST API, I am trying to work with the functions in SOAP UI.
The API doc for get_managed_users with user_id=12345 (internal id retrieved with get_user_id call correctly) is returning all the users. The docs say that would be the case if you do not specify a user_id value. But my full command is: (Token and API key changed to protect the clueless)
https://www.box.com/api/1.0/rest?user_id=27360&auth_token=blahbalhblah1234&action=get_managed_users&api_key=someKeyYouShouldNotSee
Now I could work with the complete result list, but that won't scale as we get thousands of users into the system.
I can make a call with edit_managed_user, using the same user_id value and the change is reflected in the UI, and in the next get_managed_users call. Thus I do have the correct user_id value, I would so assume.
I tried testuser#gmail.com as the user_id value as well, and get the entire list back. This leads me to believe that somehow I am sending user_id wrong, but I just do not see it.
Any hints? Why, with what seems like a valid user_id value is it acting like it is absent or incorrect?
Most likely you have either called this method with an invalid user_id, or one that is not in your set of managed users. Can you double check that the user comes back in your list of already managed users?