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

# API

LimeCall's [API and WebHooks](https://platform.limecall.com/settings/api)

LimeCall's (API) key is a code used to identify and authenticate an application or user. Acting as a unique identifier and provide a secret token for authentication purposes.

LimeCall's API will define how pieces of software interact with each other. It controls requests made between programs, how those requests are made, and the data formats used.

**Why Use API Keys?**

API keys are commonly used to control the utilization of the API’s interface and track how it is being used. This is often as a precaution to prevent abuse or malicious use. Adding additional security when communicating between platforms.

<figure><img src="/files/3PNkHibqRqJlqbPKnIiR" alt=""><figcaption></figcaption></figure>

**Inbound + Outbound WebHooks**

You might have seen webhooks mentioned in your apps' settings and wondered if they're something you should use.&#x20;

The answer is probably yes.

WebHooks are one way that apps can send automated messages or information to other apps.

They're a simple way your online accounts can 'speak' and 'notify' each other of events such as orders or calls, and get notified automatically when something new happens. In many cases, you'll need to know how to use webhooks if you want to automatically push data from one app to another.

Here's our guide on [Integrating WebHooks + API](https://docs.limecall.com/integration-channels/webhooks-+-api)


---

# 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.limecall.com/getting-started/settings/api.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.