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

# Overview

> Look up any term the docs use with a specific meaning.

| Term                                                               | Means                                                                                                                                                          |
| ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Category**                                                       | The kind of system - `hris`, `ats` or `lms`. Decides which models exist and appears in every endpoint path                                                     |
| **[Integration](/get-started/integrations)**                       | A vendor system, named by a slug such as `bamboohr`                                                                                                            |
| **[Connector](/get-started/how-to-connect)**                       | Your customer's connection to one integration. Holds their credentials and sync schedule                                                                       |
| **[Model](/get-started/model-availability)**                       | A unified object type - employee, benefit, candidate. The same across every integration in its category                                                        |
| **[Record](/guides/reading-writing/record-identity)**              | One instance of a model, synced from one connector                                                                                                             |
| **Organization**                                                   | Your Bindbee account                                                                                                                                           |
| **[Environment](/get-started/environments)**                       | Development or Production. Separate connectors and keys; shared logs, scope and custom fields                                                                  |
| **[API key](/api-reference/basics/authentication)**                | Authenticates your organization. Sent as `Authorization: Bearer`, on every request                                                                             |
| **[Connector token](/api-reference/basics/authentication)**        | Tells Bindbee whose data you want. Sent as `X-Connector-Token` on any request that reads or writes a specific connector                                        |
| **[Scope](/get-started/scoping)**                                  | The models and fields Bindbee is allowed to fetch. A field outside scope is absent from responses                                                              |
| **[Sync](/guides/reading-writing/syncing)**                        | The job that fetches the data from the source system and puts it in Bindbee's shape. Automatic in Production, manual in Development                            |
| **[Custom field](/guides/extending/custom-fields)**                | A value the unified model doesn't carry, pulled out of the [raw payload](/guides/reading-writing/raw-data) with a [JMESPath](https://jmespath.org/) expression |
| **[Magic Link](/get-started/how-to-connect)**                      | A hosted page where your customer authorizes their own system, with no front-end code on your side                                                             |
| **[Passthrough](/guides/extending/passthrough)**                   | A request forwarded to the source system's own API, using the credentials already on a connector                                                               |
| **[Issue](/guides/troubleshooting/errors)**                        | A failure raised automatically against a connector, carrying the request and response behind it                                                                |
| **[Meta API](/guides/reading-writing/writing-data/meta-apis)**     | Returns the request shape a write endpoint expects for a given connector, since required fields differ by system                                               |
| **[`id` vs `remote_id`](/guides/reading-writing/record-identity)** | `id` is Bindbee's identifier - stable, the one to store. `remote_id` is the source system's own                                                                |

To reach one customer's data you send both: the API key says who you are, the connector token says which customer. [Authentication](/api-reference/basics/authentication) lists which endpoints need which.

## Related

* [Quickstart](/get-started/quickstart) - these terms in action, on a test connector
* [Environments](/get-started/environments) - what the two environments separate, and what they share
* [How to connect](/get-started/how-to-connect) - the two ways a connector is created
* [Scoping](/get-started/scoping) - what organization-level scope controls
* [Authentication](/api-reference/basics/authentication) - how the two tokens are supplied