Fundamentals
Authentication and environments
API keys, test and production environments, and how to keep keys safe.
Every call carries your business key in the x-api-key header.
curl https://api.pineplechain.com/v1/me \
-H "x-api-key: ak_mer_••••••••••••••••"Test and production
| Test | Production | |
|---|---|---|
| Key prefix | ak_mer_ | ak_live_ |
| Network | XRPL Devnet | XRPL Mainnet |
| Money | Test XRP | Real XRP |
| Data | Separate | Separate |
Each key belongs to the environment it was created in. If the X-Pineplechain-Mode header says otherwise, the API answers 409 mode-mismatch. Responses always carry the environment in the X-Pineplechain-Mode header.
Good practices
- The key is shown only once, when it is created. pineplechain stores only a hash of it.
- Use the key on the server only. Never in the browser, a mobile app or a repository.
- Create one key per system and revoke a leaked one under Integration › API keys. Revocation is immediate.