Every RaiderX partner can run their own software on top of RaiderX: your own screens, your own spreadsheet, a connection to the tools you already use. RaiderX keeps the broker’s compliance, document storage, e-signatures and CDA review on its side. Nobody has to turn anything on for you. This guide takes you from a key to a working connection, whether you build it yourself, hand it to a developer, or have an AI agent do the work.
Sign in on the web and tap Developer under Account in the menu (or the Developer card on Settings). The page says what a key made from your account can reach: the whole company if you own an LLC or PMC or lead a team, or only your own records if you are an agent. It has four cards: API keys, Webhooks, Documentation and the reference to hand to a developer or an AI, plus a one-line check to prove a key works.
Tap API keys, then Create key. Name it (Production, Staging, or your developer’s name), pick Test, and tick the acknowledgment. A test key starts with rxsk_test_: it writes to your real records but nothing leaves RaiderX (no e-signatures, emails, texts or push notifications), so start there. A live key starts with rxsk_live_ and acts for real. The key is shown once; copy it somewhere safe. The same page shows how many requests each key has made and when it was last used, and Revoke for the moment one may be exposed.
Documentation opens the full reference: every call, what it needs, what it returns, with a panel to try each one. Every request carries your key. If yours is an organization key, every change also names which of your own users is acting (the X-RaiderX-Actor header) so the audit trail reads right; a personal key records changes as yours and needs nothing more. Prove the connection with the one-line check on the Developer page: it returns your organization, your key and what the key reaches.
If an AI agent (Claude, Cursor, ChatGPT, any coding agent) is building or running your integration, give it the Markdown reference at raiderx.net/api/v1/openapi.md, or the machine-readable version at raiderx.net/api/v1/openapi.json. Both are the complete, current reference and open without a sign-in, so paste the link or the file into its instructions together with a test key. Tell it what you want in plain words ("pull every CDA’s status each morning", "add each new deal to my spreadsheet") and keep it on the test key until you have watched it work.
A test key of their own, named after them, so you can revoke just theirs later; the Documentation link or the Markdown reference; the Postman collection at raiderx.net/api/v1/postman.json if they use Postman; and, for an organization key, the actor id convention you want them to send. They never need your RaiderX sign-in; never share your password. When they are ready for production, you create the live key.
Webhooks → New endpoint: paste the address your software listens on, tick the events you want (or none for all of them), and choose live traffic, test traffic or both. The signing secret is shown once; save it, your developer uses it to verify each delivery. RaiderX posts signed JSON within moments of each event (a CDA approved, a document reviewed, a deal closed, and more) and retries for up to 24 hours. The same page lists every delivery with its response and a Replay button. An agent’s endpoint hears only events about the agent’s own records.
Once the test run works, create a live key, switch your software to it, and watch the first day: request counts on API keys and deliveries on Webhooks. Every call is logged with a request id you can quote in a support request.
You, your developer or your AI build against the documentation with nothing real going out.
Your software hears about broker decisions and compliance events as they happen.
Real deals, documents and CDAs flow through your software; RaiderX still reviews every CDA.
An LLC or PMC owner, a team leader or the broker gets an organization key that reaches the whole organization, the same as their dashboard. Everyone else gets a personal key that reaches only their own records, never a colleague’s. The Developer page says which you have.
It is open to everyone and in daily use. Every account with an active key is told before a breaking change.
A key or a webhook signing secret is shown the moment it is created and never again. Lose it and you create a new one.
A test key writes to your real records; nothing leaves RaiderX (no e-signatures, emails, texts or push notifications) and its webhook events reach only endpoints set to test traffic. Name test records so you can find and delete them, and keep test and live keys in separate setups.
Broker review of every CDA, document storage, e-signature and the audit trail stay on RaiderX’s side. The API gives you the data and the uploads; the broker’s decisions come back to you as webhook events.
If you are locked out over your license, or your company is suspended for compliance, changes are refused with the reason, the same as in the app. If RaiderX has turned the API off for your organization, every call says so; ask us through a support request.
Sign in and the platform walks you through it. Stuck on a step? Ask ConsoleX from your dashboard — it knows this process end to end — or browse all 23 partner guides.
Sign in · DeveloperChecked against the platform on October 25, 2026.