# Ledger Adapter API

**URL:** <https://forum.interledger.org/t/ledger-adapter-api/553>\
**Category:** Implementations and SDKs\
**Tags:** plugins, payment-channels, settlement\
**Created:** [April 29, 2019, 5:35pm UTC](https://forum.interledger.org/t/ledger-adapter-api/553 "2019-04-29T17:35:05Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![adrianhopebailie](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/adrianhopebailie/32/31_2.png) [@adrianhopebailie](https://forum.interledger.org/u/adrianhopebailie)\
**Post date:** [May 13, 2019, 2:17pm UTC](https://forum.interledger.org/t/ledger-adapter-api/553/13 "2019-05-13T14:17:53Z")

</div>

> [@emschwartz](#):
>
> Whether it’s called a Settlement Engine or a Ledger Adapter, we’re talking about the API from the connector to this external system.

No. As already discussed in [Settlement Architecture - #3 by adrianhopebailie](https://forum.interledger.org/t/settlement-architecture/545/3) the external system either includes a “Settlement Engine” (the component that decides when to settle and by how much, as defined in that same thread) or not.

This changes how you design the API.

The purpose of this thread was to discuss the API for an external system that DOES NOT include settlement business logic (i.e. it’s just a ledger adaptor). If you are suggesting that this is a bad design then let’s abandon this thread and go back to [Settlement Architecture - #3 by adrianhopebailie](https://forum.interledger.org/t/settlement-architecture/545/3) where we have all of the option properly laid out.

I’ve addressed some of your points above in that thread

---

_[View the full topic](https://forum.interledger.org/t/ledger-adapter-api/553)._