Africore
API Reference.

The Africore REST API provides programmatic access to the Africore tokenization protocol — including asset listings, token issuance, cross-chain bridge operations, oracle price feeds, node data, and webhooks.

Base URL:

https://api.africore.io/v1

Authentication: All requests require a bearer token in the Authorization header:

Authorization: Bearer YOUR_API_KEY

All responses are JSON. Timestamps are ISO 8601 UTC. Rate limits: 100 req/min for standard keys; 1,000 req/min for institutional keys.

Example request:

curl -X GET https://api.africore.io/v1/assets \
  -H "Authorization: Bearer afr_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json"

API keys are issued per approved account through the Africore developer portal. Keys are prefixed afr_live_ for mainnet and afr_test_ for testnet. Two permission scopes are available: read-only and read-write.

Retrieve tokenized assets from the Africore protocol registry. Public assets are accessible with a standard read-only key.

Query Parameters — GET /assets

Example Response

[
  {
    "asset_id": "afr_asset_ke_0041",
    "name": "Nairobi Farmland Portfolio — Block 7",
    "jurisdiction": "KE",
    "category": "agriculture",
    "valuation_usd": 2400000,
    "yield_rate_pct": 8.4,
    "compliance_status": "verified",
    "token_address": "0x3fA8B653F9aB942e0b28DcA4..."
  }
]

The tokenization API is available to approved institutional issuers only. Submit real-world assets for on-chain tokenization and track job status through the compliance pipeline.

Request Body — POST /tokenize

Example Response

{
  "job_id": "tok_job_20260410_0087",
  "status": "pending_review",
  "estimated_completion": "2026-04-12T14:00:00Z",
  "assigned_compliance_officer": "co_nairobi_003"
}

The Africore Bridge enables cross-chain transfer of tokenized assets between Africore Chain and major EVM networks. Permissioned bridging preserves KYC/AML compliance across chains. Supported chains: africore | ethereum | polygon | bnb | arbitrum

Request Body — POST /bridge/transfer

The Africore Oracle Network delivers real-time and historical price data for tokenized assets. Prices are aggregated from multiple on-the-ground data sources, signed on-chain for immutability, and surfaced via these endpoints.

Example Response — GET /oracle/price/{asset_id}

{
  "asset_id": "afr_asset_ke_0041",
  "price_usd": 2418500,
  "last_updated": "2026-04-10T08:30:00Z",
  "source_count": 7,
  "confidence_score": 0.94
}

confidence_score ranges from 0.0 to 1.0, reflecting oracle consensus across data sources. Scores below 0.6 are flagged for manual review.

Query active infrastructure nodes on the Africore network. Node operators earn AFRI and USDC rewards for running oracle infrastructure and providing network uptime.

Example Response — GET /nodes/{node_id}

{
  "node_id": "node_ng_0014",
  "tier": "genesis",
  "owner_address": "0xaBc12...F9e4",
  "uptime_pct": 99.7,
  "earnings_afri": 1240.5,
  "earnings_usdc": 310.12,
  "last_reward_at": "2026-04-09T00:00:00Z"
}

Register a public HTTPS endpoint to receive real-time protocol events. Africore will POST a signed JSON payload to your endpoint whenever a subscribed event occurs.

Available Events

Payload Envelope

{
  "event": "yield.distributed",
  "timestamp": "2026-04-10T12:00:00Z",
  "data": { ... }
}

All webhook payloads include a X-Africore-Signature header containing an HMAC-SHA256 signature of the payload body, using your webhook secret as the key. Verify this signature before processing events.

All error responses follow a consistent envelope format. Inspect code for machine-readable error classification and message for a human-readable description.

Error Envelope

{
  "code": "ERR_VALIDATION",
  "message": "Required field 'jurisdiction' is missing.",
  "details": { "field": "jurisdiction" }
}

HTTP Status Codes