Authentication with the GraphQL API

Real Items Products

Search…

Product Documentation

Our Products

GraphQL API

Authentication with the GraphQL API

View a product template

List items by product template ID

View an item

Create product template

List all items

List product templates

Create items (NFTs, Phygitals)

Tracker App

CP3 (Consumer Protection 3.0)

Tokenized Asset Manager

Glossary

Authentication with the GraphQL API

We do not proved API Keys. Instead authentication is handled by OAuth2.
To use the API the client app must first authenticate using a username and password. Each application connecting to the GraphQL API must have an account (just like a human) in the Real Items system. To create an account for your application log into the Tokenized Asset Manager, click on Administrators and create an account.
How it works
Successful authentication will return a JWT token which must be used for the duration of the session. After authorization, the JWT token must be passed into each request as the Bearer token. The default session duration for JWT tokens is 24 hours. The logic for detecting session timeouts and reauthorizing must be coded within the client application.
Here is an example authentication curl request which will return a JWT token.
1
curl --location --request POST 'https://staging.realitems.io/oauth/token' \
2
--header 'Authorization: Basic cmVhbGl0ZW1zc3RhZ2luZ2NsaWVudGlkOi5CZldjRnk4TUE4KEM=' \
3
--header 'Content-Type: application/x-www-form-urlencoded' \
4
--data-urlencode 'grant_type=password' \
5
--data-urlencode '[email protected]' \
6
--data-urlencode 'password=1a/l^k93QGi:'
Copied!
If authentication is successful the response will look something like this.
1
{
2
    "access_token": "eyJhbGiOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJjb3VudHJ5IjoiVVNBIiwidXNlcl9uYW1lIjoia2VuQHJlYWxpdGVtcy5vcmciLCJtb2JpbGUiOiIrNTEwOTMyNDkxMSIsImxhc3RfbmFtZSI6Indvb2RydWZmIiwid2FsbGV0cyI6WyIweGY0ZTVFRjdkZTE1NDQ1QmM1NEU2M0FCMmJGZEM0YkJEY2U0MmUxZkIiLCIweDlFRUNBQjRERjEzQjYzMzhBZDYwMzg4MzVlNjFEQTJENDZjMWRDQjAiXSwiYXV0aG9yaXRpZXMiOlsiU1RBTkRBUkRfVVNFUiIsIkFETUlOX1VTRVIiLCJTVVBFUl9VU0VSIl0sImNsaWVudF9pZCI6InJlYWxpdGVtc3N0YWdpbmdjbGllbnRpZCIsImF1ZCI6WyJyZWFsaXRlbXNzdGFnaW5nand0cmVzb3VyY2VpZCJdLCJzY29wZSI6WyJyZWFkIiwid3JpdGUiXSwiaWQiOiIyIiwiZXhwIjoxNjE0OTc0Mjg3LCJmaXJzdF9uYW1lIjoia2VuIiwianRpIjoiYTc0MGIyY2YtYWRmOC00MjQ0LWJiMTMtZTdlOGVhODQyZjI1In0.xNuUbl87rN6lCGjuJV5MWpFZR6uG-SYEA4hZv3EFes8",
3
    "token_type": "bearer",
4
    "expires_in": 86400,
5
    "scope": "read write",
6
    "id": "22",
7
    "first_name": "joe",
8
    "last_name": "shmoe",
9
    "country": "USA",
10
    "mobile": "+4159324911",
11
    "wallets": [
12
        "0xf4e5EF7de15445Bc54E63AB2bFdC4bBDce42e1fB",
13
        "0x9EECAB4DF13B6338Ad6038835e61DA2D46c1dCB0"
14
    ],
15
    "jti": "a740b2cf-adf8-4244-bb13-e7e8ea842f25"
16
}
Copied!

GraphQL API

View a product template

Last modified 6mo ago

Copy link

Contents

We do not proved API Keys. Instead authentication is handled by OAuth2.

How it works