# Issue withh Bybit V5 API Signature Generation using Make.com, please help

**URL:** <https://community.make.com/t/issue-withh-bybit-v5-api-signature-generation-using-make-com-please-help/65938>\
**Category:** Questions\
**Tags:** http\
**Created:** [January 10, 2025, 7:39am UTC](https://community.make.com/t/issue-withh-bybit-v5-api-signature-generation-using-make-com-please-help/65938 "2025-01-10T07:39:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ludwig\_Codjambassis](https://avatars.discourse-cdn.com/v4/letter/l/6bbea6/32.png) [@Ludwig\_Codjambassis](https://community.make.com/u/Ludwig_Codjambassis)\
**Post date:** [January 10, 2025, 7:39am UTC](https://community.make.com/t/issue-withh-bybit-v5-api-signature-generation-using-make-com-please-help/65938/1 "2025-01-10T07:39:20Z")

</div>

## Need Help with Bybit V5 API Signature Issue in Make.com

Hello Make community - I'm having some challenges generating a valid signature for the Bybit V5 API using Make.com. Every attempt results in this error:

```
{"retCode":10004,"retMsg":"Signature for this request is not valid.","result":{},"retExtInfo":{},"time":1736460157151}
```

### Bybit Documentation Guidelines

According to the documentation, these are the requirements for signature generation:

> "Basic steps:
> 
> - timestamp + API key + (recv\_window) + (queryString | jsonBodyString)
> - Use the HMAC\_SHA256 or RSA\_SHA256 algorithm to sign the string in step 1, and convert it to a hex string (HMAC\_SHA256) / base64 (RSA\_SHA256) to obtain the sign parameter.
> - Append the sign parameter to request header, and send the HTTP request. Note: the plain text for GET and POST requests is different."

### Current Implementation

I've implemented the following:

- Parameters are properly ordered alphabetically in both URL and signature string
- Timestamp is retrieved from Bybit's time server with a +1000ms adjustment
- API key has been verified to have read and write permissions

### Configuration Details

Here's my current Make.com setup:

Complete scenario configuration:

 ![Complete scenario](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/f/f/ffb0a91a3a8ddd92397d33cdffa371b645fc870c.png)

HTTP request setup:

 ![HTTP request configuration](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/0/3/038606b119559d8f9c71ce43cc8d6ad40b35e3ee.png)

Parameter configuration:

 ![Parameters](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/6/c/6cdfe27f4b8aa83b0b7788283b92561ecd54ac9e.png)

Additional request details:

 ![Additional HTTP request details](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/9/7/978a5726ebeab47f54952114f1bb2f62036a2411.png)

If anyone has experience with the Bybit V5 API implementation in Make.com, I would appreciate your insights on what might be missing in my configuration.

Thank you for your help.

---

<div class="post-metadata">

**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\
**Post date:** [April 10, 2025, 6:46am UTC](https://community.make.com/t/issue-withh-bybit-v5-api-signature-generation-using-make-com-please-help/65938/2 "2025-04-10T06:46:44Z")

</div>