
The short answer: you do not have to read the whole documentation. For an integration that works and does not break at the first problem, eight stops are enough, in this order. The first five are the same for any project; the rest depend on what you are automating.
The path, stop by stop
|
|
|
|
|
|
|
|
Where to start, depending on the project
| If you want to... | Read first |
| Show prices and plans on your website | Catalog |
| Send SMS from your system | SMS |
| Send emails from your application | Email Center |
| Manage DNS records | DNS |
| Open support tickets from another system | Support |
| Check and pay invoices with credit | Invoices and credit |
| Know whether a slow operation has finished | Key and status |
| Do not skip the API rules. A program that repeats a purchase without Idempotency-Key, that does not wait after a 429, or that reads only the first page of a list causes problems the reference alone will not explain. |
| From day one, keep the key in an environment variable called RLX_API_KEY: it is the one every example in the documentation reads, so you can copy them without changing anything. See the code examples. |
|
The first step takes a minute and needs no key. Get started with the API |
RECOMMENDED PRODUCT Web hosting with cPanel Domain and SSL included, daily backups and the panel you already know. from $5.36/mo (3-year plan, with coupon) See plans |











