API base URL, authentication headers, and content types.
Updated
https://api.dashfordevs.com
All API endpoints are relative to this base URL. The same API serves all organization types (e-commerce, service, wholesale).
| 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 |
curl -X GET "https://api.dashfordevs.com/storefront/products" \
-H "X-API-Key: pk_live_your_key_here"
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!"}'
| 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) |
sk_*) in client-side code. It provides full admin access to your organization.
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.
Every SDK method has one of these endpoints under it. The developer case covers why both surfaces exist rather than only one.