- rename product to Scribase Mail across web app, emails, marketing and docs - new monochrome mark/favicons and neutral black/white theme; remove emoji UI - source code link (AGPL-3.0) in sidebar, login and unsubscribe pages - rewrite marketing site and self-hosting docs for OCI Email Delivery, add OCI notes page (event sources, unavailable features) - add NOTICE and MERGE.md crediting useSend and listing changes - add deploy/compose.scribase-mail.yml (web+postgres+redis, 1.47 GB limits), deploy/.env.example, Caddy site and DEPLOY.md for mail.scribase.com - replace legacy provider env vars in turbo.json, CI, env examples, docker files - OCI SDK packages as server externals for the standalone build Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
25 lines
750 B
Plaintext
25 lines
750 B
Plaintext
---
|
|
title: Introduction
|
|
description: "Fundamental concepts of Usend's API."
|
|
---
|
|
|
|
## Base URL
|
|
|
|
Scribase Mail's API is built on REST principles and is served over HTTPS. To ensure data privacy, unencrypted HTTP is not supported.
|
|
|
|
The Base URL for all API endpoints is:
|
|
|
|
```sh Terminal
|
|
https://mail.scribase.com/api/
|
|
```
|
|
|
|
## Authentication
|
|
|
|
Authentication to Usend's API is performed via the Authorization header with a Bearer token. To authenticate, you need to include the Authorization header with the word Bearer followed by your token in your API requests like so:
|
|
|
|
```sh Terminal
|
|
Authorization: Bearer us_12345
|
|
```
|
|
|
|
You can create a new token/API key under your Scribase Mail [Developer Settings](https://mail.scribase.com/dev-settings/api-keys).
|