npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@baxcloud/parse-server-baxverify

v1.0.4

Published

Parse Server custom auth adapter for BaxVerify phone login (SMS OTP)

Readme

@baxcloud/parse-server-baxverify

Parse Server custom auth adapter for BaxVerify phone login. Mobile clients verify SMS OTP with BaxVerify, then call ParseUser.logInWith('baxverify', { id, token }); Parse Server validates the proof JWT server-side.

For BaxVerify webhook verification (and other BaxCloud product webhooks), use @baxcloud/baxcloud-server-sdk on your server alongside this adapter.

Product-specific SDKs:

Install

npm install @baxcloud/parse-server-baxverify parse-server

Requires Node.js 18+. Your BaxCloud API key must stay on the Parse Server — never in mobile apps.

Quick start

1. Environment

BAXCLOUD_PROJECT_ID=your-project-id
BAXCLOUD_API_KEY=your-api-key

2. Parse Server config

const { ParseServer } = require('parse-server');

new ParseServer({
  databaseURI: process.env.DATABASE_URI,
  appId: process.env.PARSE_APP_ID,
  masterKey: process.env.PARSE_MASTER_KEY,
  serverURL: process.env.PARSE_SERVER_URL,
  auth: {
    baxverify: {
      module: '@baxcloud/parse-server-baxverify',
    },
  },
});

3. Flutter client

After BaxVerify verifyOtp, pass result.externalAuth to Parse:

await ParseUser.logInWith('baxverify', result.externalAuth!);

See Flutter BaxVerify SDK and BaxCloud docs.

Configuration options

You can pass credentials in Parse auth config instead of env vars:

auth: {
  baxverify: {
    module: '@baxcloud/parse-server-baxverify',
    projectId: process.env.BAXCLOUD_PROJECT_ID,
    apiKey: process.env.BAXCLOUD_API_KEY,
    consume: true, // default — single-use token on login
  },
},

| Option | Description | |--------|-------------| | projectId | BaxCloud project ID (or BAXCLOUD_PROJECT_ID) | | apiKey | BaxCloud API key (or BAXCLOUD_API_KEY) | | consume | Consume JWT on login (default true) |

Custom factory

For a local auth file or shared defaults:

const { createBaxVerifyParseAuth } = require('@baxcloud/parse-server-baxverify/create');

module.exports = createBaxVerifyParseAuth({
  projectId: process.env.BAXCLOUD_PROJECT_ID,
  apiKey: process.env.BAXCLOUD_API_KEY,
});

How it works

  1. Client sends OTP via BaxVerify (@baxcloud/baxverify on your API, or baxcloud_verify_sdk on Flutter).
  2. Client verifies OTP and receives a short-lived accessToken (JWT proof).
  3. Client calls ParseUser.logInWith('baxverify', { id: phone, token: accessToken }).
  4. This adapter calls BaxVerify validateVerificationToken, checks phone matches authData.id, and stores { phone } on the Parse User.

Error codes

Token validation calls the BaxVerify API. Failures return stable codes such as BAXVERIFY_TOKEN_INVALID, BAXVERIFY_TOKEN_CONSUMED, or BAXVERIFY_FEATURE_DISABLED, often with details.helpUrl pointing to the dashboard fix.

See BaxVerify error codes.

Related SDKs

License

MIT

Support

  • Help: https://baxcloud.tech/dashboard/help
  • Contact: https://baxcloud.tech/contact
  • Documentation: https://baxcloud.tech/docs/baxverify/sdk/parse-server
  • Email: [email protected]