The Data Mammoth API provides programmatic access to your entire hosting infrastructure. Automate server provisioning, manage billing, handle support tickets, and integrate Data Mammoth services into your applications and workflows. This guide introduces the API concepts, architecture, and capabilities.
What Can You Do with the API?
The Data Mammoth API lets you automate virtually every action available in the dashboard:
- Server management — Create, configure, start, stop, restart, and delete servers.
- Billing operations — View invoices, check payment status, and manage subscriptions.
- Support — Create and manage support tickets, access Knowledge Base articles.
- Account management — Update account details, manage SSH keys, and configure settings.
- Monitoring — Retrieve server metrics and performance data.
- Webhooks — Receive real-time notifications for events.
API Architecture
The Data Mammoth API follows REST (Representational State Transfer) principles:
- Base URL — All API requests are made to
https://api.datamammoth.com/v1/ - HTTP Methods — Standard methods are used:
GET — Retrieve data
- POST — Create new resources
- PUT / PATCH — Update existing resources
- DELETE — Remove resources
- JSON format — All requests and responses use JSON.
- HTTPS only — All API communication is encrypted via TLS.
Quick Example
Here is a simple example that lists your servers:
curl -X GET "https://api.datamammoth.com/v1/servers" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json"Response:
{
"data": [
{
"id": "srv_abc123",
"name": "web-production",
"status": "running",
"ip": "203.0.113.10",
"plan": "vps-standard",
"region": "us-east",
"os": "ubuntu-24.04",
"created_at": "2026-01-15T10:30:00Z"
}
],
"meta": {
"total": 1,
"page": 1,
"per_page": 25
}
}API Endpoints Overview
| Endpoint Group | Path | Description |
|---|---|---|
| Servers | /v1/servers | Create, manage, and monitor servers |
| Billing | /v1/billing | Invoices, payments, and subscriptions |
| Support | /v1/support | Tickets and Knowledge Base |
| Account | /v1/account | Account settings and SSH keys |
| Webhooks | /v1/webhooks | Event notification configuration |
Authentication
The API supports multiple authentication methods:
- API Keys — Simple bearer token authentication for server-to-server communication.
- JWT (JSON Web Tokens) — Token-based authentication with expiration for enhanced security.
Response Format
All API responses follow a consistent structure:
Success Response
{
"data": { ... },
"meta": { ... }
}Error Response
{
"error": {
"code": "not_found",
"message": "The requested server was not found.",
"status": 404
}
}See API Error Codes & Handling for a complete error reference.
Rate Limiting
API requests are subject to rate limits to ensure fair usage and platform stability. Rate limit information is included in response headers. See API Rate Limits & Best Practices for details.
SDKs and Code Examples
We provide code examples in popular languages:
Getting Started
What to Do Next
- API Authentication — Keys & JWT — Get your API credentials.
- API Quickstart — Your First API Call — Start making API calls.
- API Rate Limits & Best Practices — Optimize your API usage.
- Webhooks — Real-Time Event Notifications — Set up event-driven integrations.