# "api" object
{% hint style="info" %}
🎥 Watch the "api" object section of the ["Server Global State (TanStack/React Query)"](https://youtu.be/f-UX9pu7u9Y) style guide video here.
{% endhint %}
***
We use a [custom-built **"api" object**](https://youtu.be/lux6vB4GyWk?si=YPnseIcBPZUjkZxy), which is essentially a wrapper over [React Query](https://tanstack.com/query/v3/)[ (v3)](https://tanstack.com/query/v3/), and is [tRPC-like](https://create.t3.gg/en/usage/trpc) in terms of usage.
The frontend routes line up with our backend routes according to our [(v2) API schema](https://pavewise.gitbook.io/pavewise-style-guide-and-more/api).\
\
\&#xNAN;*(in the comments in the second image below, you can see which backend/Rails controller actions are related to each frontend route)*
***
### Overview
* [**Configuration**](#configuration)
* [**Usage**](#usage)
***
### Configuration
**"api" object** (holds "router" objects)
**"router" objects** (hold **"procedures"** -- e.g. getSingle, getMany, etc.)
***
### Usage
* **Queries (e.g. getSingle, getMany) (useQuery-wrapped procedures)**
* **Mutations (e.g. create, update, delete) (useMutation-wrapped procedures)**
**-- Top-level resource (e.g. projects):**
```jsx
mutationProjectUpdate.mutate({
id: doc.id,
payload: {
production_goal: requestData.production_goal,
},
});
```
**-- Nested resource (e.g. production goals -- projects/production\_goals)**
```jsx
mutationProductionUpdate.mutate({
parentResource: 'projects',
parentId: doc.id,
id: production.id,
payload: {
date: production.date,
goal: production.goal,
actual: production.actual,
},
});
```
---
# Agent Instructions: 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:
```
GET https://pavewise.gitbook.io/pavewise-style-guide-and-more/frontend/our-systems/data-fetching-and-apis/api-object.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
