> For the complete documentation index, see [llms.txt](https://docs.sign.singpass.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sign.singpass.gov.sg/for-relying-parties/how-our-api-works.md).

# How our API works

## Integrate Sign into your applications using our APIs

{% hint style="info" %}
If your organization is not capable of integrating directly with Sign APIs, you can consider approaching our [Digital Signing Partners](/for-relying-parties/digital-signing-partners.md). 
{% endhint %}

#### To get started on integration:

* [Read the documentation](/for-relying-parties/api-documentation/sign-v3.md)
* [Check the onboarding requirements](/for-relying-parties/onboard.md) 

This diagram illustrates at a high-level how your application and your users will interact with Sign:

<figure><img src="/files/Yf57N42yw5yToyohytdx" alt=""><figcaption></figcaption></figure>

## Conduct Code

Before integrating Sign into your application, please ensure that you adhere to the following principles:&#x20;

### <mark style="color:red;">What you see is what you sign</mark>

* You should always ensure that the user knows what they are signing before being directed to Sign.
* You should never use this system to misrepresent intended documents which your user plans to sign.

### <mark style="color:red;">PDPA & Applicable Regulations</mark>

* Protect, retain and transfer data retrieved according to the Personal Data Protection Act (PDPA), relevant industry regulations and applicable legislation.

### <mark style="color:red;">Lawful purposes</mark>

* Use Sign for lawful purposes only. Singpass reserves the right to terminate the integration if Sign is used for any unlawful purpose.

### <mark style="color:red;">Accessibility</mark>

* You should ensure that your user always has a fallback option if they are unable to use Singpass to sign (e.g. other forms of electronic signatures, or a physical option)&#x20;