REST API • v1 • JSON
Automate expiry tracking, reminders, contacts, tasks, vehicles, equipment, locations, and document management directly from your application. One REST API, full coverage.
# 1. Get your access token
curl -X POST https://api.remindax.com/v1/oauth/token \
-H "Content-Type: application/json" \
-d '{"grant_type":"client_credentials","client_id":"YOUR_ID","client_secret":"YOUR_SECRET"}'
# 2. Call any endpoint
curl https://api.remindax.com/v1/items \
-H "Authorization: Bearer YOUR_TOKEN"
Explore full API reference ↓
Create an API app, get a token, and make your first request. All calls go to https://api.remindax.com over HTTPS. An active subscription is required; expired accounts receive HTTP 403 subscription_inactive.
Open Settings → Developers. Create an app, set scopes (space or comma separated, or leave blank for full access), then copy the client_id and client_secret. The secret is shown only once.
The Token Endpoint on that page is the public URL you should call:
https://api.remindax.com/v1/oauth/token
POST grant_type=client_credentials with your client credentials. Do not call /partner/v1 — that path is internal to the app.
POST https://api.remindax.com/v1/oauth/token
Content-Type: application/json
{
"grant_type": "client_credentials",
"client_id": "YOUR_CLIENT_ID",
"client_secret": "YOUR_CLIENT_SECRET"
}
A successful response looks like:
{
"token_type": "Bearer",
"access_token": "eyJ...",
"expires_in": 86400,
"scope": "*"
}
Tokens last 86400 seconds (24 hours). When expires_in elapses, POST to the same endpoint again — there is no refresh token.
Send the token as a Bearer header. Versioned paths are under /v1.
GET https://api.remindax.com/v1/items Authorization: Bearer YOUR_ACCESS_TOKEN Accept: application/json
You get a JSON list of tracked items. Browse the API Reference for contacts, reminders, folders, tasks, vehicles, equipment, locations, Drive uploads, and the rest of the API.
A record of notable API changes, newest first.
vehicles:*, equipment:*, and locations:* scopes.