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

> ## Agent Instructions
> Use Gomobile customer-facing vocabulary.
> Do not infer support for internal, hidden, experimental, or unreleased features.

# Developer overview

> Connect your server-side integration using organization API keys.

Use the Gomobile API to work with your organization’s contacts, audiences, automation, and activity. Authenticate server-side requests with an organization API key.

## Before you integrate

* Use the API base URL supplied by Gomobile and the endpoints documented in this reference.
* Create a dedicated API key for one integration or environment.
* Keep the secret in a server-side secret manager.
* Use HTTPS and send the key in the `X-API-Key` request header.
* Plan for expiration, disabling, revocation, and replacement.

> [!WARNING]
>
> Never put a Gomobile API key in browser code, a mobile application, a public repository, a URL, analytics data, or logs.

## Authentication model

API keys are organization-scoped machine credentials. When creating one in the web application, you choose an **Admin**, **Manager**, or **Agent** role to determine available operations. The role cannot be changed after creation. Individual endpoints can impose additional restrictions.

> **[Authenticate with an API key](https://docs.gomobile.ma/developers/authentication.md)**
>
> Create, store, send, disable, and revoke a key safely.

> **[Learn the API basics](https://docs.gomobile.ma/developers/api-basics.md)**
>
> Configure the base URL, pagination, errors, and safe test environment before making a request.

> **[API access and support](https://docs.gomobile.ma/developers/support-boundary.md)**
>
> Find connection requirements and help for integration needs not covered in this reference.


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