Nijipe DevelopersREST API SPECIFICATION
Access Merchant Hub

2. API Quickstart

To make authenticated API calls to Nijipe, include your store API key as a Bearer token in the Authorization header of every request. API keys are prefixed nj_live_ for production and nj_test_ for sandbox testing. Test mode keys create isolated invoices that never interact with the Bitcoin mainnet.

Authorization: Bearer nj_live_YOUR_STORE_API_KEY

1. Canonical Base URL
The Base URL for all API requests is https://www.nijipe.com/api/v1.

⚠️ Crucial Redirect Warning

You must use the exact canonical URL (including www.). If you send requests to the root domain (nijipe.com), you will trigger a 308 Permanent Redirect. Standard HTTP clients (like Node.js fetch or Axios) will follow this redirect but will strip your Authorization: Bearer header in the process for security reasons, resulting in a 401 Unauthorized error.

ℹ️ Subdomain Architecture Note

The api.nijipe.com subdomain is strictly reserved for our internal Bitcoin Core RPC and ZMQ streaming nodes. All standard REST API traffic must be routed through the main application domain shown above.

Nijipe operates fully non-custodially for On-chain Bitcoin transactions. When a client checkout is generated, our derivation engine takes your store's configured XPUB/ZPUB key and derives a unique, single-use Segwit receiver address, ensuring complete sovereign control of your funds.