> For the complete documentation index, see [llms.txt](https://everyday-digital.gitbook.io/falkor-dev-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everyday-digital.gitbook.io/falkor-dev-docs/pathways/events-and-bookings/consume.md).

# Consume

The **Event Consume endpoint** allows you to **set the** [**state of attendance**](https://docs.falkor.io/pathways/events-classroom#attendance-states) to booked, absent, or attended. See the table below about the various states.

The Event Consume endpoint will **enable integrations where attendance is managed through a different mechanism** i.e. not the built-in check-in. This can be useful if your classroom or event activities need additional communication, access codes, or tickets.

## Attendance States

| States                                                                                |
| ------------------------------------------------------------------------------------- |
| <p><strong>booked</strong><br>The user is registered for the event.</p>               |
| <p><strong>attended</strong></p><p>The user has attended the event.</p>               |
| <p><strong>absent</strong></p><p>The user was absent at the event/did not attend.</p> |

## Consuming Attendance

In order to consume attendance, you will need to **retrieve the attendance** `guid`. This can either be done via the **event list endpoint** or automatically via **event webhooks**. The consume endpoint allows you to **set the attendance state** for single or multiple users.

{% content-ref url="/pages/-MILDIkjuq4JAZQrfay9" %}
[Webhooks](/falkor-dev-docs/pathways/webhooks.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MILDEI4GFeIg0xi-450" %}
[List](/falkor-dev-docs/pathways/events-and-bookings/list.md)
{% endcontent-ref %}

### Parameters

| Key       | Type                                        |
| --------- | ------------------------------------------- |
| **guids** | Array. A list of GUIDs.                     |
| **state** | String. The state to set the attendance to. |

```
curl -X POST \
  v1/rewards/consume \
  -H 'Authorization: Basic <Your Base64 Encoded Token>' \
  -d '{
	"guids" : ["3bf56525-d5ad-4f39-88b3-0cdcd0bfc7dc",...etc],
	"state" : "attended"
}'
```

### Success Response

The response will contain how many attendees have a **changed state**. Attendees will only change their state if the **current state** does not match the **new state**.

```
{
    "status": "success",
    "data": {
        "changed": 5
    },
    "hash": "dfdfac8d5493733dfab6d24c599785ba",
    "response_time": 0.11311697959899902
}
```


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://everyday-digital.gitbook.io/falkor-dev-docs/pathways/events-and-bookings/consume.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.