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

# API Reference

Browse the Rekord API endpoints organised by resource: models, records, contributions, contexts, rules, workflows, webhooks.

The Rekord API groups endpoints by resource:

| Resource                                                      | Description                                                         |
| ------------------------------------------------------------- | ------------------------------------------------------------------- |
| [Models](/rekord-api/api-reference/models.md)                 | Schema definitions: fields, types, validation, resolution policies. |
| [Records](/rekord-api/api-reference/records.md)               | Resolved, current-best-answer for each entity.                      |
| [Contributions](/rekord-api/api-reference/contributions.md)   | Immutable evidence submissions from any source.                     |
| [Decisioning Contexts](/rekord-api/api-reference/contexts.md) | Decision boundaries grouping records, evidence, and evaluations.    |
| [Workflows](/rekord-api/api-reference/workflows.md)           | Workflow configuration for automated decision making                |
| [Webhooks](/rekord-api/api-reference/webhooks.md)             | Subscriptions, signing secrets, and test deliveries.                |

## API basics

The API is RESTful, and requests and responses use JSON. A few conventions apply across all endpoints:

* Property names use `snake_case`.
* Temporal values are ISO 8601 strings (e.g. `2026-01-15T09:30:00.12345Z`).
* Empty strings are not supported. Be explicit, and use `null` to unset a value.
* Resource collections use plural nouns in URLs (e.g. `/models`).

## API evolution

The Rekord API follows an append-only evolution strategy. We add new optional properties to request bodies, new properties to response bodies, and new endpoints. We do not remove or rename existing fields, change data types, or make optional fields mandatory.

We recommend you design your client to ignore unexpected fields in API responses.


---

# 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://docs.rekordsoftware.com/rekord-api/api-reference.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.