> For the complete documentation index, see [llms.txt](https://docs.verifyme.ng/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifyme.ng/introduction/getting-started.md).

# Getting Started

You can start integrating our API's into your beautiful products by following the steps below:

* Create a Corporate VerifyMe account by navigating to <https://verifyme.ng/auth/signup>

![](/files/-McgOrpuzNANbD2CPQQc)

* Once you have created the account, Kindly request for your account to be enabled for API from your verifyMe account manager. You need to specify your `risk threshold` and `identity payload type` while making this request. See more about risk level and identity payload type [here](/introduction/about-verifications.md).

* Once created you should have access to the API section in the image below. Your **API KEYS** and **Webhooks** can be found in this part of your portal.

![API dashboard](/files/-McgPeJdxkQzIyO8s4ul)

* Head over to the **Billing** tab and fund your account in order to start making verification requests.

* Once funded, You should be able to make successful API calls🎊


---

# 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.verifyme.ng/introduction/getting-started.md?ask=<question>&goal=<endgoal>
```

`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.