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

# Plugin API

*This section is recommended for developers only. If you are not familiar with PHP, javascript and WordPress programming, I suggest you rather ask for advice from a developer.*

The plugin provides an API for developers. This API provides a good way of making changes in the plugin behavior without thouching the plugin code.

Before altering the plugin code for your needs, consider looking for an action or filter hook in this reference. Using hooks is a redundant and update proof way of making changes.

If you are a developer, but unfamiliar with WordPress hooks, then please study the [WordPress plugin API](https://codex.wordpress.org/Plugin_API) first.

* [Actions list and usage](/plugin-api/actions-list-and-usage.md)
* [Filters list and usage](/plugin-api/filters-list-and-usage.md)
* [asp\_query\_args special filter](https://knowledgebase.ajaxsearchpro.com/hooks/filters/asp_query_args)
* [Theme functions](/plugin-api/theme-functions.md)
* [Front-end filters API](/plugin-api/front-end-filters-api.md)
* ASP\_Query Class


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.ajaxsearchpro.com/plugin-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.