Hi I am using java to call rest api of Bigcommerce. How to get all orders from BIg commerce in api V3.
I know for V2. But I could not find the same in V3.I want to get all orders without providing order id.
There isn't currently a v3 equivalent for the v2 Orders endpoint. In v3 you can get transaction/payment data, but not the full order. We do have plans to build out the orders resource on the v3 API in the future.
In the meantime, best practice is to use v3 for resources that are available through v3, but use v2 for any resources that are still on v2 only (like Orders). The API is designed with interoperability in mind, and both versions of the API can be used within the same application.
So I know this is a little late, but I thought I'd pass along how I got this to work just now. The part that doesn't seem to be conveyed very clearly is that the v2 API is available for stores that are required to use the v3 API -- you just have to use the v3 authentication in your request.
A v2 request uses (User, Password) in the basic authorization header, and in my case, for an existing v2 store, I use this URL:
https://www.mystore.com/api/v2/orders/78225
to get an order (where mystore is the real name).
A v3 request uses (X-Auth-Client, X-Auth-Token) in the header, and in my case, for a new v3 store, I use this URL:
https://api.bigcommerce.com/stores/mystorehash/v2/orders/722003
to get an order (where mystorehash is the store_hash that the BC documentation talks about).
Related
Does anyone know how to convert a GitHub PR that is ready to a draft PR and vice versa programmatically? I am trying with the v3 ReST API and the v4 GraphQL api. I can change properties like title and body just fine in both APIs, but when I try to change the draft field, it's not supported. It's also not mentioned in the docs. Somehow it must be possible, at least the GitHub web UI has buttons to do just that, in both directions, but it's not calling either API, but backend functions that have nothing to do with the v3/v4 APIs.
I am working with the v3 of the BigCommerce API and need to find a way to update or on-create the field for google shopping fields for each product.
There is a GET googleproductsearch in v2 but no documentation on updating seem to find an update path
I have tried following this thread:
Accessing Google Shopping Fields via BigCommerce API
Does anyone know what the endpoint to update or create a google shopping setting onto an item using the API instead of the site:
The Google Shopping feed functionality is currently being sunset and isn't included in V3 Catalog APIs, which is likely why documentation for an endpoint was removed. I was able to see the Allow Headers only includes GET, HEAD, and OPTIONS so it doesn't look like modifying these fields is possible via API. You can use a CSV import to accomplish this, and you can find more info about that here: https://support.bigcommerce.com/s/article/Importing-Exporting-Products#table
I am looking for a Squarespace API which i can use to place order.
I searched on google and found a Squarespace documentation that mentions Orders API ( https://support.squarespace.com/hc/en-us/articles/236297987-Squarespace-API-keys ) but it is not helpful as it does not mention any API endpoint.
Commerce API Endpoint for order fulfilment is available but i was not able to find one for placing an order.
Any help in this direction will be highly appreciated.
Using the Squarespace developer docs as a reference, the endpoints are as follows:
All API endpoints are served from https://api.squarespace.com/<version>
For example: curl
"https://api.squarespace.com/1.0/commerce/orders/56f1806d7b863796cbc2ee81"
-H "Authorization: Bearer YOUR_SECRET_API_KEY"
At time of writing, it is not currently possible to place orders using the Squarespace Commerce API. But you can set stock levels now, which means that if you can work with the Stripe API yourself and facilitate the purchase, you can then update stock levels within Squarespace.
With the Squarespace Commerce API, you can build applications that
manage data from your Squarespace store. HTTP endpoints are provided
which allow you to:
Retrieve orders
Update orders with fulfillment information
Retrieve product variant stock levels
Update stock levels using incremental and decremental adjustments
Set finite stock levels for product variants
Mark product variants as having unlimited stock
Note that this feature requries a rather expensive "Commerce Advanced" plan.
I am new to BigCommerce. I am creating a customer using API v3 in BigCommerce and also able to read it from API as shown below but I am not able to get the customer:
but if I am creating the customer using API v2 then it is visible in BigCommerce can any body let me what is wrong here.
I have also found that v2 is going to deprecate v2 so, should i use V2.
The customer resource is only available in V2. There is a newsletter subscriber resource available in V3, but this doesn't support the creation of customer account/entries.
V2 doesn't have a listed deprecation date and is recommended for all resources that don't exist in V3.
I'm trying to understand what the difference between the two REST URLs used for fetching aggregation data in the Yodlee API. In particular, when I look at the sample API calls in Test Drive, the base REST URL that is used is:
https://rest.developer.yodlee.com/services/srest/restserver/v1.0/
But when I looked in the API Docs (https://developer.yodlee.com/apidocs/index.php) and in the Config.js file of the Node.JS sample application, the base REST URL that is used it:
https://developer.api.yodlee.com/ysl
I want to know what the difference between these two URLs are and which one I should really be using for both testing and production. Thanks!
https://developer.api.yodlee.com/ysl is used for new Yodlee REST API, and the https://rest.developer.yodlee.com/services/srest/restserver/v1.0/is the old one (Aggregation REST API).
Of course, Yodlee through mailing lists encourages developers to use new style api (so that's the one you should be using), but the documentation is less then ideal for it, so prepare for dragons ahead.
It doesn't help either that old api throughout Yodlee web site is sometimes just called "REST API", and sometimes the new one is also just called "REST API" without anyway to quickly distinguish for which one is the documentation.
For me the easiest way to distinguish new api from old one is the way version is declared in example urls:
new (Yodlee) api: /v1/
old (REST) api: /v1.0/