New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

@ciptex/recording-sdk

Package Overview
Dependencies
Maintainers
12
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@ciptex/recording-sdk

@ciptex/recording-sdk

latest
npmnpm
Version
0.1.6
Version published
Maintainers
12
Created
Source

Race Recording SDK

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.

Installation

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"

Testing your installation

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.

Using This Library

Authenticate Client

const accountSid = "ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
const authToken = "your_auth_token";
const client = new RecordingClient({ accountSid, authToken });

Create A New Record

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()  

Get Existing Record

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()  

Handling Exceptions

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.

More Documentation

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

Package last updated on 10 Sep 2024

Did you know?

Socket

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.

Install

Related posts