SVX Documentation
HomepageAPISDK
Current
Current
  • Docs
  • Concepts
    • Digital Identity and Why It's Important
    • Digital Wallets
    • Ecosystems
    • Information Security
    • Personal Data & Attributes
    • Privacy- and Security-by-design
    • Secure Data Storage
    • Selective Disclosure / ZKP
    • Tokens and Tokenisation
    • Verifiable Credentials
    • Terminology
  • Platform
    • Secure Value Exchange
    • Authorisation, Tenant & Organisation Manager (ATOM)
    • Credential Service
    • Decentralised Identifiers (DIDs)
    • Keys
    • Tenants, Organisations, and End-Users
    • Vault
      • Enterprise Vault
    • Portal
    • Supported Standards
  • Guides
    • Onboarding to SVX
    • API Guides
      • Credentials
        • Credential Schemas
        • Credential Types
        • Issue Credentials
        • Presentation Definitions
        • Presentations
      • DIDs
        • DID Resolver
        • DID Registrar
        • DID Methods
          • did:key
          • did:web
          • did:ebsi
          • did:indy
        • DID Controller Keypair
      • OpenID Connect
        • For Verifiable Presentation
      • Users
        • Inviting End-Users
        • Authenticating End-Users
      • Vault
        • Items and Slots
        • Connections and Sharing
        • Classification Hierarchies
        • Attachments
        • On-sharing & Client Tasks
        • Account Delegation
      • Machine-2-Machine Communication
    • Portal Tutorials
      • Tenant Administrators
        • Onboard to a Tenancy
        • Dashboard and Navigation
        • Manage Tenancy
        • Manage Tenant Administrators
        • Manage Organisations
        • Manage Organisation Administrators
        • Credential Schemas
        • Applications
        • End Users
      • Organisation Administrators
        • Manage Organisation
        • Onboarding and Organisation Setup
        • Dashboard and Navigation
        • Manage Organisation Administrators
        • Credential Templates
        • View Credentials
        • Verification Templates
        • Verification Requests
        • Connections
        • Applications
    • Wallet Tutorials
      • Wallet Set Up
      • Provider Registration
      • Organisation Configuration
      • Credentials
      • Requests
      • Security
      • Wallet Recovery
  • Tools
    • Meeco SDK & CLI
    • Cryppo SDK & CLI
  • Releases
    • 2.1.1
    • 2.1.0
    • 2.0.0
    • 1.4.3
    • 1.4.2
    • 1.4.1
    • 1.4.0
    • 1.3.8
    • 1.3.7
    • 1.3.6
    • 1.3.5
    • 1.3.4
    • 1.3.3
    • 1.3.2
    • 1.3.0
    • 1.2.5
    • 1.2.4
    • 1.2.3
    • 1.2.2
    • 1.2.1
    • 1.2.0
    • 1.1.0
    • 1.0.0
    • Legacy API-of-Me
  • Policies
    • Privacy
    • Developer Policy
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Guides
  2. API Guides

Machine-2-Machine Communication

Last updated 1 year ago

Was this helpful?

Tenant and Organisation Administrators can provide an application with authenticated access to SVX functionality. This allows the application to perform different actions based on the permissions of the Tenant or Organisation Administrator creating the application.

Applications created by Tenant Administrators will be able to:

  • Invite and remove end-users

  • Manage credential schemas

Applications created by Organisation Administrators will be able to:

  • Create and archive credential templates

  • Issue and revoke credentials

  • Create and archive verification templates

  • Create verification requests and view verification responses

  • Create and cancel connections with end-users

Access the SVX Sandbox API and create an application

To access the SVX Sandbox API and create an application you will need to follow the steps below:

1. Access the SVX Sandbox API documentation

Navigate to . At the top of the landing page, you will see the OpenAPI3 specification. Download the specification and import it into .

Note To download the OpenAPI3 specification into Postman, follow these simple steps:

  1. Download the specification from the

  2. Open Postman

  3. Import the downloaded .json file

2. Create an application

Note Tenant and Organisation Administrators can both create Applications, however, different workflows are achieved based on the associated role and access rights.

Note Once an application has been created, ensure you record the client_id and client-secret.

3. Open the API configuration

View the Open API configuration at https://login-sandbox.securevalueexchange.com/oauth2/.well-known/openid-configuration and retrieve your authorisation token.

Use the token endpoint from the configuration (https://login-sandbox.securevalueexchange.com/oauth2/token) to obtain an authorisation token. You can do this using the cURL command as shown below:

   curl -X POST https://login-sandbox.securevalueexchange.com/oauth2/token \
   -d 'grant_type=client_credentials' \
   -d 'client_id=YOUR_CLIENT_ID' \
   -d 'client_secret=YOUR_CLIENT_SECRET'

Replace YOUR_CLIENT_ID and YOUR_CLIENT_SECRET with the actual values you obtained when creating the application.

Note The Application Token will expire every 10 minutes. To refresh the token you will need to call the token endpoint again.

4. Access the SVX Sandbox API

With the obtained authorisation token, you can now use the SVX Sandbox API. For example, if you want to access the me endpoint, use the following cURL command:

   curl --location 'https://api-sandbox.svx.exchange/me' \
   --header 'Meeco-Organisation-Id: YOUR_ORGANISATION_ID' \
   --header 'Accept: application/json' \
   --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Replace YOUR_ORGANISATION_ID with the relevant ID for your organisation, and YOUR_ACCESS_TOKEN with the token obtained in the previous step. You should now be able to successfully access the SVX Sandbox API using the provided authorisation token.

Log in to the and create an application, see the Applications tutorial located in the for more information.

SVX Sandbox API documentation
Postman
SVX API documentation
SVX Portal
Portal tutorials