In 2.15.0 and earlier, the useSandbox parameter was optional in

this._client=new CoinbasePro({ apiKey: account.apikey, apiSecret: account.secret, passphrase: account.passphrase})

From 2.16.0 the useSandbox parameter is mandatory

this._client=new CoinbasePro({ apiKey: account.apikey, apiSecret: account.secret, passphrase: account.passphrase, useSandbox: false })

Can we make useSandbox optional again and have it default to false?

Hi @bennyn, I have been running the library and so far so good. I would like to point out an issue I got today, though this is not a library issue, I think.

So, today websocket was trying to reconnect for more than 15 minutes and it couldn't. I restarted the program and it connected. Even though the Coinbase Pro documentation says that it is 4 seconds interval I think it prevents to reconnect at some point (if you keep reconnecting).

Don't you think it would be a good idea to provide an option to set a reconnection interval when websocket connects (in connect() method)?

Please let me know what do you think.

Hey thanks for building and maintaining this package. I was attempting to migrate from depreciated coinbase-pro package and unfortunately, my event listeners are not firing using the example provided in the docs.

I attempted to go through the code in coinbase-pro-node/src/client/WebSocketClient.ts and I was not able to even find subscribeToTickers method in src. I do not have a good grasp of typescript so it could be part of the problem.

(I created a simplified gist using the old package), would it be possible for me to implement an identical/similar system for handling WS messages as I have done below?

1. Subscribe to multiple channels ex ['ticker', 'full']
2. receive all channel updates to one event listener [WebSocketEvent.ON_MESSAGE'] so I can redirect them to a switch statement.
3. store an instance of the socket and resubscribe/ destroy recreate

https://gist.github.com/Slurpgoose/ab41a4674a7a353b8f68b9d80af2b004

Also if this is possible will I need to import WebSocketEvent, WebSocketChannelName objects to access these methods or are they inherited from new CoinbasePro(auth)? Or am I able to subscribe using a string.

I've been getting an internal server error for a couple of hours on a crypto transfer.

client.rest.withdraw.postCryptoWithdrawal(0.0000001, 'BTC', '339FL7Xoh3WmrcJmo6ejeLfBVZgus2fTdx', true).then((data) => {
    console.log('===============')
    console.log('Transfering DATA')
    console.log(data)
}).catch((error) => {
    console.log('===============')
    console.log('Transfering DATA')
    console.log(error)
})

Do we have support for /withdraw/coinbase-account? That would be much easier, and have no fees. Thanks again!

The listProfiles API supports an active parameter. See here

This parameter is missing. See here

What is the equivalent in your library to the following code from the coinbase-pro library:

publicClient.getProductHistoricRates(
  'BTC-USD',
  { 
    granularity: 3600,
    start: start_time,
    end: end_time
  }  
)

I'm getting a 400 error message when using your library but nothing very specific beyond that. Is there way to surface the errors a little better on the rest calls?

Thanks!

Hello,

Thanks for developing this project.

Would it be possible to add the updated Candles[] array to this callback please: https://github.com/bennycode/coinbase-pro-node/blob/main/src/demo/rest-watch-candles.ts#L12

I would like to know the full candle history from when I called client.rest.product.getCandles up until the latest tick.

When returning a structure in a function in NodeJS, the returnvalue must be between brackets. Otherwise it returns {}. There are 7 files with 10 occurences where this should be fixed.

I tried to create a pull request, but it removed the brackets, or assigning the structure to a variable first

Hi @bennyn I am still having a reconnection issue though I changed connect() parameters.

So, at some point websocket establishes connection and then closes, and this run as a loop. On ON_OPEN it shows that it establishes connect and just after that ON_CLOSE it says convection closed and repeats the same. I have to manually stop and run program in order to make it work.

Any recommendation and/or suggestion? should I subscribe every time when it reconnects again?

An opportunity to improve documentation:

Related to #339, I was curious how to query for all orders (rather than for open orders alone). It seemed like the only parameters we could pass with the request were pagination values. After a quick scan of the source I realized a general query-string is created from whatever object is passed as the pagination object (thanks to loose restrictions on the interface). As such, getOpenOrders({ status: 'all' }) would suffice to retrieve all orders.

• Add Pagination
• "granularity too small for the requested time range. Count of aggregations requested exceeds 300"
• Handle 'Slow rate limit exceeded'
• Handle 'Public rate limit exceeded'
• Watch candles: coinbase/coinbase-pro-node#203 (comment)
• Add test case for WebSocket onerror
• WebSocket unsubscribe: As a shorthand you can also provide no product ids for a channel, which will unsubscribe you from the channel entirely
• Type WebSocket messages: https://github.com/coinbase/coinbase-pro-trading-toolkit/blob/v0.4.0/src/exchanges/coinbasePro/CoinbaseProMessages.ts#L117 OR https://github.com/vansergen/coinbase-pro/blob/v2.0.0/src/websocket.ts#L142

Hi

I'm trying to use coinbase-pro-node in a Vue app but I'm receiving the following error when trying to use the websocketclient

Error: No valid WebSocket class provided
_connect reconnecting-websocket-mjs.js:506
ReconnectingWebSocket reconnecting-websocket-mjs.js:203
connect WebSocketClient.js:159
_callee$ VCoinbaseSocket.vue:49
Babel 10
VueJS 4
click vuetify.js:2564
VueJS 33
VCoinbaseSocket.vue:51

Any ideas?

Thanks

Observed on watching one minute candles.
When candle minutes are skipped from coinbase api due to no activity candle watch of 1 minute is stuck.
Suggest
const matches = candles.filter((candle: any) => {
const open = new Date(candle.openTimeInISO)
const expected = new Date(expectedTimestampISO)
return open >= expected !Changed to >=
})

Latest axios seems to cache the get candle history automatically perhaps
in getCandles pass date or header to force fresh get
const response = await this.apiClient.get<RawCandle[]>(resource, {
params: { ...params, time: new Date() },
})

The following seems to only return the body from the response:

client.rest.product.getCandles('BTC-USD', {
  granularity: CandleGranularity.ONE_HOUR,
  start: start_time,
  end: end_time
});

How do you get the complete response including, e.g., the status code?

Thanks for your work on this project! My feature request is to add support for deposits.

EDIT:
I'm also seeing this on private endpoints not just market data endpoints. So, I am not entirely sure if there is an issue here, may just be an issue with my stack.

First off, I really appreciate the work put into this project, I think its great and I would really like to be using it long term. I'd love to contribute as well, if I am knowledgeable enough, and I'll most likely take a stab as creating a patch for this issue locally.

That being said, here is my issue:

Initially I see that in my console this appears:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api-public.sandbox.pro.coinbase.com/products/BTC-USD/candles?granularity=60. (Reason: missing token ‘cb-access-key’ in CORS header ‘Access-Control-Allow-Headers’ from CORS preflight channel)

I am attempting to integrate this library with a react application, using gatsbyjs. Everything imports and builds as I expect, however at runtime I see that the cb-access-key is checked for in every OPTIONS request:

Access-Control-Request-Headers | cb-access-key,cb-access-passph…cess-sign,cb-access-timestamp
-- | --

But, this value is not listed in the response headers:

access-control-allow-headers | Content-Type, Accept, cb-session, cb-fp, cb-form-factor
-- | --

I've seen this while trying to use the rest client, such as with the getProductTicker() method and while trying to get the rest-watch-candles demo code to run in browser similarly to this:

const WatchCandle = ({client, productId, granularity}) => {
  let [candle,setCandle] = useState({});

  async function setWatch() {
    client.rest.on(ProductEvent.NEW_CANDLE, (productId, granularity, candle) => {
      console.info('Recent candle', productId, granularity, candle.openTimeInISO);
    });

    // 3. Get latest candle
    const candles = await client.rest.product.getCandles(productId, {
      granularity,
    });
    const latestCandle = candles[candles.length - 1];
    const latestOpen = latestCandle.openTimeInISO;
    console.info('Initial candle', productId, granularity, latestOpen);

    // 4. Subscribe to upcoming candles
    client.rest.product.watchCandles(productId, granularity, latestOpen);
  }

  useEffect(() => {
    setWatch();
  });

  return (<>Waiting...</>)
}

For reference on why I think its an issue with looking for that cb-access-key token on every request to coinbase, excerpt from here:

The Access-Control-Allow-Headers header is sent by the server to let the client know which headers it supports for CORS requests. The value of Access-Control-Allow-Headers should be a comma-delineated list of header names, such as "X-Custom-Information" or any of the standard but non-basic header names (which are always allowed).

This error occurs when attempting to preflight a header that is not expressly allowed (that is, it's not included in the list specified by the Access-Control-Allow-Headers header sent by the server). To fix this, the server needs to be updated so that it allows the indicated header, or you need to avoid using that header.

Are there any upgrade steps? I can reproduce this locally by switching the versions.

Hello, I was really looking forward to using this in my Angular project as it has TypeScript support and that's a huge plus for me, but when using it in something browser based, it doesn't work because of the Crypto dependency from what I gathered. Do you have any solution to this?

I detecting new deposit from getAccountHistory method, but there is no txHash in the details. How do I get a transaction hash from api? What is a details.transfer_id for?

Usually, listAccounts() works fine and returns the balances of the requested account.

newbalances=await account._client.rest.account.listAccounts();
if(newbalances.length===undefined) { console.log("Newbalances:"+JSON.stringify(newbalances)); };

Sometimes it returns getTime(). Newbalances:{"iso":"2021-01-15T09:22:55.205Z","epoch":1610702575.205}

@bennyn So I partially tested websocket connection issue. When I manually connect to the Coinbase Pro websocket (wss://ws-feed.pro.coinbase.com) it works and in 24 hours hasn't broken yet, but in your library I still got loop (connect and reconnect). See timestamp list. Again when I restart the program it connects and listens for a while.

...
[2020-04-03T14:01:30.517Z] Coinbase Pro websocket established connection!
[2020-04-03T14:02:29.572Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:02:34.818Z] Coinbase Pro websocket established connection!
[2020-04-03T14:03:34.134Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:03:39.382Z] Coinbase Pro websocket established connection!
[2020-04-03T14:04:39.111Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:04:44.338Z] Coinbase Pro websocket established connection!
[2020-04-03T14:05:44.001Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:05:49.252Z] Coinbase Pro websocket established connection!
[2020-04-03T14:06:48.941Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:06:54.177Z] Coinbase Pro websocket established connection!
[2020-04-03T14:07:53.531Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:07:58.881Z] Coinbase Pro websocket established connection!
[2020-04-03T14:08:58.573Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:09:03.833Z] Coinbase Pro websocket established connection!
[2020-04-03T14:10:03.432Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:10:08.674Z] Coinbase Pro websocket established connection!
[2020-04-03T14:11:07.984Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:11:13.226Z] Coinbase Pro websocket established connection!
[2020-04-03T14:12:12.450Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:12:17.675Z] Coinbase Pro websocket established connection!
[2020-04-03T14:13:17.068Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:13:22.295Z] Coinbase Pro websocket established connection!
[2020-04-03T14:14:22.171Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:14:27.450Z] Coinbase Pro websocket established connection!
[2020-04-03T14:15:27.345Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:15:32.567Z] Coinbase Pro websocket established connection!
[2020-04-03T14:16:32.200Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:16:37.476Z] Coinbase Pro websocket established connection!
[2020-04-03T14:17:37.124Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:17:42.351Z] Coinbase Pro websocket established connection!
[2020-04-03T14:18:42.161Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:18:47.394Z] Coinbase Pro websocket established connection!
[2020-04-03T14:19:46.614Z] Coinbase Pro websocket was closed, it will reconnect again
[2020-04-03T14:19:51.846Z] Coinbase Pro websocket established connection!

Docs: https://docs.pro.coinbase.com/#list-orders

Your API is called getOpenOrders, and I suppose it makes sense to have only open statuses available, but it seems that you may be missing a simple getOrders method that will accept any OrderStatus.

It would be nice to be able to use OrderStatus.DONE without having to use @ts-ignore. I could just use all for my purposes, but I feel like that could cause problems without extra filtering at some point.

I have a function that is called once per minute to refresh account balances:

newbalances=await account._client.rest.account.listAccounts();

This function mostly has no issues, but I get a "request timestamp expired" message after some time. I haven't been able to catch the error and the program thus terminates unexpectedly.

I have noticed that in these cases CB-ACCESS-TIMESTAMP has a value of NaN. I don't know if this is the cause, or not.

headers: {
  Accept: 'application/json, text/plain, */*',
  'CB-ACCESS-KEY': '*** VALID KEY ***',
  'CB-ACCESS-PASSPHRASE': '*** VALID PASS *** ',
  'CB-ACCESS-SIGN': '*** VALIG SIGNATURE ***',
  'CB-ACCESS-TIMESTAMP': NaN,
  'User-Agent': 'axios/0.21.0'
},

and the response is

response: {
status: 401,
statusText: 'Unauthorized',
...
data: { message: 'request timestamp expired' }
},

How to modify ErrorUtil.js to catch request timestamp expired so that the request is tried. I also have 400 request timeout, which I would also like handle in ErrorUtil.js, and have them retried.
401 Unauthorized - Timestamp expired.txt

In the previous deprecated version of Coinbase-pro-node, the only pairs returned when running getProduct(), were what is listed below. Noticeably missing is ETH-USD pair. Will this package have any support for ETH-USD pair?

• ETH-BTC
• LINK-USDC
• BTC-EUR
• BAT-USDC
• BTC-GBP
• BTC-USD

I was reviewing the websocket client code and didnt see where L2 updates were being returned and just wanted to double check if they are in fact supported?

I apologize in advance, as this very well could be user error. But I was hoping you could help me connect to the user channel via Websocket. I've been trying to figure it out all day, with no success. Here is the simplified code I've been using:

const {CoinbasePro} = require('coinbase-pro-node');

const auth = {
  apiKey: '',
  apiSecret: '',
  passphrase: '',
  useSandbox: false,
};

const client = new CoinbasePro(auth);

const channel = {
  name: 'user',
  product_ids: ['BTC-USD'],
};

client.ws.on('message', message => {
  console.info(`Received message of type "${message.type}".`, message);
});

client.ws.on('error', errorMessage => {
  throw new Error(`${errorMessage.message}: ${errorMessage.reason}`);
});

client.ws.on('open', () => {

	console.log('OPENED....')

  client.ws.subscribe(channel);
});

client.ws.connect();

It's copied from an example I found in a closed issue for this module in an attempt to avoid any mistakes. However, it does not seem to work... the "OPENED...." console log never fires. And no message or errors seem to be triggered.

My authorization details are correct, which I can verify because the REST API version works properly.

Thanks in advance for any help! And thanks either way for the work you've put into the module.

So I am stuck just trying to figure out how to just get the rest example given to work. I have it installed properly using node but every time I try to use it there's some sort of stupid error.

First trying to use it I got the error "Cannot use import statement outside of a module"
So I said okay and added the "type=module" to my code.

Then I get "Failed to resolve module specifier "CoinbasePro". Relative references must start with either "/", "./", or "../""
So I tried adding one of the characters it says.

Regardless of which one I use I get the error "net::ERR_ABORTED 404 (Not Found)"

The file I am running this from is in the root directory of the site. Does it have to be within the node_modules folder?

If anyone can assist me id appreciate it please!

Hi @bennyn ,

its me again, unfortunately I came across a new issue in regards to WebSocketChannelName.USER.

auth config is not passed to class WebSocketClient and I was not able to find a method inside the class to retrieve a new signature.

I was able to monkey patch the latest version by passing
the configuration to WebsocketClient here

As well by adding a validation here

      if (message.channels.some(channel => channel.name === 'user') && signature === undefined){
           signature= signRequest(this.auth, 'GET', '/users/self/verify');
       }

Although you already have implemented the logic for creating a signature in coinbase-pro-node/src/auth
I added these functions from depreciated coinbase-node package to return a signature since they were easier for me to understand.

const checkAuth = (auth) => {
    if (auth && !(auth.apiKey && auth.apiSecret && auth.passphrase)) {
        throw new Error(
            'Invalid or incomplete authentication credentials. Please provide all of the key, secret, and passphrase fields.',
        );
    }
    return auth || {};
};

const signRequest = (auth, method, path, options = {}) => {
    checkAuth(auth);
    const timestamp = Date.now() / 1000;
    let body = '';
    if (options.body) {
        body = JSON.stringify(options.body);
    } else if (options.qs && Object.keys(options.qs).length !== 0) {
        body = `?${querystring.stringify(options.qs)}`;
    }
    const what = timestamp + method.toUpperCase() + path + body;
    const key = Buffer.from(auth.apiSecret, 'base64');
    const hmac = crypto.createHmac('sha256', key);
    const signature = hmac.update(what).digest('base64');
    return {
        key: auth.apiKey,
        signature,
        timestamp,
        passphrase: auth.passphrase,
    };
};

I appreciate all the work you have done on this project and just wanted to share the issue in case I missed something or so it could be fixed in a future release.

if this solution seems reasonable (except for the 2 unnecessary functions from the old package) let me know and Id be happy to make a PR.

At this time, https://api.pro.coinbase.com/products returns 58 currency pairs. However, the following only returns 6:

const {CoinbasePro} = require('coinbase-pro-node');
const auth = {
    apiKey: '',
    apiSecret: '',
    passphrase: '',
    useSandbox: true,
};
const client = new CoinbasePro(auth);
const response = await client.rest.product.getProducts();

Is there a way to make it return all currency pairs?

Just wondering if there was / will be withdrawal to coinbase account possible with this library

Dependabot encountered the following error when parsing your .dependabot/config.yml:

The property '#/update_configs/0/default_assignees' did not contain a minimum number of items 1
The property '#/update_configs/0/ignored_updates' did not contain a minimum number of items 1

Please update the config file to conform with Dependabot's specification using our docs and online validator.

I'm trying to place a market order with a stop loss set below the current trade price but I get an error Invalid order_type market when I do. The code I am using is below

client.rest.order.placeOrder({
    type: "market",
    funds: "100",
    side: "buy",
    product_id: 'BTC-USD',
    stop: "loss",
    stop_price: "19300"
}).then(res => {
    console.log(res);
}).catch(err => {
    console.log(err);
});

It works fine if I remove the stop loss but fails if I keep it, even though the API documentation says otherwise

Hi, Ive finished transitioning over to using this library and everything seems to be working great!

A couple things I have concerns about:

1. When network loss occurs reconnecting-websockets is able to handle reconnecting and messages automatically continue a few seconds later. Unfortunately there is no event emitted and so I am using a timer to keep track of how many subscribed markets did not receive a message per 1005ms interval (5ms to account for timer variance).

The reason I believe this is important is because, I use a unix socket to transmit exchange snapshots to another systemd services that handle buying and selling and I want to prevent placing limit orders based on incorrect market data.

2. when reconnecting occurs client.ws.subscribe() is not called and therefore snapshots/last_match are not emitted. Meaning the orderbook has potential to be incorrect when a long interrupt occurs. (worst case scenario is some asks could be lower than the current bid causing a limit order to be a market order and loosing money).

At this point I am keeping track of max acceptable time disconnected and manually resubscribing.

3. Along with using the timer to track when messages stop being emitted, I verify to make sure I receive one beat per channel subscribed per minute. My timer implementation is semi-accurate (1-5ms variation) and it seems that I miss maybe 50 out of 650,000 messages or so, in some instances they are delayed and not actually missed while other times maybe a silent reconnect occurs or some other bottleneck in my application.

Initially I had a lot more missed messages as a result of poor implementation on my end. I ended up using clinic and node-tick-processor to figure it out.

By implementing more error events new users of this library will be able to debug their issues faster.

my mistakes

• I was subscribed to too many channels (bandwidth bottleneck).
• I was doing too much processing in this thread and after 6 or 8 hours I would get 100% cpu utilization and was not getting any indication of missing data prior to setting up my own beat tracking.

coinbase pro has a built in sequenceId to track messages for all channels unfortunately it seems to require being subscribed to the full channel in order for sequence numbers to be in sync and l2_updates do not have a sequenceId.

To combat this instead of saving the sequence number I started taking the timestamp to save new Date(timestamp).getSeconds() to confirm there was not a larger period than 1 second from the previous message for a product_id.

An alternative could be to count heart-beat messages per minute per product id.

I would love to get your thoughts/criticism on this as maybe I am overthinking something simple and doing something unnecessary.

I am testing on V1.15. if adding snippets of timer code, beat tracking etc can help please let me know I will be happy to do so :)

@bennycode First off, thank you for a great library! It has gotten me a long way in my project.

As far as I can tell, if the WebSocket connection is dropped, the next time it is connected it is up to the code using the library to re-subscribe to the channels to which the dropped connection was subscribed. I've implemented the logic for this in my own code, but was wondering if the place for this should be in this library? I'd be willing to put together a PR at some point if you thought that would be a good fit.

So, essentially, when the code using the library calls WebSocketClient.subscribe(), the WebSocketClient would keep track of what channels have been requested to subscribe. If something like WebSocketClient.disconnect() was called, it would forget previous subscriptions. Otherwise, when the WebSocket comes back up, it would automatically re-subscribe to the channels that were subscribed before the WebSocket went down. No worries if you don't think that logic fits in the library.

I am working on an app that will let a user add multiple exchanges to track their assets in 1 location. I am having an issue when I am testing adding 2 API keys for Coinbase Pro and requesting the history with this library. I have tried making sure its only requesting 1 set of data at a time. I have also tried creating a new connection object per request. Everything works great with 1 connection but as soon as it tries to request a 2nd it throws a 403 axios exception.

I don't think this is a bug in your code. But I am wondering if there is a known way to get around this issue.

node_version: 14
typescript_version: 4.2.4
coinbase_pro_node_version: 3.0.4

I'm currently placing a new order like this:

const orderResponse = await client.rest.order.placeOrder({...});

orderResponse :

{
  id: '8f3214cf-0db3-4c25-81b5-f7a05f863104',
  product_id: 'BTC-USD',
  side: 'buy',
  stp: 'dc',
  funds: '199.00497512',
  specified_funds: '200',
  type: 'market',
  post_only: false,
  created_at: '2021-05-25T01:44:22.982286Z',
  fill_fees: '0',
  filled_size: '0',
  executed_value: '0',
  status: 'pending',
  settled: false
}

Based on the Coinbase docs and the type definitions in the library, there should be a price property on the results, but there isn't one.

I was using getOpenOrders() without problems. After change to getOrders() I get 401 error. No other change made. I don't pass any params to getOrders().

Side question: when the autogenerated API reference is updated? It still references getOpenOrders(). Thank you.

Not sure if this is the right place to get help with this, but figured I'd give it a shot. Trying to make a call to this library on an api request from express, but the client never seems to actually do the request, just kinda hangs.

var express = require("express");
var router = express.Router();
var { CoinbasePro } = require('coinbase-pro-node');

router.get("/", function (req, res, next) {
    let query = req.query

    var auth = {
        apiKey: query.api_key,
        apiSecret: query.secret_key,
        passphrase: query.passphrase,
    };
    
    var client = new CoinbasePro(auth);

    client.rest.account.listAccounts().then(accounts => {
        const message = `You can trade "${accounts.length}" different pairs.`;
        res.send(message)

    }).catch((error) => {
        res.send(error)
    })
});

module.exports = router;

any explanation why anything else works in this route except this library would be appreciated

Hi

How can I get the list of all orders?

I found the getOrder but require an orderId

Thanks

In my code I'm trying to get all of my orders for a certain crypto currency and when I do, it throws a 401 error with the message invalid signature.

For more information, this is my code:

The product id I used was LTC-USD but it doesn't work with any I've tried.

const orders = await client.rest.order.getOrders({
  status: ["all"],
  product_id: productId,
});

Surprisingly, it works if I omit the product_id parameter.

const orders = await client.rest.order.getOrders({
  status: ["all"],
});

That works and returns a paginated result with all my orders.

I don't think I'm doing anything wrong?

I understand two node packages with official Coinbase support appear to now be deprecated. Was there a state reason why it was deprecated? Can you please describe the support that this repo here has if official or not?

Hi @bennyn I found your library very interesting and I am trying to use it. However, the documentation says that connections to websocket feed are rate-limited to 1 per 4 seconds per IP. This is not related to the real-time feed data as far as you are connected right? I just want to know how does your lib handle this issue? or I have to manually reconnect?

I'm having an issue that I can't seem to figure out. There are a very limited number products being returned. I don't see anything listed on coinbase explaining the short list.

Current list of products:

[
  {
    id: 'BAT-USDC',
    base_currency: 'BAT',
    quote_currency: 'USDC',
    base_min_size: '1',
    base_max_size: '300000',
    quote_increment: '0.000001',
    base_increment: '0.000001',
    display_name: 'BAT/USDC',
    min_market_funds: '1',
    max_market_funds: '100000',
    margin_enabled: false,
    post_only: false,
    limit_only: false,
    cancel_only: false,
    trading_disabled: false,
    status: 'online',
    status_message: ''
  },
  {
    id: 'BTC-USD',
    base_currency: 'BTC',
    quote_currency: 'USD',
    base_min_size: '0.001',
    base_max_size: '10000',
    quote_increment: '0.01',
    base_increment: '0.00000001',
    display_name: 'BTC/USD',
    min_market_funds: '10',
    max_market_funds: '1000000',
    margin_enabled: true,
    post_only: false,
    limit_only: false,
    cancel_only: false,
    trading_disabled: false,
    status: 'online',
    status_message: ''
  },
  {
    id: 'LINK-USDC',
    base_currency: 'LINK',
    quote_currency: 'USDC',
    base_min_size: '1',
    base_max_size: '800000',
    quote_increment: '0.000001',
    base_increment: '1',
    display_name: 'LINK/USDC',
    min_market_funds: '10',
    max_market_funds: '100000',
    margin_enabled: false,
    post_only: false,
    limit_only: false,
    cancel_only: false,
    trading_disabled: false,
    status: 'online',
    status_message: ''
  },
  {
    id: 'BTC-EUR',
    base_currency: 'BTC',
    quote_currency: 'EUR',
    base_min_size: '0.001',
    base_max_size: '10000',
    quote_increment: '0.01',
    base_increment: '0.00000001',
    display_name: 'BTC/EUR',
    min_market_funds: '10',
    max_market_funds: '600000',
    margin_enabled: false,
    post_only: false,
    limit_only: false,
    cancel_only: false,
    trading_disabled: false,
    status: 'online',
    status_message: ''
  },
  {
    id: 'BTC-GBP',
    base_currency: 'BTC',
    quote_currency: 'GBP',
    base_min_size: '0.001',
    base_max_size: '10000',
    quote_increment: '0.01',
    base_increment: '0.00000001',
    display_name: 'BTC/GBP',
    min_market_funds: '10',
    max_market_funds: '200000',
    margin_enabled: false,
    post_only: false,
    limit_only: false,
    cancel_only: false,
    trading_disabled: false,
    status: 'online',
    status_message: ''
  },
  {
    id: 'ETH-BTC',
    base_currency: 'ETH',
    quote_currency: 'BTC',
    base_min_size: '0.01',
    base_max_size: '1000000',
    quote_increment: '0.00001',
    base_increment: '0.00000001',
    display_name: 'ETH/BTC',
    min_market_funds: '0.001',
    max_market_funds: '80',
    margin_enabled: false,
    post_only: false,
    limit_only: false,
    cancel_only: false,
    trading_disabled: false,
    status: 'online',
    status_message: ''
  }
]

anyone know how to increase rec window for this?

REST API

Private endpoints

Accounts

• List Accounts
• Get an Account
• Get Account History
• Get Holds

Orders

• Place a New Order
• Cancel an Order
• Cancel all
• List Orders
• Get an Order

Fills

• List Fills

Deposits

• Deposit funds from a payment method
• Deposit funds from a coinbase account

Withdrawals

• Withdraw funds to a payment method
• Withdraw funds to a coinbase account
• Withdraw funds to a crypto address

Stablecoin Conversions

• Create Conversion

Payment Methods

• List Payment Methods

Coinbase Accounts

• List Accounts

Fees

• Get Current Fees

Reports

• Create a new report
• Get report status

Profiles

• List Profiles
• Get a Profile
• Create profile transfer

User Account

• Trailing Volume

Market Data

Products

• Get Products
• Get Product Order Book
• Get Product Ticker
• Get Trades
• Get Historic Rates
• Get 24hr Stats

Currencies

• Get currencies

Time

• Get time

Hi there,

Not an issue but more like a feature request.

Right now the functionality to delete individual orders is missing (I think)

If I can work out how to do pull request, I'll have a stab at implementing it.

Thanks for your work!

WebSocket times-out after 100 seconds from establishing connection and subscribing to channel. There is no ping implemented to keep the WebSocket alive. I have implemented a work-around by re-subscribing every minute, but would be great if the connection would stay open.

    account._client.ws.subscribe([
      { name: WebSocketChannelName.USER, product_ids: user._products }
    ]);

Does this lib support the FIX API (fix.pro.coinbase.com) ?

https://docs.pro.coinbase.com/#fix-api