> For the complete documentation index, see [llms.txt](https://docs.esignet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esignet.io/home/esignet-2.0.0/develop/integration.md).
# Integration Guides - eSignet
Explore seamless eSignet integration with guides on authentication, digital wallets, and more.
## Integration Guides
eSignet is built as a core engine with a small number of deliberately pluggable extension points, rather than one monolithic system you have to fork to adapt. That separation — covered in [Architecture](/home/esignet-2.0.0/develop/architecture.md) — is what makes it possible to connect eSignet to a different identity backend, change how it logs activity, or let your own application use it for login, without touching the engine itself.
This section assumes you already know what eSignet is and how its pieces fit together. It's for when you're ready to extend or connect to eSignet for your own use case, and it points you to the exact extension point and reference implementation to start from.
There are three ways to integrate with eSignet:
### Connect eSignet to Your Identity System
eSignet doesn't hardcode how a person's identity gets verified — that's handled by a pluggable `authnprovider` interface. If you want eSignet to authenticate people against your own identity system (a national ID registry, a credential store, an existing user directory), you implement this interface rather than modifying eSignet itself, the fastest way to see a real, working `authnprovider` before you write your own.
### Add or Customize Audit Logging
Every authentication and consent event eSignet handles can be captured for audit purposes — who logged in, when, and what was consented to. This is also implemented as a plugin, so you can route audit events wherever your organization needs them (a SIEM, a compliance data store, a log pipeline) instead of being limited to whatever eSignet logs by default.
### Connect Your Application to eSignet
If you're building an application — a website, a mobile app, a backend service — that should let people log in with eSignet, this is your path. It covers registering your application as a relying party, exchanging the result of a login for tokens, and retrieving the user's shared details.
### Which One Do I Need?
| If you want to... | Go to |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Plug eSignet into your own identity backend (ID registry, credential store, user directory) | [Authnprovider](/home/esignet-2.0.0/develop/integration/authenticator.md) |
| Capture or export logs of authentication and consent activity | [Audit Plugin](/home/esignet-2.0.0/develop/integration/audit.md) |
| Let users of your application log in with eSignet | [Relying Party Integration](/home/esignet-2.0.0/develop/integration/relying-party.md) |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.esignet.io/home/esignet-2.0.0/develop/integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
