> For the complete documentation index, see [llms.txt](https://city-protocol.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://city-protocol.gitbook.io/docs/tokenization-as-a-service/api-and-sdk-surface.md).

# API and SDK surface

TaaS is designed to be integrated through APIs and SDKs.

A typical integration surface includes:

<table><thead><tr><th width="191.5">Interface</th><th>Purpose</th></tr></thead><tbody><tr><td>Product Registry API</td><td>Fetch product metadata, supported networks, token addresses, risk labels, capacity, fees, and redemption terms.</td></tr><tr><td>Investor Eligibility API</td><td>Check whether a wallet or user is eligible to subscribe, hold, transfer, or redeem.</td></tr><tr><td>Subscription API</td><td>Route deposits, create subscription records, and issue tokens or vault shares.</td></tr><tr><td>Redemption API</td><td>Submit redemption requests, check status, and claim settlement assets.</td></tr><tr><td>Oracle API</td><td>Retrieve latest NAV, historical NAV, update time, signer status, and deviation status.</td></tr><tr><td>Attestation API</td><td>Retrieve reserve proofs, report hashes, verification timestamps, collateralization records, and service-provider confirmations.</td></tr><tr><td>Webhooks</td><td>Notify integrators of NAV updates, product status changes, permission changes, subscription events, and redemption events.</td></tr></tbody></table>

&#x20;

These interfaces allow partner platforms to integrate tokenized yield products without directly managing the full operational stack.