> For the complete documentation index, see [llms.txt](https://docs.origami.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.origami.tech/user-guide/api-key-creation/gate-io.md). # Gate io ## Step One If you haven't already, go to [Gate’s](https://www.gate.io/signup/XlBHVllf?ref_type=103) website and create an account. Proceed with KYC. ## Step two Verify your account and get started on the API by navigating to API Management.
gate io api for origami tech, go to api management
gate io api for origami tech, create api key
## Step Three Come up with API Key Remark, add this IP to IP Permissions: **15.235.202.52** Use v4 API Key and Trading Account Choose Spot→ Read and Write, Perpetual Futures → Read and Write, Delivery Futures → Read and Write, Wallet→ Read Only, Option → Read and Write, Comission Details → Read and Write, Account → Read Only, Margin Trading → Read and Write, Loan → Read and Write as shown on the screenshot below Click on submit
gate io api for origami tech, create api key
## Step Four Tick the checkboxes and complete creation with Fund Password, 2FA and Verification Code
gate io api for origami tech, risk reminder
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.origami.tech/user-guide/api-key-creation/gate-io.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.