Authentication
Login accepts a single identifier while registration submits either email or phone plus consent values.
SMS API
Amiq keeps integration predictable: submit a message, track its state, receive callbacks, and keep route decisions observable.
Create accountRequest shape
The website proxy follows the provided OneHub contract for auth, contact, subscribers, channels, and content. Messaging endpoints can be layered into the same server-side pattern.
identifier: email or phone
site: x-onehub-site
error: code, message, requestId
pagination: limit, offset, hasMoreEndpoint families
The implementation avoids turning the API catalog into a public control panel.
Login accepts a single identifier while registration submits either email or phone plus consent values.
Consultation messages are submitted to the public contact endpoint with source URL context.
Public channel rates are fetched through a local route handler with loading, empty, error, and retry states.
Callbacks
A clean SMS API treats delivery as a state machine, not a single yes-or-no event.
Validate parameters, create a traceable request ID, and return a state the app can store.
Resolve destination and channel logic without leaking provider details to clients.
Send a delivery report to the customer's webhook once downstream evidence arrives.
Group errors into actionable categories for retry, support, or compliance review.
Developer experience
The page mirrors a developer-doc feel without becoming a separate docs portal.
HTTP and JSON are the default integration primitives for predictable server-to-server messaging.
Request IDs, error codes, and pagination fields are preserved through route handlers.
API keys and admin tokens stay outside client bundles and are configured as environment secrets.
Amiq can help model OTP, alert, or lifecycle traffic before the production route is turned on.
Plan integration