Base URL & Headers
API base URL, authentication headers, and content types.
Updated
On this page
Base URL
https://api.dashfordevs.com
All API endpoints are relative to this base URL. The same API serves all organization types (e-commerce, service, wholesale).
Required Headers
| Header | Value | Required |
|---|---|---|
X-API-Key | Your API key (pk_* or sk_*) | Yes (all endpoints) |
Content-Type | application/json | Yes (POST/PUT requests) |
Authorization | Bearer {access_token} | Authenticated endpoints only |
Example Request
curl -X GET "https://api.dashfordevs.com/storefront/products" \
-H "X-API-Key: pk_live_your_key_here"
Example POST Request
curl -X POST "https://api.dashfordevs.com/storefront/contact" \
-H "X-API-Key: pk_live_your_key_here" \
-H "Content-Type: application/json" \
-d '{"name": "Jane", "email": "jane@example.com", "content": "Hello!"}'
API Key Types
| Prefix | Type | Use Case |
|---|---|---|
pk_* | Public Key | Client-side / browser code (read-only frontend access) |
sk_* | Secret Key | Server-side only (full admin access, write operations) |
Never expose your secret key (
sk_*) in client-side code. It provides full admin access to your organization.
Health Check
GET /storefront/ping
X-API-Key: pk_live_your_key
Returns organization info including your org type (ecommerce, service, wholesale) if the key is valid.
Next Steps
- Pagination — Paginating list results
- Error Responses — Error format
- API Keys & Authentication — Getting your keys
Every SDK method has one of these endpoints under it. The developer case covers why both surfaces exist rather than only one.