# API Workflow

The normal workflow for Linked Records follows this sequence of operations:

1. [Configure API](/nchain-event/linked-records/api-workflow/configure-api.md)
2. [Create Link Record](/nchain-event/linked-records/api-workflow/create-link-record.md)
3. [Get Link Location Status](/nchain-event/linked-records/api-workflow/get-link-location-status.md)
4. [Read Link Record](/nchain-event/linked-records/api-workflow/read-link-record.md) **\***
5. [Update Link Record](/nchain-event/linked-records/api-workflow/update-link-record.md) **\***
6. [Delete Link Record](/nchain-event/linked-records/api-workflow/delete-link-record.md) **\***
7. [Verify Link Record](/nchain-event/linked-records/api-workflow/verify-link-record-+.md) [**†**](/nchain-event/overview/configuration-symbols.md) **\***
8. [Navigate Link Record](/nchain-event/linked-records/api-workflow/navigate-link-record.md) [¶](/nchain-event/overview/configuration-symbols.md) **\*** 

{% hint style="info" %}
Note: **\*** Although these operations can be performed any time after creating a link record, they will only be reading from the blockchain after the record has been confirmed by Get Location Status.
{% endhint %}

These operations are described in more detail below.


---

# 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://docs.teranode.group/nchain-event/linked-records/api-workflow.md?ask=<question>
```

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.