How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Oumla Ltd

Oumla Ltd tokenization API

The tokenization API from Oumla Ltd — 9 operation(s) for tokenization.

Documentation Provider Profile APIs.io OpenAPI GitHub

Oumla Ltd tokenization API is one of 12 APIs that Oumla Ltd publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tokenization. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 13 operations across 9 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://sandbox.oumla.com.

13 operations 9 paths 33 schemas 2 DELETE6 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://sandbox.oumla.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Oumla Ltd tokenization API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (x-api-key).

  • x-api-key — API key for authentication

Paths & Operations 13

Across 9 paths, the API surfaces 13 operations — 2 DELETE, 6 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

tokenization 13
POST
/api/v1/tokenization/tokens
Issue Token
issueNewToken 1 param body → 202400401403404500
GET
/api/v1/tokenization/tokens
List Tokens
getTokens 3 params → 200400401403500
POST
/api/v1/tokenization/tokens/link
Link Contract
linkContract 1 param body → 200400401403404409500
POST
/api/v1/tokenization/collections
Create new Collection
createCollection 1 param body → 202400401403404500
GET
/api/v1/tokenization/collections
List Collections
getCollections 3 params → 200400401403500
GET
/api/v1/tokenization/collections/{id}
Get collection by ID
getCollectionById 2 params → 200401403404500
DELETE
/api/v1/tokenization/collections/{id}
Delete collection by ID
deleteCollection 2 params → 200401403404500
GET
/api/v1/tokenization/collections/{id}/tokens/{tokenId}
Get Collection token details
getCollectionTokenDetails 3 params → 200401403404500
POST
/api/v1/tokenization/collections/{id}/tokens/mint
Mint token
mintToken 2 params body → 200400401403404500
GET
/api/v1/tokenization/collection/tokens
Get collection tokens by ID or type
getCollectionTokens 5 params → 200400401403404500
POST
/api/v1/tokenization/collections/{id}/tokens/burn
Burn token
burnToken 2 params body → 200400401403404500
DELETE
/api/v1/tokenization/tokens/{id}
Unlink Token
unlinkToken 2 params → 200401403404500
GET
/api/v1/tokenization/tokens/{id}
Get linked token by ID
getLinkedToken 2 params → 200401403404500

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are CollectionTokenDetailDto (16 properties), CreateCollectionBodyDto (10 properties), TokenMintOrBurnItemDto (10 properties), TokenMetadataDto (9 properties). Each schema is shown below with its type and property counts.

GetCollectionTokenDetailsResponseDto
object
1 property
IssueTokenWorkflowResponseDto
object
1 property 1 required
UnlinkTokenResultDto
object
1 property
ConstructorParam
object
3 properties 3 required
CollectionTokenDetailMetadataDto
object
6 properties
UnlinkTokenResponseDto
object
1 property
CreateCollectionWorkflowResponseDto
object
1 property 1 required
WorkflowStartResultDto
object
4 properties 4 required
CreateCollectionBodyDto
object
10 properties 5 required
GetLinkedTokenResponseDto
object
1 property
LinkContractBodyDto
object
5 properties 2 required
GetCollectionsResponseDto
object
3 properties
CollectionItemDto
object
8 properties
TokenMintOrBurnItemDto
object
10 properties
MintOrBurnRecordSummaryDto
object
6 properties
TokenMetadataDto
object
9 properties
TokenResponseDto
object
5 properties
MetadataDto
object
6 properties 2 required
CreateParams
object
1 property 1 required
BurnTokenBodyDto
object
5 properties 3 required
IssueNewTokenRequestBody
object
9 properties 8 required
MintTokenResponseDto
object
1 property 1 required
DeleteCollectionResponseDto
object
1 property
LinkContractResponseDto
object
1 property
CollectionTokenDetailDto
object
16 properties
GetCollectionByIdResponseDto
object
1 property
ApiErrorResponseDto
object
7 properties 5 required
CollectionMetadataDto
object
4 properties
GetTokensResponseDto
object
2 properties
GetCollectionTokensResponseDto
object
2 properties
MintTokenBodyDto
object
7 properties 4 required
MetadataAttributeDto
object
3 properties 2 required
BurnTokenResponseDto
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

oumla-ltd-tokenization-api-openapi.yml Raw ↑

Other APIs Oumla Ltd publishes across the network.

Oumla Ltd addresses API
AE Profile APIs.io
Oumla Ltd assets API
AE Profile APIs.io
Oumla Ltd contract-interactions API
AE Profile APIs.io
Oumla Ltd contract-templates API
AE Profile APIs.io
Oumla Ltd deployed-contracts API
AE Profile APIs.io
Oumla Ltd networks API
AE Profile APIs.io
Oumla Ltd profiles API
AE Profile APIs.io
Oumla Ltd transactions API
AE Profile APIs.io
Oumla Ltd wallets API
AE Profile APIs.io
Oumla Ltd withdraw API
AE Profile APIs.io
Oumla Ltd workflows API
AE Profile APIs.io
#Tokenization
← Back to O APIs
API Details
ID
oumla-ltd:oumla-ltd-tokenization-api
Base URL
https://sandbox.oumla.com
Docs
https://docs.oumla.com/api-reference/introduction
Provider
Oumla Ltd
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=oumla-ltd-tokenization-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/oumla-ltd-tokenization-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Oumla Ltd tokenization API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.