Skip to content

Comments

Change delist schedule API request to unsigned#1659

Merged
carlosmiei merged 1 commit intosammchardy:masterfrom
m-HD:m-HD-patch-spot-delist-schedule
Feb 17, 2026
Merged

Change delist schedule API request to unsigned#1659
carlosmiei merged 1 commit intosammchardy:masterfrom
m-HD:m-HD-patch-spot-delist-schedule

Conversation

@m-HD
Copy link
Contributor

@m-HD m-HD commented Jan 14, 2026

It's not necessary to sign the spot delist schedule request.

It's not necessary to sign the spot delist schedule request.
@m-HD m-HD requested a review from carlosmiei as a code owner January 14, 2026 20:10
async def get_spot_delist_schedule(self, **params):
return await self._request_margin_api(
"get", "/spot/delist-schedule", signed=True, data=params
"get", "/spot/delist-schedule", signed=False, data=params
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@m-HD Hello, if you try to open the link in the browser https://api.binance.com/sapi/v1/spot/delist-schedule

you can see you get {"code":-2014,"msg":"API-key format invalid."} meaning that the endpoint indeed requires credentials

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For spot delist schedule an API-key is necessary, that's true. But the request for this endpoint doesn't need to be signed as it is MARKET_DATA.
See: https://developers.binance.com/docs/wallet/general-info#request-security
I have tested the patch and it worked.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pull request is still open. It's working properly, but hasn't been included in the latest update 1.0.35.
What's the problem?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@m-HD Sorry I was assuming that providing signed=False would skip the APIKey in Headers (since this endpoint is an "hybrid" only requires apiKey but not signing) but that's not the case, will merge it now.

@carlosmiei carlosmiei merged commit 02ce388 into sammchardy:master Feb 17, 2026
2 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants