BitcartCC update: API Keys management, less configuration, more features!

0 60

Written by

BitcartCC

Your all-in-one opensource crypto solution

4 years ago

In community: Bitcoin Cash(e11c)

New BitcartCC update is out!

Main change in this update is authorization system, which:

Fixes many existing and future bugs hard to investigate and fix
Decreases maintenance spent on the system itself, which allows adding new features faster
Improves integrations and gives more possibilities for creating your own apps around your instances' BitcartCC Merchants API

We switched from JWT tokens to usual tokens with OAuth scopes, more below.

Now tokens aren't refreshed, but now you can control tokens of your account!

In profile page(user icon in the top right side of the any page->Profile) you'll be able to delete, view and create API Tokens(API Keys)

Each token can be restricted to access only certain parts of your account, via permissions system!

When creating a token, you'll be able to select which permissions to grant to that token, or even provide only partial access(like access only to store A and B, but not C)

Also, those permissions can be granted by a third-party app or site instead, visit

/authorize page on your instance to see it

Authorize your or other people's apps and have fun!

Authorization request is a powerful way of granting third-party apps and sites access to your instance, allowing many new usecases, like custom design admin panels, invoice automation and tracking tools, automatic discount creation tools and many more-no limitations!

Example of authorization request URL

Other changes:

Added new /crud/stats endpoint to fetch all stats at once, which means you'll get stats in your admin panel faster and with less bandwidth!

One more important change is, all endpoints used by store POS are now fully or partially public, which means there is no need to type in store email, password and id in our installer wizards!

/stores/{storeid} endpoint will return only partial data of the store, like store name and display email. Store email server settings aren't retrieved and only store owner can access full data.