📘
TEOS User Guides
Contact CoreLedgerPrivacy Policy
TEOS API
TEOS API
  • 👋Welcome to TEOS API
  • Get started
  • TEOS API overview
    • Terms and concepts
      • Asset
      • Spark
      • Wallet
      • Supply
      • Warp
      • Invoice
      • Transaction
    • Architecture note
      • Tenant setup options
    • Authentication
    • Versioning
  • Using TEOS API
    • Postman examples
    • Rate limits
    • Dealing with blockchain transactions
      • How to get Ether for signing transactions
      • Transaction creation and submission
        • First transaction creation and submission for a new address on the private blockchain
    • Handling errors
      • 1xxxx codes
      • 2xxxx codes
      • 3xxxx codes
    • TEOS Events
    • Warp search
  • TEOS API references
    • TEOS API Swagger (OpenAPI)
  • Using additional APIs of TEOS Platform
    • User authentication flow with TEOS Authentication service and TMS
    • Device authorization flow with TxServer and TEOS Authentication service
    • Adding wallet to the TEOS Platform flow with TxServer and TEOS API
    • Using TxServer API
      • TxServer API (OpenAPI)
      • Key Pair Generation. Transaction Signing
      • Device Restoration
    • Using TEOS Authentication service
      • TEOS Authentication Service API
    • Using TMS API
      • TMS API Swagger (OpenAPI)
      • Handling errors
      • Changelog
    • Using Discovery Service
  • FAQ
  • Changelog
    • v0.9
    • Non-versioned changes
    • Previous versions (not supported)
  • Troubleshooting
Powered by GitBook
On this page
  • New Features:
  • Changes:
  • Fixed bugs:

Was this helpful?

Edit on GitHub
  1. Changelog

v0.9

TEOS API Version 0.9 release notes

PreviousChangelogNextNon-versioned changes

Last updated 1 year ago

Was this helpful?

Released 06.07.2023| Supported until 01.07.2024

New Features:

  • We've added the possibility to retrieve on- and off-chain data of an asset with one endpoint. Use it to make sure that the same info is stored in TEOS Platform and in the blockchain GET /odata/v0.9/Assets({key})/MetaData

  • Starting from this version TEOS API consumers can pay invoices in two ways:

    • with a direct transfer of an invoice asset from own address to the invoice target address by using POST /odata/v0.9/Invoices({key})/PayWithTransfer

    • with executing warp against the one of the owned asset in return to the invoice asset and instructing the TEOS API to transfer the warp result to the invoice target address by using POST /odata/v0.9/Invoices({key})/PayWithWarpTransfer TEOS API consumers should run warp search first, find the warps which will meet the invoice criteria, select the best one and then submit warp parameters to TEOS API to initiate /PayWithWarpTransfer:

      {
        "senderAddress": "0xe0450ce1e2ef73b15514ae6a003b90d0ebac8835", //address paying for the invoice
        "inputAmount": "100500", //the amount of offered asset that sender will pay, taken from the output of the WARP search result
        "supplyIds": [
          "0x827CB8534CFABA240CC90001C271BF2BEC1796539AB2000168E4D1DC000007C7",
          "0xC271BF2BEC1796539AB20001C271BF2BEC1796539CDE000168E4D1DC00000797"
        ] //the list of the supplies which should be executed within a selected warp
      }

Transaction parameters for further signing and submitting are returned as a response according to Transaction creation and submission.

Changes:

  • We improved the swagger describing the TEOS API: removed junk classes, enriched the description and prerequisites for using the specific methods and removed the possibility to call API with swagger, you can find a lot of examples of calling TEOS API methods within

  • We've improved our system of error handling. You can always check the error codes in Handling errors section

Breaking changes:

  • Method for paying invoice POST /odata/v0.8/Invoices({key})/Process was renamed to /PayWithTransfer for v0.9

  • Method for retrieving spark operations has changed to GET /odata/v0.9/SparkOperations/Search instead of POST Now it's fully odata based and you can use odata operators as described in swagger

Fixed bugs:

  • We eliminated the problem when signing parameters couldn't be retrieved for addresses not created with the TEOS API after the transaction is successfully created

  • We changed GET /odata/v0.8/Assets(UniqueAssetId) to return non-activated assets (not written to blockchain, but already existing in the TEOS platform) similar to GET /odata/v0.8/Assets and GET /odata/v0.8/Assets/my

Postman collection