
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@ciptex/recording-sdk
Advanced tools
The recording-api helper library lets you write Node.js code to make HTTP requests to the Ciptex Race Recording API.
Do not use Basic Authentication in a front-end application. Doing so can expose your Twilio credentials to end-users as part of the bundled HTML/JavaScript sent to their browser.
The easiest way to install recording-sdk is from NPM. You can run the command below from your project directory to install the library:
npm install --save @ciptex/recording-sdk@latest
Then in your code:
import { RecordingClient } from "@ciptex/recording-sdk"
Try Listing Configuration like this:
import { RecordingClient } from "@ciptex/recording-sdk"
const accountSid = "ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"; // Your Account SID from www.twilio.com/console
const authToken = "your_auth_token"; // Your Auth Token from www.twilio.com/console
const client = new RecordingClient({ accountSid, authToken });
const main = async () => {
try {
// LIST EXAMPLE HERE
}
catch (error) {
console.error(error);
}
}
main()
It's okay to hardcode your credentials when testing locally, but you should use environment variables to keep them secret before committing any code or deploying to production. Check out How to Set Environment Variables for more information.
const accountSid = "ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
const authToken = "your_auth_token";
const client = new RecordingClient({ accountSid, authToken });
import { RecordingClient } from "@ciptex/recording-sdk"
const accountSid = "ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
const authToken = "your_auth_token";
const client = new RecordingClient({ accountSid, authToken });
const main = async () => {
try {
//CREATE EXAMPLE HERE
}
catch (error) {
console.error(error);
}
}
main()
import { RecordingClient } from "@ciptex/recording-sdk"
const accountSid = "ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
const authToken = "your_auth_token";
const client = new RecordingClient({ accountSid, authToken });
const main = async () => {
try {
//GET EXAMPLE HERE
}
catch (error) {
console.error(error);
}
}
main()
If the Recording API returns a 400 or a 500 level HTTP response, the recording-sdk library will throw an error which can be caught. 400-level errors are normal during API operation ("Invalid number", "Cannot deliver SMS to that number", for example) and should be handled appropriately.
Once you're up and running with the recording-sdk library, you'll find code samples using the latest version in our REST API docs
FAQs
@ciptex/recording-sdk
We found that @ciptex/recording-sdk demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 12 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.