> ## Documentation Index
> Fetch the complete documentation index at: https://api.humdov.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> What the HumDov v1 API is, what it covers, and how to get started

The HumDov v1 API lets your own website or tools read and write records in your HumDov organization — add a member from a signup form, pull a form's submissions into your CRM, check someone in to a service, and so on.

It's a plain REST API: JSON in, JSON out, authenticated with a single API key. No OAuth flow, no SDK required.

## Base URL

```
https://api.humdov.app/v1
```

## What it covers

| Resource | What you can do |
| - | - |
| [Members](/api-reference/members/list-members) | List, read, create, and update members |
| [Tags](/api-reference/tags/list-tags) | List tags, and add/remove them on a member |
| [Prayer requests](/api-reference/prayer-requests/list-prayer-requests) | List, read, and submit prayer requests |
| [Forms](/api-reference/forms/list-forms) | List your forms and their fields |
| [Form responses](/api-reference/form-responses/list-form-responses) | List, read, and submit responses to a form |
| [Events](/api-reference/events/list-events) | List and read events |
| [Services](/api-reference/services/list-services) | List and read services |
| [Attendance](/api-reference/attendance/list-attendance) | List and record check-ins for a service |
| [Departments](/api-reference/departments/list-departments) | List and read departments |

Each resource only exposes the operations it's actually meant for — for example, Events and Services are read-only, since they're really there to let you discover an `event_id`/`service_id` for other calls rather than to manage events externally.

## Getting an API key

API keys are created from your HumDov dashboard, under **Developer API**. Each key is scoped to specific resources and operations (e.g. `members.create`, `form_responses.view`) — you only grant a key the access it actually needs.

<Note>
  A key can only be granted scopes that the person creating it already has permission for on the dashboard. If you can't see or edit a resource on the dashboard, you can't hand a key access to it either.
</Note>

Once created, the raw key is shown to you exactly once — store it somewhere safe. HumDov never stores or displays it again, only its last 4 characters.

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" href="/authentication">
    How to send your API key and what each scope means
  </Card>

  <Card title="Pagination & rate limits" href="/pagination-and-rate-limits">
    How list endpoints and request limits work
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.