Skyden Send
Sign in
Getting Started / Authentication

Authentication

All API requests require authentication with an API key. Keys are created per project and can be scoped to specific permissions.

Bearer token

Pass your API key as a Bearer token in the Authorization header:

curl -X GET https://skyden.kiloconnectrdc.com/api/v1/messages \
  -H 'Authorization: Bearer sks_live_xxxxx' \
  -H 'Accept: application/json'
<?php
use Skyden\Send\SkydenSend;

SkydenSend::config('sks_live_xxxxx');
import { SkydenSend } from 'skyden-send';

SkydenSend.config('sks_live_xxxxx');

Key formats

Skyden Send uses two key formats, depending on the environment:

Test sks_test_xxxxxxxxxxxxxxxxxxxx

Use for development and testing. Requests are logged but not billed.

Live sks_live_xxxxxxxxxxxxxxxxxxxx

Use for production. Messages are delivered and billed.

Scopes

Each API key can be scoped to a limited set of permissions. Requests with an unauthorized scope will return a 403.

Scope Allows
message.sendSend messages
message.readRead messages
media.uploadUpload media files
media.readRead media files
otp.sendSend OTP codes
otp.verifyVerify OTP codes

Security best practices

  • Never commit your API key to Git. Use environment variables.
  • Rotate keys regularly (every 90 days recommended).
  • Use the minimum scopes needed for each integration.
  • Never expose a live key in client-side code.