# Legacy API v2

Documentation for version 2 of the Complyance API, for Saudi Arabia and Malaysia. It stays here for integrations that still use v2; new integrations should use the current API.

> **Building a new integration?**
>
> API v2 is no longer developed. Use the current API instead: start with the [developer quickstart](https://docs.complyance.io/get-started/quickstart/) and the [Unify API](https://docs.complyance.io/api-reference/unify/), which sends invoices for every supported country in one format.

## API v2 by country

- [Saudi Arabia (ZATCA)](https://docs.complyance.io/legacy/v2/ksa/): Sign up, generate an API key, onboard an EGS unit and send invoices with the v2 Unify API.
- [Malaysia (LHDN and Peppol)](https://docs.complyance.io/legacy/v2/malaysia/): Onboard for LHDN or Peppol, send invoices and receipts, and look up the v2 error messages.

## Moving to the current API

The current API replaces the separate v2 APIs with one request format, GETS, for every country. The [Saudi Arabia](https://docs.complyance.io/countries/sa/) and [Malaysia](https://docs.complyance.io/countries/my/) guides show how to onboard a company and send invoices with it. For help planning a move from v2, contact <support@complyance.io>.

Source: https://docs.complyance.io/legacy/