Getting Your API Keys
Step 1: Access the Dakota Dashboard
To get an API key, you first need access to the Dakota Platform dashboard:New to Dakota? If you don’t have a Dakota account yet, contact our sales team to get started. Once your account is set up, you’ll receive credentials to access the dashboard.
Step 2: Create an API Key
- Log into your Dakota Platform dashboard
- Navigate to the API Keys section in the sidebar
- Click Create New API Key
- Give your key a descriptive name (e.g., “Production Server”, “Development Testing”)
- Choose a scope: Full access, Operate or Read only. See API Key Scopes
- Copy and store the key securely — it will only be shown once
API Key Format
API keys are base64-encoded strings with exactly 60 characters, for example:AHGlPZaxDSMz8Wf1l8VRH4ObdbHiKsWFWnmRyHtiwAc=
API Base URLs
Once you have your API key, use it with the corresponding API base URL:Required Headers
All API requests require thex-api-key header for authentication:
Mutating Requests: x-idempotency-key
Thex-idempotency-key header is required for POST, PUT, and PATCH requests to ensure request idempotency:
- Use a unique UUID for each logical operation
- Include this header on
POST,PUT, andPATCHrequests; do not include it onGETorDELETErequests - The key is cached for 24 hours. Once the first request has completed successfully, repeating it with the same key inside that window returns the original response instead of running it again. Reusing the key with a different request body returns
422idempotency-key-reused - Only successful responses are cached, so a failed request stays retryable under the same key
Content-Type Header
For requests with a body (POST, PUT, PATCH), include:Making Authenticated Requests
GET Request Example
GET requests only need the API key header:cURL
JavaScript
Python
Go
Rust
Java
POST Request Example
POST requests require both the API key and idempotency key headers:cURL
JavaScript
Python
Go
Rust
Java
Header Summary
Remember: Includex-idempotency-keyonPOST,PUT, andPATCHrequests.GETandDELETErequests should not include this header. The key must be a valid UUID.

