ARK Core: Legacy API v1 Will No Longer Be Supported As Of June 1st 2019

In November 2018 we migrated to ARK Core
v2 on our
Public Network. All exchanges, node operators and API users were recommended to
migrate to the new v2 API along with the update to ARK Core v2.

As of now the Public v1 API is still maintained, however this will change on
June 1st. API v1 will reach its End Of Life cycle at that time. If you are still
using the old API v1 you must migrate over to API v2.

After the 1st of June existing nodes will no longer respond to v1 API calls.

We chose to continue supporting the v1 API during the Core v2 migration to make
transition as smooth as possible while giving everyone ample time to switch. It
is now nearing the EOL of API v1 and as such we would like to remind everyone to
please switch to API v2 as soon as you can.

Check the documentation for more details and a
special guide written on how to migrate your tools from ark-node v1 to the new
Core v2.

In general, you have two options to choose from, but we highly recommend the
first — using the official ARK Crypto and Client packages.

Use ARK Crypto and Client packages (recommended)

Use our crypto and client SDKs in your code. By doing so you will have full
support for upcoming releases and no further migrations will be needed besides
updating versions of our maintained SDKs via respective package repositories. We
have SDKs (client and crypto) implementations available in more than 12
programming languages.

**All our SDK implementations are available here:
**https://docs.ark.io/sdk

SDKs have two parts:

• CLIENT** **to handle the REST
  API communication part.
• CRYPTO** **for
  transaction building & signing.

**You can check minimal code demos here: **SDK Usage
Demos

Manual Implementation (not really recommended)

If you don’t want to use our Client SDKs or are unable to do so, you will need
to implement generation and broadcasting of transactions by yourself via our
public API v2 endpoints.

NOTE: Manual implementation is only for advanced users and developers who know
what they are doing. Support for any kind of issues arising in this method will
also be limited, since each implementation can vary depending on integration.

General documentation is available at**
**https://docs.ark.io/api/public/v2/.

We strongly recommended you do NOT use this option, as there are features that
will change in the transaction payload generation and signing. It is best to go
with our client and crypto packages to have long term sustainability.

---

Follow us on social media ( Twitter | Facebook | Reddit | YouTube), join our community ( Slack | Discord ) and stay tuned to our blog on Medium.