# Developers: build on DAPL in Africa | Arrel

URL: https://arreltech.com/developers

> Build on DAPL, digital asset infrastructure for Africa: one API for custody, venues, stablecoin settlement and compliance, with a sandbox on request.

# Build on DAPL, digital asset infrastructure for Africa.

One API for custody, venues, stablecoin settlement and compliance. Documentation and a sandbox are available on request.

[Request sandbox](#sandbox) [Talk to us](https://arreltech.com/company/contact-sales)

## Documentation, on request.

Quickstart

From sandbox keys to a first screened transfer.

On request

Documentation

Concepts: wallets, policies, approvals, checks and providers.

On request

API reference

Every endpoint, request and response.

On request

SDKs

Client libraries for the main server languages.

On request

## One API, every provider underneath.

Your systems call DAPL. The same request works whichever custodian, venue or screening tool sits behind it, and every call runs your checks first.

Illustrative request

```
<span class="c"># Illustrative, not the published API</span>
<span class="k">POST</span>  /transfers
{
<span class="s">"from"</span>: <span class="s">"treasury-wallet"</span>,
<span class="s">"to"</span>: <span class="s">"counterparty-a"</span>,
<span class="s">"asset"</span>: <span class="s">"USDC"</span>,
<span class="s">"amount"</span>: <span class="s">"250000.00"</span>,
<span class="s">"approval_policy"</span>: <span class="s">"two-approvers"</span>
}

<span class="c"># Response: checks run before funds move</span>
{ <span class="s">"status"</span>: <span class="s">"pending_approval"</span>, <span class="s">"screening"</span>: <span class="s">"clear"</span>, <span class="s">"approvals"</span>: <span class="s">"1 of 2"</span>  }
```

## Guides by job, for African use cases.

Guide 01

Settle cross-border in stablecoins

Move USDC between counterparties, with screening and two-person approval before release.

Guide 02

Accept and pay out

Receive funds, convert at the venue you chose, and pay out in local currency.

Guide 03

Connect exchanges

Reach 11 venues, VALR and Luno first, through one integration.

Guide 04

Run client mandates

Segregated wallets, rules and reporting per client mandate.

Guide 05

Run compliance on every transfer

KYT and KYC checks before funds move.

Guide 06

Tokenize a register

Issue an instrument and check every transfer against the issuer's rules.

## The toolkit, as it opens up.

Sandbox

A test environment with DAPL and connected providers.

On request

Code samples

Working examples for each guide.

Coming

Status

Live status of DAPL and each integration.

Coming

Changelog

What changed, and when.

Coming

## Request sandbox access for your engineers.

For engineering teams at African financial institutions evaluating DAPL. Arrel replies by email.

NameWork email

Institution Country

What would you like to build first?

## Developers, answered.

Is there a public API reference?

Documentation, the API reference and SDKs are shared with institutions on request during evaluation. Request sandbox access below.

Is there a sandbox?

Yes. Sandbox access is given on request to engineering teams at African institutions evaluating DAPL.

Do we integrate each provider separately?

No. Your systems call DAPL's API once; DAPL maintains the connections to each custodian, venue, rail and screening tool.

What does a typical integration involve?

A technical walkthrough of your current stack with Arrel's engineers, sandbox access, then a launch typically measured in weeks.