How to connect your software to the RaiderX API

The seven steps

1. 1

   Open the Developer area

   Sign in on the web and go to raiderx.net/app/llc/developer. It is not in the menu. You will see four cards — API Keys, Webhooks, Documentation and Markdown export — and a one-line check to prove a key works. Only the owner’s account can open it.

2. 2

   Create a key — test first

   Tap API Keys, then Create key. Name it (Production, Staging, or your developer’s name) and pick a mode. A test key starts with rxsk_test_ and skips real e-signatures, emails and texts, so start there. A live key starts with rxsk_live_ and acts on your real company. 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 a Revoke link for the moment one may be exposed.

3. 3

   Read the documentation

   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, and anything that changes a record also names which of your own users is acting (the X-LLC-Actor header) so the audit trail reads right. Prove the connection with the one-line check on the Developer overview — it returns your company, your key and the actor you sent.

4. 4

   Give your AI agent the same documentation

   If an AI agent — Claude, Cursor, ChatGPT, any coding agent — is building or running your integration, give it the Markdown export 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 and the actor id to use. Tell it what you want in plain words — "sync each new agent into our CRM", "pull every CDA’s status each morning" — and keep it on the test key until you have watched it work.

5. 5

   Working with a developer? Give them these four things

   A test key of their own, named after them, so you can revoke just theirs later; the Documentation link or the Markdown export; the Postman collection at raiderx.net/api/v1/postman.json if they use Postman; and 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.

6. 6

   Turn on webhooks when you want to hear about events

   Webhooks → New endpoint: paste the address your software listens on, list the events you want (or leave it blank 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 — CDA approved, agent onboarded, compliance document expiring, and more — and retries for up to 24 hours. The same page lists every delivery with its response and a Replay button.

7. 7

   Go live

   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.