> For the complete documentation index, see [llms.txt](https://mimic-api.gitbook.io/mimic-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mimic-api.gitbook.io/mimic-api-docs/earn/stakings/stakings-id.md).

# /stakings/{id}

Get the status of a stake or unstake execution.

```json
{"openapi":"3.1.0","info":{"title":"Mimic API","version":"0.0.1-rc"},"tags":[{"name":"Stakings","description":"Deposit ETH into a staking protocol to generate yield, or unstake it. Compute EIP-712 data to sign via `POST /stakings/{action}/prepare`, then submit the signature via `POST /stakings/{action}/{id}/execute`."}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"header","name":"X-Api-Key","description":"API key for your Mimic account. Required for every operation except the public reference-data endpoints."}},"parameters":{"ActionId":{"name":"id","in":"path","required":true,"description":"ID returned by `POST /{action}/prepare`.","schema":{"$ref":"#/components/schemas/UUID"}}},"schemas":{"UUID":{"type":"string","format":"uuid","description":"Identifier for an action request, returned by `POST /{action}/prepare` and used to submit its signature and track its status."},"ExecutionStatus":{"type":"object","description":"Status of an action execution.","required":["status"],"properties":{"status":{"type":"string","enum":["pending","succeeded","failed","skipped"],"description":"Status of this execution."},"inputs":{"type":"object","description":"Key-value map of the original request parameters."},"timestamp":{"allOf":[{"$ref":"#/components/schemas/Timestamp"}],"description":"Timestamp of the execution."},"logs":{"type":"array","description":"Execution log messages.","items":{"type":"string"}},"error":{"type":"string","description":"Error message. Present only when status is `failed`."}}},"Timestamp":{"type":"integer","title":"Unix timestamp (ms)","description":"Unix timestamp in milliseconds."},"HexString":{"type":"string","description":"An arbitrary 0x-prefixed hex string."},"Error":{"type":"object","properties":{"message":{"type":"string"}}}},"responses":{"BadRequest":{"description":"Bad request — invalid parameters or body.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"Unauthorized":{"description":"Unauthorized — missing or invalid credentials.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"NotFound":{"description":"Resource not found.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}}},"paths":{"/stakings/{id}":{"get":{"tags":["Stakings"],"description":"Get the status of a stake or unstake execution.","parameters":[{"$ref":"#/components/parameters/ActionId","description":"ID returned by `POST /stakings/stake/prepare` or `POST /stakings/unstake/prepare`."}],"responses":{"200":{"description":"Status of the stake or unstake execution.","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ExecutionStatus"},{"type":"object","properties":{"txHash":{"allOf":[{"$ref":"#/components/schemas/HexString"}],"description":"Transaction hash. Present only when status is `succeeded`."}}}]}}}},"400":{"$ref":"#/components/responses/BadRequest"},"401":{"$ref":"#/components/responses/Unauthorized"},"404":{"$ref":"#/components/responses/NotFound"}}}}}}
```


---

# 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://mimic-api.gitbook.io/mimic-api-docs/earn/stakings/stakings-id.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.
